Pain Assessment PSS

1a. Project Name Pain Assessment PSS 1b. Project ID 1585 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 Clinical Interoperability Council 2b. Co-Sponsor WG Clinical Information Modeling Initiative 2c. Co-Sponsor Level of Involvement Request formal content review prior to ballot 2b. Co-Sponsor WG 2 Patient Care 2c. Co-Sponsor Level of Involvement Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.) 2d. Project Facilitator Stan Huff 2e. Other Interested Parties (and roles) New York Presbyterian - Sarah Collins-Rossetti, Chief Nursing Informatics Officer Epic - Emily Barey, Chief Nursing Officer 2f. Modeling Facilitator Nathan Davis 2g. Publishing Facilitator Stan Huff 2h. Vocabulary Facilitator Susan Matney 2i. Domain Expert Representative 2j. Business Requirements Analyst 2k. Conformance Facilitator 2l. Other Facilitators 2m. Implementers New York Presbyterian - Sarah Collins-Rossetti, Chief Nursing Informatics Officer Epic - Emily Barey, Chief Nursing Officer University of Utah PenRad 3a. Project Scope The purpose of the project is to develop a standardized pain assessment that includes the assertion of pain and all pertinent qualifying elements such as pain severity, pain quality (burning, stabbing, aching), nonverbal pain indicator (grimacing, aggression, agitation). The qualifying elements will have LOINC codes and the associated value sets will be SNOMED CT concepts. Note that FHIR profiles and terminology bindings will conform to USCDI. 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 Westra et al 2018 ACI.pdf 3b. Project Need Pain is the most common symptom documented in healthcare. Many questions about the pain (qualifying observations) are also recorded such as pain quality, exacerbating factors, body location etc. This data needs to be standardly structured and encoded in order to gain knowledge about pain. 3c. Security Risk No 3d. External Drivers 3e. Objectives/Deliverables and Target Dates 1. Identify needed data elements and value sets used to document pain (completed by Nursing Knowledge Big Data Science Initiative) 2. Curate the needed terminology content with LOINC and SNOMED CT (LOINC complete 11/2020). 2. Develop the Clinical Element Models (Complete 7/30/2020) 3. Develop the FHIR profiles (Target 5/30/2020) 4. QA FHIR profiles within CIMI (Complete 6/30/2020) 5. Develop Implementation Guide (Complete 7/30/2020) 6. Connectathon (Sept. 2021 HL7 meeting) 7. Ballot in Jan. 2021 3f. Common Names / Keywords / Aliases: Pain Assessment 3g. Lineage 3h. Project Dependencies 3i. HL7-Managed Project Document Repository URL: https://github.com/HL7/fhir-pain-assessment-ig 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 SNOMED CT 3o. Earliest prior release and/or version to which the compatibility applies 4a. Products 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 Create new standard 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 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 Nursing Knowledge Big Data Science Initiative 6b. Content Already Developed 0 6c. Content externally developed? No 6d. List Developers of Externally Developed Content Intermountain healthcare 6e. Is this a hosted (externally funded) project? No 6f. Stakeholders Quality Reporting Agencies, Standards Development Organizations (SDOs) 6f. Other Stakeholders 6g. Vendors EHR, PHR 6g. Other Vendors 6h. Providers Emergency Services, Local and State Departments of Health, Healthcare Institutions (hospitals, long term care, home care, mental health) 6h. Other Providers 6i. Realm U.S. Realm Specific 7d. US Realm Approval Date Dec 10, 2019 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 Nov 13, 2019 7g. V2 MG Approval Date 7h. Architecture Review Board Approval Date 7i. Steering Division Approval Date Feb 04, 2020 7j. TSC Approval Date Mar 02, 2020