Vital Records Common Library (VRCL) FHIR Implementation Guide, published by HL7 International / Public Health. This guide is not an authorized publication; it is the continuous build for version 2.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/vr-common-library/ and changes regularly. See the Directory of published versions
Change Log
Unpublished Changes
- FHIR-49764: IJE has two distinct 2-letter codoes for unknown. The States, Territories, and Provinces Value Set has incorporated a null flavor code of UNK since its inception in VRDR STU2, but that isn't adequate to represent IJE content. This change needs to be propogated to VRDR and BFDR that reference this value set.
- FHIR-49937: IJE does not represent time zones. FHIR requires a time zone. Added a row to the usage documentation of the use of partial date times to guide usage of partial date time components for IJE conversion to FHIR.
STU 2.0 Changes
- Most of the changes since STU1.1 relate to Vital Records IG Harmonization. For a summary of harmonization-related changes see the Content Transitions page.
- Restricted data absent reasons to codes 'unknown' and 'temp-unknown' in ExtensionPartialDateVitalRecords and ExtensionPartialDateTimeVitalRecords. Added ValueSetPartialDateDataAbsentReasonVitalRecords
- Replaced local codesystem for Canadian Provinces with https://canadapost.ca/CodeSystem/ProvinceCodes
- In valueset ValueSetBirthAttendantTitlesVitalRecords replaced retired SNOMEDCT code for Medical Doctor 112247003 with active code 309343006.
- Eliminated the local code system for missing race value reasons that was used for ValueSetRaceMissingValueReasonVitalRecords. Reworked the value set and concept map with NullFlavor and ActReason codes.
- Eliminate string length limits on address extensions. Document length limits on submissions in comment.
- Eliminate Unused Extensions for Related Person (deceased, race, ethnicity). These are not needed.
- Change ExtensionPatientFetalDeathVitalRecords to be a Boolean extension of Patient.deceased
- Constrain units of parent ages – ExtensionReportedParentAgeAtDeliveryVitalRecords.
- Add abstract profile of USCoreLocation to serve as the basis for VRDR and BFDR Location profiles.
- Added record identifiers that are used in VRDR and BFDR to common library
- Renamed ValueSetMothersDateOfBirthEditFlagsVitalRecords to ValueSetDateOfBirthEditFlagsVitalRecords to generalize utility.
- Eliminated HispanicNoUknown valueset which was content-identical with ValueSetYesNoUnknownVitalRecords.
- Consolidate ValueSetBirthSexChildVitalRecords and ValueSetBirthSexFetusVitalRecords into a single VS called ValueSetSexAssignedAtBirthVitalRecords
- Use an inline extension for motherOrFather in ExtensionReportedParentAgeAtDeliveryVitalRecords
- Removing Missing Value Reason codesystem (ValueSetRaceMissingValueReasonVitalRecords uses THO codes)
- Add Domestic Partnership to ValueSetMaritalStatusVitalRecords
- Restrict birth sex for newborn to M,F,U. Added ValueSetBirthSexChildVitalRecords, and referenced from PatientChildVitalRecords
- Added abstract patient profile PatientVitalRecords, which is derived from USCorePatient, and is the basis for PatientChildVitalRecords and PatientMotherVitalRecords, as well as Patient profiles in VRDR and BFDR.
- Generalization of Parent Education Level to Education Level. ObservationEducationLevelVitalRecords now accomodates use cases in VRDR and BFDR, with subject now a generalized PatientVitalRecords, focus can now be a RelatedPersonParentVitalRecords or Mother (rather than just Mother/Father), and the addition of a bypass edit flag.
Previous Versions
See the change log in the (previous versios).