HL7 FHIR Implementation Guide: Military Service History and Status Release 1 - US Realm | STU1, published by Cross Group Projects WG. This is not an authorized publication; it is the continuous build for version 1.0.0). This version is based on the current content of https://github.com/HL7/fhir-military-service/ and changes regularly. See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
These define constraints on FHIR resources for systems conforming to this implementation guide.
Deployment History Episode |
Deployment History Episode describes a completed deployment. |
Military Occupation |
The profile reuses the ODH PastOrPresentJob profile to apply it specifically to military jobs/occupations. The observation resource that conforms to this specification is referenced by Military Service Episode. |
Military Service Episode |
Military Service Episode describes a patient/veterans overall experiences of a militiary employment. The profile references military deployments and occupations as well as military branche, seperation and discharge status. A patient/Veteran may have zero or more military service episodes. The episode documents the time spent in the military organization, the dischage status and reason, and a collection of deployment episodes |
US Veteran |
US Veteran profile extends US Core Patient profile. It’s intended to be used when the patient is Veteran was confirmed by the VA. This profile includes a [‘US Veteran Status’] (usveteranstatus) extension to hold status information as a boolean (i.e. ‘true’ indicates that the patient’s veteran status was confirmed). |
These define constraints on FHIR data types for systems conforming to this implementation guide.
us-veteran-status |
us-veteran-status is a boolean extension used to specify whether a patient was confirmed or verified to have Veteran status. Veteran status is not limited to Combat Status but reflects the status of yes/no they had indeed served in a military organization |
These define sets of codes used by systems conforming to this implementation guide.
Deployment Episode Type Value Set |
Recommended deployment episode type code - only the root concept of ‘Deployment Episode’ is needed for typical implementations. |
Combat Episode Mission Value Set |
Example combat mission code; this is only an example data element that may be associated with a Deployment Episode, if needed. |
Discharge Status Value Set |
Discharge Status Value Set - this value set identifies gaps in SNOMED CT. The only concept currently supported is that of ‘dishonorable’ discharge. |
Military Branch Value Set |
Military Branch Value Set - is a subset of the ODH Occupation value set. |
Military Occupation Value Set |
Military Occupation Value Set |
Pay Grade Code Value Set |
Pay Grade Code Value Set - is a subset of the OHD Supervisory Role value set. Its scope is limited to military pay grade codes. |
Separation Reason Value Set |
Separation Reason Value Set contains concepts that are managed as a local extensions, subject to submission to SNOMED CT. |
These define new code systems used by systems conforming to this implementation guide.
Military Service History and Status Code System |
Military Service History and Status Code System |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
huffman-crystal-example-veteran |
Sam Share: Veteran’s patient record |
hugo-cross-example-veteran |
Hugo Cross: Veteran’s patient record |
philip-scott-example-deployment-history-episode |
Deployment to Vietnam |
philip-scott-example-military-occupation |
Example Military Occupation |
philip-scott-example-military-service-episode |
Military Service Episode for Veteran Example, Philip Scott |
philip-scott-example-veteran |
Phillip Scott: Veteran’s patient record |