Delivery step 02
Map systems, formats, and authority
Every source and consumer is named. For each one the platform records the format, the system that owns the data, the consent rule, and who may change it.
What happens
- List each source, its system of record, and its exchange method.
- Record the consent boundary and the purpose of use for each data flow.
- Name the downstream consumer of each field in the case record.
How the platform carries it out
- The source map is the table in Where The Data Comes From: eight source families, each with its format and its entry point.
- Authority is recorded for each field: the system of record, the last writer, and the approver for a change.
- Consent and purpose are checked when data is read, rather than stored as a separate copy.
AI role
Proposes a first draft of the source map from interface specifications and configuration files. The integration analyst corrects it before it is used.
Approval
The data owner for each source confirms its row in the map.
Systems involved
- Interface specifications from each partner
- Salesforce object map
- Source register in the case record
Reference components
- channel inventory
- resource mapping
Pre-sizing
Business case, effort, time, and cost for this step.
These are planning estimates for scoping. They are based on the work listed here and must be checked with the client before a commitment is made.
Business justification
Most rework comes from data that is copied between systems without an owner. A source map with authority per field removes that rework and makes consent visible before any data moves.
Business value
- Every field has one system of record and one approver for changes.
- Consent and purpose are checked before data is shown or sent.
- New sources can be added without rediscovering the existing ones.
Documentation to produce
- Source register
- Field authority register
- Consent and purpose matrix
- Consumer map per field
Work breakdown and effort
| Work item | Person-days |
|---|---|
| Inventory sources, systems of record, and exchange methods | 6 |
| Build the field authority register | 5 |
| Map consent boundaries and purposes of use | 4 |
| Map downstream consumers for each field | 3 |
| Review with each data owner | 2 |
| Total effort | 20 |
Delivery time
3 weeks for the full step.
Resources required
- Integration architect: 1 FTE
- Business analyst: 0.5 FTE
- Privacy and compliance reviewer: 0.25 FTE
POC: 1 weeks
Scope
- Map the sources for one case type end to end, including one EHR feed and one laboratory feed
Exit criteria
- Each field in the POC scope has an authority and a consent rule
MVP: 2 weeks
Scope
- Source register and authority register for all sources in the case workflow
- Consent matrix reviewed by the data owners
Exit criteria
- Every data owner has confirmed their rows
- No field in the case record lacks an authority
Assumptions
- Interface specifications are available from each partner
- Data owners respond within the review window
Risks
- Partners cannot provide interface specifications on time
- Consent rules differ by source
Cost calculation
Enter your own day rate and weekly platform cost. Until they are entered, the calculator shows effort and delivery time only.
- Effort
- 20 person-days
- Delivery time
- 3 weeks
- Labor cost
- 0
- Platform cost
- 0
- Total estimate
- 0