Vital Signs PSS

1a. Project Name Vital Signs PSS 1b. Project ID 1541 1c. Is Your Project an Investigative Project (aka PSS-Lite)? No 1d. Is your Project Artifact being Reaffirmed or proceeding to Normative directly after being either Informative or STU? No 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 Orders & Observations 2b. Co-Sponsor WG Clinical Information Modeling Initiative 2c. Co-Sponsor Level of Involvement Other Involvement. Specify details in text box below 2c. Co-Sponsor Involvement Creation of logical models, FHIR profiles, and IG 2d. Project Facilitator Stan Huff 2e. Other Interested Parties (and roles) 2f. Modeling Facilitator Nathan Davis 2g. Publishing Facilitator Nathan Davis 2h. Vocabulary Facilitator Susan Matney 2i. Domain Expert Representative Susan Matney 2j. Business Requirements Analyst 2k. Conformance Facilitator Richard Esmond 2l. Other Facilitators Galen Mulrooney, Jay Lyle 2m. Implementers Intermountain Healthcare University of Utah American Medical Association Cerner 3a. Project Scope To create the terminology content, logical models, FHIR profiles and implementation guides for all of vital signs including all qualifying observations (patient position, body location, device, method, etc.) and coded value sets, building on the FHIR Vital Signs profile currently in place. This FHIR implementation guide will use the US Core profiles. If this FHIR implementation guide is unable to use a US Core profile we will request approval from US Realm SC, and provide the US Realm approved rationale for deviation in the implementation guide where applicable. Attachments 3b. Project Need Vital signs are collected on nearly every patient encounter. Oftentimes, the clinician needs to know the patient position, device, body location or method the measures were taken. Blood pressure as a component of vital signs also plays a key role in national efforts to control hypertension in the U.S.. This project is collaborating with the AMA in supporting the Target BP program which is focused on helping health care organizations, at no cost, improve BP control rates through an evidence-based quality improvement program and recognizes organizations committed to improving BP control, measure blood pressure accurately and enable patient self-measurement (SMBP). SMBP can also help providers better diagnose high BP and effectively manage patients. More information can be found at www.targetbp.com. The goal for this project identify the additional qualifiers, and value sets and add them encode them within the FHIR profile. 3c. Security Risk No 3d. External Drivers 3e. Objectives/Deliverables and Target Dates 1. Develop the logical model (complete) 2. Curate the needed terminology content with LOINC and SNOMED CT (complete). 3. Develop the FHIR profiles (complete) 4. QA the FHIR profile with CIMI (complete) 5. Develop the IG. (first draft complete, second draft cjomplete) http://build.fhir.org/ig/HL7/cimi-vital-signs/branches/master/profiles.html 6. Connectathon (Complete - May HL7 meeting) 7. Ballot Sept 2020 3f. Common Names / Keywords / Aliases: Vital Signs, Vital Signs profiles, Vital Signs IG 3g. Lineage 3h. Project Dependencies 3i. HL7-Managed Project Document Repository URL: https://github.com/HL7/cimi-vital-signs 3j. Backwards Compatibility No 3k. Additional Backwards Compatibility Information (if applicable) 3l. Using Current V3 Data Types? Yes 3l. Reason for not using current V3 data types? 3m. External Vocabularies Yes 3n. List of Vocabularies LOINC, UCUM, SNOMED 3o. Earliest prior release and/or version to which the compatibility applies http://build.fhir.org/ig/HL7/cimi-vital-signs/branches/master/profiles.html 4a. Products FHIR Extensions, FHIR Implementation Guide, FHIR Profiles, FHIR Resources, Logical Model 4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to? STU3, R4 4c. FHIR Profiles Version 4d. Please define your New Product Definition 4d. Please define your New Product Family 5a. Project Intent Implementation Guide (IG) will be created/modified 5a. White Paper Type 5a. Is the project adopting/endorsing an externally developed IG? No 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 Success criteria: Development of the vital signs IG that supports US Core as well as SMBP use cases that are provided by the AMA Target BP program. 5d. Joint Copyright Yes 5e. I understand I must submit a Joint Copyright Letter of Agreement to the TSC in order for the PSS to receive TSC approval. Yes 6a. External Project Collaboration Logica Intermountain Healthcare American Medical Association 6b. Content Already Developed 100% 6c. Content externally developed? No 6d. List Developers of Externally Developed Content Intermountain Healthcare, HSPC 6e. Is this a hosted (externally funded) project? No 6f. Stakeholders Clinical and Public Health Laboratories, Quality Reporting Agencies, Standards Development Organizations (SDOs) 6f. Other Stakeholders 6g. Vendors EHR, PHR, Health Care IT, Clinical Decision Support Systems, HIS 6g. Other Vendors 6h. Providers Clinical and Public Health Laboratories, Emergency Services, Healthcare Institutions (hospitals, long term care, home care, mental health) 6h. Other Providers 6i. Realm Universal 7d. US Realm Approval Date Jan 21, 2020 7a. Management Group(s) to Review PSS FHIR 7b. Sponsoring WG Approval Date May 23, 2019 7c. Co-Sponsor Approval Date May 23, 2019 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 08, 2020 7g. V2 MG Approval Date 7h. Architecture Review Board Approval Date 7i. Steering Division Approval Date Mar 13, 2020 7j. TSC Approval Date Mar 23, 2020