docs(data-integration): add a patients CSV template, scope the columns to USCDI - #59
Merged
Merged
Conversation
RFC 4180, so every spreadsheet opens it and it is the delivery format itself rather than a mock-up. Generated from the page's own tables, so the columns cannot drift apart.
example.org per RFC 2606, and a generic address in place of real places.
county and name_prefix are base FHIR fields US Core never mentions: not in its differential, not must-support, not uscdi-requirement.
akim1995
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A downloadable template for
patients, linked from the page.CSV rather than a spreadsheet format: RFC 4180 is an open standard, every spreadsheet opens it, and it is the delivery format the spec already describes, so the template is the real file with its header filled in rather than a mock-up. Generated from the page's own tables, so the two cannot drift.
Example data is now non-resolving.
example.orgper RFC 2606 in place ofacme.org, and a generic address in place of real streets, towns and counties. Every coded example validated against its bound value set.Two columns dropped:
countyandname_prefix. Both are base FHIR fields US Core never mentions: absent from its differential, not must-support, notuscdi-requirement. They appear in the profile's snapshot only because a snapshot inherits every base element.Left in place, though they have the same status:
patient_identifier_type,_use,_assigner_org_npi. Droppingtypewould make a member number in anidentifier_<n>_valueslot indistinguishable from any other identifier, which is a data-usefulness call rather than a conformance one.