Difference between revisions of "Quality Measure Execution-Early Hearing"
| Line 17: | Line 17: | ||
==Details== | ==Details== | ||
| − | + | The Quality Measure Execution-Early Hearing (QME-EH) content profile specifies how to use the HL7 Quality Reporting Document Architecture (QRDA) standard to implement a patient-level quality measure report for newborn hearing screening. | |
| − | + | QRDA is a specialized implementation guide (IG) for the HL7 Clinical Document Architecture standard (CDA R2). It establishes general guidelines for creating three types of CDA documents for sharing different types of quality measure reports. | |
| + | |||
| + | The QME-EH profile shows implementers how to use a supplied measure definition for newborn hearing screening, and the measure definition’s associated data set and data processing logic, to create and consume a CDA-based patient-level quality measure report. This includes: | ||
| + | *Measure Section: Each Measure Section in the report declares which measure(s) the data enclosed within the section is intended to support. Each measure section further includes: | ||
| + | *Reporting Parameters Section: Within each Measure Section, the patient-level QRDA document provides information about the reporting time interval applicable for creating or consuming the data associated with that measure or set of measures. The reporting time interval is jurisdictionally defined. This may contain other information that provides context for the patient data being reported. | ||
| + | *Patient Data Section: Within each Measure Section, the patient-level QRDA document encodes discrete data needed to process the data and execute the assessment defined for the quality measure or set of measures. | ||
| − | |||
| − | |||
==Systems Affected== | ==Systems Affected== | ||
''<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>'' | ''<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>'' | ||
Revision as of 13:16, 17 January 2014
The Quality Measure Execution-Early Hearing (QME-EH) profile describes the content needed to communicate patient-level data to electronically monitor the performance of early hearing detection and intervention (EHDI) initiatives for newborns.
Summary
The Newborn Hearing Screening measure (EHDI 1a) developed by the Centers for Disease Control and Prevention (CDC) and endorsed by the US National Quality Forum (NQF), has been selected as the sample measure for the Trial Implementation of this QME-EH profile. The EHDI- 1a measure provides patient-level information to track performance against the goal to provide hearing screening for all newborns prior to discharge from a birthing facility. Where specific US measure content is specified in this profile, realm-specific options and definitions have been used.
The Quality Measure Execution-Early Hearing (QME-EH) content profile demonstrates the use of the HL7 Quality Reporting Document Architecture (QRDA) standard to implement the patient-level quality measure report (QRDA level I) for measures specific to newborn hearing screening. QRDA establishes the general implementation guidelines for using the HL7 Clinical Document Architecture Standard (CDA R2) to create different types of quality measure reports. QME-EH constrains QRDA for measures defined for the newborn hearing screening conducted as a part of the Early Hearing Detection and Intervention (EHDI) public health program.
Benefits
- Ensure that digital newborn hearing screening quality measure data captured and communicated consistently in order to support consistent quality measure computation
- Standardize quality measurement for care of newborns born in a birthing facility
- Provide interoperability between clinical EHRs and Public Health EHDI Information Systems (EHDI-IS) for increased efficiency and better data quality
Details
The Quality Measure Execution-Early Hearing (QME-EH) content profile specifies how to use the HL7 Quality Reporting Document Architecture (QRDA) standard to implement a patient-level quality measure report for newborn hearing screening.
QRDA is a specialized implementation guide (IG) for the HL7 Clinical Document Architecture standard (CDA R2). It establishes general guidelines for creating three types of CDA documents for sharing different types of quality measure reports.
The QME-EH profile shows implementers how to use a supplied measure definition for newborn hearing screening, and the measure definition’s associated data set and data processing logic, to create and consume a CDA-based patient-level quality measure report. This includes:
- Measure Section: Each Measure Section in the report declares which measure(s) the data enclosed within the section is intended to support. Each measure section further includes:
- Reporting Parameters Section: Within each Measure Section, the patient-level QRDA document provides information about the reporting time interval applicable for creating or consuming the data associated with that measure or set of measures. The reporting time interval is jurisdictionally defined. This may contain other information that provides context for the patient data being reported.
- Patient Data Section: Within each Measure Section, the patient-level QRDA document encodes discrete data needed to process the data and execute the assessment defined for the quality measure or set of measures.
Systems Affected
<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>
- PACS systems may store, manage, and/or display Evidence Documents.
- Display systems may query, retrieve and display Evidence Documents.
- Reporting workstations may retrieve, process and include details from Evidence Documents in reports
Actors & Transactions:
<Insert an actor-transaction diagram, and or list of Content Definitions>
Specification
Profile Status: Final Text <Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>
Documents:
<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>
IHE Radiology Technical Framework:
Underlying Standards:
<list all the standards on which the profile is based; if possible with links to sources>
See Also
<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>
Related Profiles
<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>
- Reporting Workflow [RWF] may use Evidence Documents as inputs to the reporting process.
- Simple Image & Numeric Reports [SINR] may include data copied from Evidence Documents.
- Cross-enterprise Document Sharing for Imaging [XDS-I] can be used to share Evidence Documents between sites over a network.
- Portable Data for Imaging [PDI] can store Evidence Documents on media such as CDs.
- Import Reconciliation Workflow [IRWF] can fix patient ids, etc. of Evidence Documents when importing.
Consumer Information
The Profile FAQ Template answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>
The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile. <Replace the link with a link to the actual Purchasing page for the Profile>
Implementer Information
The Profile Implementation Template provides additional information about implementing this Profile in software. <Replace the link with a link to the actual Implementation page for the Profile>
Reference Articles
<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis). Go ahead, Google: IHE <Profile Name> abstract or Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >
This page is based on the Profile Overview Template