IHE FHIR Profile: Occupational Data for Health (ODH)
1.0.1-current - ci-build
IHE FHIR Profile: Occupational Data for Health (ODH), published by IHE Patient Care Coordination Committee. This guide is not an authorized publication; it is the continuous build for version 1.0.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/PCC.ODH/ and changes regularly. See the Directory of published versions
IHE welcomes New Issues from the GitHub community. For those without GitHub access, issues may be submitted to the Patient Care Coordination Public Comment form.
As issues are submitted they will be managed at Occupational Data for Health GitHub Issues, where discussion and workarounds may be found. These issues, when critical, will be processed using the normal IHE Change Proposal management and balloting.
ODH_001: Management of the ISCO-08 and ISIC Rev.4 code systems. IHE is working with HL7 to transfer the management of the ISCO08 and ISICRev4 code systems, either to HL7 Terminology (THO) or to their own code system registry.
ODH_003: ODH extensions duplicate the HL7 US Realm ODH extensions. This profile defines the Employer and Is Current Job extensions, which have the same purpose and structure as the odh-Employer-extension and odh-isCurrentJob-extension defined by the HL7 FHIR Profile: Occupational Data for Health (ODH), STU 1.3. They were duplicated intentionally so that the extensions carry no US Realm context: the HL7 extensions are published in a US Realm implementation guide that depends on US Core. IHE is still working out how international profiles should reuse HL7 US Realm work without carrying over US-only requirements, and without giving the international community the impression that a profile is US-centric because it depends on a US Realm guide. Until this is resolved, implementers exchanging data with US systems can treat the IHE and HL7 extensions as equivalent in meaning.
ODH_004: Reference targets and banned elements inherited from HL7 US ODH. The ODH Observation profiles keep the HL7 restrictions on basedOn (ServiceRequest), partOf (Procedure) and, in Past or Present Job, focus (RelatedPerson) and derivedFrom, which may be too narrow for international use. They also allow elements that the HL7 profiles prohibit (focus, bodySite, method, specimen, device, referenceRange), marking them as not recommended. See Table 4:XX-2 for the full list of differences. IHE PCC will review these constraints and coordinate any change with HL7 through a change proposal.
focus comment, inherited verbatim from the HL7 FHIR Profile: Occupational Data for Health (ODH), STU 1.3, states that focus "is used only when conveying job information of person(s) who share a home with a patient who is a child". The Past or Present Job and Usual Work descriptions likewise limit household-member use to "a minor's record".focus to identify any household member whose work is recorded in the patient's record, regardless of the patient's age, and align the focus comment and the profile descriptions with the ODH scope.focus = RelatedPerson. When HL7 resolves the issue, the resolution will be applied to this profile.section.entry by profile with the discriminator path reference.resolve(). The FHIR validator does not evaluate this path, so every entry is reported as matching all five entry slices ("Element matches more than one slice"), even when each referenced Observation conforms to exactly one HL7 US ODH Observation profile. The current HL7 continuous integration build of HL7 US ODH still uses this path. This IHE profile slices the same entries with the discriminator path resolve(), which validates correctly.section.entry discriminator path from reference.resolve() to resolve() in its next update. This is a one-line change, the same path this IHE profile uses.None.