PSS for Anaesthesia Billing Support

1a. Project Name PSS for Anaesthesia Billing Support 1b. Project ID 1550 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 Financial Management 2b. Co-Sponsor WG Anesthesia 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 MaryKay McDaniel/Ben Krahenbuhl (Epic) 2e. Other Interested Parties (and roles) 2f. Modeling Facilitator Cooper Thompson, Patrick Sullivan 2g. Publishing Facilitator 2h. Vocabulary Facilitator MaryKay McDaniel 2i. Domain Expert Representative Marc Leib, MD ASA; Karen Gehne, Anesthesia Business Consultants; Melissa Laws, ABEO 2j. Business Requirements Analyst 2k. Conformance Facilitator Rob Snelick 2l. Other Facilitators 2m. Implementers Epic Anesthesia Business Consultants (ABC) ABEO 3a. Project Scope Anaesthetist often provide their services at locations other than the anesthetist’s administrative offices. To support billing for their services clinical and administrative data from the servicing location must be gathered and provided to the Anaesthetist’s billing location. This information is currently captured by either the servicing location EMR and/or the attending Anaesthetist manually in a variety of formats. This project is to identify the information required and define a standard for its exchange. Use Case(s) Supported: Anaesthesia information from EHR to external provider billing service (could be the office of the Rendering Anaesthetist or billing service) to support billing for the anaesthetist services. Rendering anaesthetist performs service at Hospital A. The hospital bills the surgical expenses to the patient or patient’s insurer. The anaesthetist bills the patient or submits a claim to the patient’s insurer for his/her services. The anaesthetist does not provide equipment or medications. Multiple services could be provided by the anaesthetist during one surgical procedure (delivery or encounter/event). This project will: • Identify information needs (data elements) and create a Domain Analysis Model (DAM) to facilitate consistent usage across product families within HL7 • Map information model to V2.x and FHIR Resources (to help inform the information model itself) • If needed, propose updates/changes for V2.x • Create a FHIR Implementation Guide, as resources permit Attachments 3b. Project Need No existing standard has been found to meet the need of this project. This information is currently captured by either the servicing location EMR and/or the attending Anaesthetist manually in a variety of formats. This project is to identify the information required and define a standard for it’s exchange. 3c. Security Risk Unknown 3d. External Drivers 3e. Objectives/Deliverables and Target Dates ABS DAM - Jan 2020 Gap Analysis Mapping of DAM to V2.x and FHIR - Sep 2020 Potential change requests for V2.x - Jan 2021 ABS FHIR IG, as resources permit - Jan 2021 3f. Common Names / Keywords / Aliases: Anaesthesia, Billing, Billing Support 3g. Lineage 3h. Project Dependencies 3i. HL7-Managed Project Document Repository URL: https://confluence.hl7.org/display/FM/Anaesthesia+Billing+Support 3j. Backwards Compatibility No 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 Yes 3n. List of Vocabularies SNOMED, CPT, ICD-10 Possibly NUBC/NUCC Anaesthesia Billing Codes 3o. Earliest prior release and/or version to which the compatibility applies 4a. Products Domain Analysis Model (DAM), FHIR Implementation Guide, V2 Messages – Administrative, V2 Messages - Clinical, V2 Messages - Departmental 4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to? R4 4c. FHIR Profiles Version 4d. Please define your New Product Definition 4d. Please define your New Product Family 5a. Project Intent Revise current standard, 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 5d. Joint Copyright No 5e. I understand I must submit a Joint Copyright Letter of Agreement to the TSC in order for the PSS to receive TSC approval. no 6a. External Project Collaboration 6b. Content Already Developed 6c. Content externally developed? No 6d. List Developers of Externally Developed Content 6e. Is this a hosted (externally funded) project? No 6f. Stakeholders Other 6f. Other Stakeholders Billing Services 6g. Vendors EHR, PHR, HIS 6g. Other Vendors 6h. Providers Healthcare Institutions (hospitals, long term care, home care, mental health), Other 6h. Other Providers Any clinic that provides Anaesthesia services 6i. Realm U.S. Realm Specific 7d. US Realm Approval Date Dec 03, 2019 7a. Management Group(s) to Review PSS FHIR, V2 7b. Sponsoring WG Approval Date Jul 02, 2019 7c. Co-Sponsor Approval Date Jul 19, 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 Dec 04, 2019 7g. V2 MG Approval Date Nov 22, 2019 7h. Architecture Review Board Approval Date 7i. Steering Division Approval Date Oct 30, 2019 7j. TSC Approval Date Jan 06, 2020