1a. Project Name

Military Service History and Status FHIR Profiles

1b. Project ID


1c. Is Your Project an Investigative Project (aka PSS-Lite)?


1d. Is your Project Artifact being Reaffirmed or proceeding to Normative directly after being either Informative or STU?


1e. Today's Date

1f. Name of standard being reaffirmed


1g. Project Artifact Information

1h. ISO/IEC Standard to Adopt

1i. Does the standard include excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption?

1j. Unit of Measure

2a. Primary/Sponsor WG

Cross-Group Projects

2d. Project Facilitator

Ioana Singureanu, VA

2e. Other Interested Parties (and roles)

Sean Muir, VA
Genevieve Luensman, CDC, ODH Project
Mary Kay McDaniel, Cognosante, Da Vinci Project
Craig Newman, ALTARUM
Brett Marquard, FEHRM
Nancy Orvis ?
Michelle Miller ?

2f. Modeling Facilitator

Ioana Singureanu, VA

2g. Publishing Facilitator

Sean Muir, VA

2h. Vocabulary Facilitator

Dr. Campbell (VA)

2i. Domain Expert Representative

Matt Green (VA), Genny Luensmann (CDC)

2j. Business Requirements Analyst

2k. Conformance Facilitator

Ioana Singureanu

2l. Other Facilitators

2m. Implementers


3a. Project Scope

This project is intended to create profiles (Observation resources) and extensions needed to represent military service, discharge, etc. across a diverse set of use cases: eligibility, self-reported military service information, eprior authorization information, health risks, social determinants of health, etc.
The scope of this project is to create a superset *reusable" profiles and extensions similar to Z-segments in V2. These profiles will be included in a US-realm library of profiles (e.g. US Core) such that other acceleration and implementation projects can reuse them. This project will support the ballot process required to include of Military Service History and Status


3b. Project Need

Currently there are several US Realm projects that need to use, manage, and collect information about military service, discharge, status, combat, etc. using information provided by patients/Veterans, validated based on service records.
This project will help coordinate the effort to create profiles and extensions needed to represent Military Service History, Veteran status, and associated risk factors. The collaboration outlined in this project intended to influence projects in different stages of development and provide a common representation of the data identified related to military service in a way that is consistent with each project's use cases.

3c. Security Risk


3d. External Drivers

3e. Objectives/Deliverables and Target Dates

- Use case and requirements harmonization across (March/April 2020)
- Draft FHIR Profiles (March 2020)
--- FHIR core profiles, localized US Realm profiles
- FHIR Connectathon ( May 2020)
- Ballot the profiles (depending on HL7 process requirements)
- Submit balloted profiles to FHIR US Core
- Support subsequent ballot process

3f. Common Names / Keywords / Aliases:

Military Service History, Combat, Veteran Status

3g. Lineage

3h. Project Dependencies

3i. HL7-Managed Project Document Repository URL:

Confluence: https://confluence.hl7.org/display/CGP/Military+Service+History+and+Status+FHIR+Profiles+Project+Page Github project: pending

3j. Backwards Compatibility


3k. Additional Backwards Compatibility Information (if applicable)

3l. Using Current V3 Data Types?

3l. Reason for not using current V3 data types?

3m. External Vocabularies

3n. List of Vocabularies

3o. Earliest prior release and/or version to which the compatibility applies

4a. Products

FHIR Extensions, FHIR Implementation Guide, FHIR Profiles

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?


4c. FHIR Profiles Version


4d. Please define your New Product Definition

4d. Please define your New Product Family

5a. Project Intent

Supplement to a current standard, Implementation Guide (IG) will be created/modified

5a. White Paper Type

5a. Is the project adopting/endorsing an externally developed IG?


5a. Externally developed IG is to be (select one)

5a. Specify external organization

5a. Revising Current Standard Info

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

5d. Joint Copyright


5e. I understand I must submit a Joint Copyright Letter of Agreement to the TSC in order for the PSS to receive TSC approval.


6a. External Project Collaboration

6b. Content Already Developed


6c. Content externally developed?


6d. List Developers of Externally Developed Content

6e. Is this a hosted (externally funded) project?


6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Payors

6f. Other Stakeholders

6g. Vendors

EHR, PHR, Clinical Decision Support Systems, HIS

6g. Other Vendors

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6h. Other Providers

6i. Realm

U.S. Realm Specific

7d. US Realm Approval Date

Jan 21, 2020

7a. Management Group(s) to Review PSS


7b. Sponsoring WG Approval Date

Dec 19, 2019

7c. Co-Sponsor Approval Date

7c. Co-Sponsor 2 Approval Date

7c. Co-Sponsor 3 Approval Date

7c. Co-Sponsor 4 Approval Date

7c. Co-Sponsor 5 Approval Date

7c. Co-Sponsor 6 Approval Date

7c. Co-Sponsor 7 Approval Date

7c. Co-Sponsor 8 Approval Date

7c. Co-Sponsor 9 Approval Date

7c. Co-Sponsor 10 Approval Date

7e. CDA MG Approval Date

7f. FMG Approval Date

Jan 22, 2020

7g. V2 MG Approval Date

7h. Architecture Review Board Approval Date

7i. Steering Division Approval Date

Feb 21, 2020

7j. TSC Approval Date

Mar 02, 2020