Skip to content

docs(data-integration): one reference rule, and scope the row key to its feed - #72

Closed
akim1995 wants to merge 1 commit into
mainfrom
akim/data-integration-one-reference-rule
Closed

docs(data-integration): one reference rule, and scope the row key to its feed#72
akim1995 wants to merge 1 commit into
mainfrom
akim/data-integration-one-reference-rule

Conversation

@akim1995

Copy link
Copy Markdown
Contributor

No description provided.

…its feed

Row keys claimed every row carries record_id, but the Provider Directory
feed has none: it keys on npi, network_id and plan_id. Both row rules now
say which feed they govern, as History already did.

Four foreign keys resolved against record_id and four against the target's
own key, with nothing on the page saying which did what. Two of those keys
earned it — patient_identifier and encounter_id have _system companions and
become Patient.identifier and Encounter.identifier. The other two did not:
location_id and report_id have no system, never reach FHIR, and exist only
to be pointed at, which is what record_id is for. diagnostic_reports even
carried report_id equal to record_id on every row.

Dropping them leaves one rule with two stated exceptions, and locations
keeps the LOC-221 value encounters and practitioners already reference.
@akim1995

Copy link
Copy Markdown
Contributor Author

Superseded by #73 — each dataset names its own key instead of a shared record_id.

@akim1995 akim1995 closed this Aug 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant