Skip to content

docs(data-integration): templates for related_persons and social_history, several example rows each - #60

Merged
akim1995 merged 3 commits into
mainfrom
akim/data-integration-template-rows
Aug 27, 2026
Merged

docs(data-integration): templates for related_persons and social_history, several example rows each#60
akim1995 merged 3 commits into
mainfrom
akim/data-integration-template-rows

Conversation

@akim1995

@akim1995 akim1995 commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Templates for related_persons and social_history, alongside the patients one already on main. preferred_language dropped from related_persons: RelatedPerson.communication is not must-support, not uscdi-requirement, and absent from the US Core differential. Every social_history column is USCDI-backed, so none go.

Several example rows per template instead of one. Each row shows a shape worth seeing: required-only, deceased, multi-valued codes, a name change; and for social_history, one per observation_type, which is what makes industry_code visibly occupation-only.

Every code validated against its bound value set.

Corrects NCH, documented as the child relationship code but present in neither v3-RoleCode nor v2-0131. It is CHILD.

Wording: USCDI lists data classes and the elements in each; US Core maps an element onto a FHIR element. The two were used interchangeably across all 11 pages.

Drops preferred_language from related_persons: RelatedPerson.communication
is not must-support, not uscdi-requirement, and not in the US Core
differential. Every social_history column is USCDI-backed, so none go.
One row per shape worth showing: required-only, deceased, multi-valued
codes, a name change; and one per observation_type, which is what makes
industry_code visibly occupation-only.

Also corrects NCH, which is in neither v3-RoleCode nor v2-0131. The
child code is CHILD.
USCDI lists classes and the elements in each; US Core maps an element
onto a FHIR element.
@akim1995
akim1995 merged commit f7c7702 into main Aug 27, 2026
2 checks passed
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