Difference between revisions of "Early Hearing Detection and Intervention-Workflow Document"

From IHE Wiki
Jump to navigation Jump to search
 
(23 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
This IHE Early Hearing Detection and Intervention-Workflow Definition (EHDI-WD) profile specifies a standard workflow to orchestrate the collection and exchange of data between clinical and program-specific public health information systems.  
 
This IHE Early Hearing Detection and Intervention-Workflow Definition (EHDI-WD) profile specifies a standard workflow to orchestrate the collection and exchange of data between clinical and program-specific public health information systems.  
  
 
+
Part of the [[Early Hearing Detection and Intervention - Family of Profiles]].
 
__TOC__
 
__TOC__
  
Line 31: Line 31:
 
   
 
   
 
==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.>''
 
 
* ''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:'''
 
'''Actors & Transactions:'''
Line 48: Line 43:
  
 
<center>[[Image:EHDI WD Picture 4.PNG]]</center>
 
<center>[[Image:EHDI WD Picture 4.PNG]]</center>
 +
 +
<center>[[Image:EHDI WD Picture 5.PNG]]</center>
 +
 +
<center>[[Image:EHDI WD Picture 6.PNG]]</center>
 +
 +
Figures 1-4 through 1-6 show the structure and content of the EHDI-WD Workflow Document as the tasks in the workflow are initiated and completed. Each numbered panel shows the content in the Workflow Document at a subsequent point in time. For example, Panel number 1 shows the creation of the Workflow Document which initiates the process, and then panel number 2 shows the content of the Workflow Document at the conclusion of that first task.
 +
Note: The figure is depicted in three parts due to its extended size. The panel numbers can be cross-referenced in the sequence diagram shown in figure X.4.2.1.2-1 of the EHDI-WD profile.
 +
 +
<center>[[Image:EHDI WD Picture 7.PNG]]</center>
 +
 +
<center>[[Image:EHDI WD Picture 8.PNG]]</center>
 +
 +
<center>[[Image:EHDI WD Picture 9.PNG]]</center>
 +
 +
<center>[[Image:EHDI WD Picture 10.PNG]]</center>
 +
 +
Actor Options
 +
For each workflow participant actor, EHDI-WD defines a realm-based Actor Option. The realm-based actor option is used to connect the actor with a specific type of content document for creation or consumption in that jurisdiction. The binding of specific content documents to the EHDI-WD US Realm actor options are defined in volume 4 of the profile.
 +
Table 1-4 lists the document types define by EHDI-WD.
 +
 +
 +
<center>[[Image:EHDI WD Picture 11.PNG]]</center>
 +
 +
<center>[[Image:EHDI WD Picture 12.PNG]]</center>
 +
 +
Actor Groupings
 +
Actor grouping mechanisms in a workflow definition profile are complex. Each workflow participant must be grouped with actors from the ITI XDW profile. These groupings specify each workflow participant’s capabilities for interacting with the workflow document content module. Also, each workflow participant may be grouped with actors from specific Content Profiles. The grouping with Content Profile actors provides the needed capabilities to create and consume the input and output documents that trigger the flow of information processing in a document-based workflow.
  
 
==Specification==
 
==Specification==
  
'''Profile Status:''' [[Comments| Final Text]]   
+
'''Profile Status:''' [[Comments| Trial Implementation]]   
''<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.>''
+
[http://ihe.net/uploadedFiles/Documents/PCC/IHE_PCC_Suppl_EHDI-WD.pdf IHE PCC Supplement EHDI-WD]
  
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
+
'''Underlying Standards:'''
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
 
  
'''Underlying Standards:'''
+
:* [http://ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_XDW.pdf Cross-Enterprise Document Workflow (ITI XDW)]
 +
:* [http://www.hl7.org/implement/standards/product_brief.cfm?product_id=7 HL7 Clinical Document Architecture (CDA® Release 2)]
 +
:* [http://www.hlt.org HL7 QRDA IG  July 2012]
 +
:* [http://loinc.org/ Logical Observation Identifiers Names and Codes (LOINC®)]
 +
:* [http://www.ihtsdo.org/snomed-ct/ Systematized Nomenclature Of Medicine Clinical Terms (SNOMED-CT)]
  
''<list all the standards on which the profile is based; if possible with links to sources>''
 
:* [http://dicom.nema.org DICOM]
 
:* [http://www.hl7.org HL7]
 
:* ...
 
  
 
==See Also==
 
==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'''
  
 +
* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS.b], Cross-enterprise Document Sharing Environment including
  
'''Related Profiles'''
+
* ''[[Cross-enterprise Document Reliable Interchange]] [XDR] can be used to support a reliable messaging-based infrastructure for sharing EHCP documents between sites over a network
  
''<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.>''
+
* ''[[Cross-enterprise Document Media Interchange]] [XDM] can be used to support a media-based infrastructure for sharing EHCP documents between sites over a network
  
* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
+
* ''[[Patient Identifier Cross Referencing]] [PIX], [[Patient Demographics Query]] [PDQ], [[Notification of Document Availability]] [NAV], and [[Document Metadata Subscription]] [DSUB] can be used to support a registry/repository-based infrastructure for sharing EHCP documents between sites over a network
* ''[[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.''
 
  
 +
* ''[[Consistent Time]] [CT] and [[Audit Trail and Node Authentication]] [ATNA] are used to support security and privacy when sharing the EHCP documents between sites over a network
  
'''Consumer Information'''
+
* ''[[Basic Patient Privacy Consents]] [BPPC] profile can be used to capture and communicate parental consents associated with the hearing screening workflow, and these should be included in the EHCP metadata.
  
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>''
+
* ''[[Document Digital Signature]] [DSG] can be used to assert the authoritative source of the care plan as public health.
  
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>''
+
* ''[[Sharing Value Sets]] [SVS] can be used to provide related value sets to the EHCP document
  
'''Implementer Information'''
+
'''Systems Affected '''
  
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>''
+
A system which implements the Plan of Care Manager actor, such as a Public Health EHDI Information system (EHDI-IS), Health Information Exchange system (HIE), or Electronic Health Records system (EHR), can create, consume and update EHDI-WD  Workflow Documents. They also can create and update Hearing Plan of Care documents.
  
'''Reference Articles'''
+
A system which implements the Screening Requestor actor, such as a Public Health EHDI Information system (EHDI-IS), Health Information Exchange system (HIE), or Electronic Health Records system (EHR), can consume and update EHDI-WD  Workflow Documents. They also can create Screening Outcome Reports.
  
''<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. >''
+
A system which implements the Order Placer actor, such as an integrated EHDI application or Electronic Health Records system (EHR), can consume and update EHDI-WD Workflow Documents. They also can consume Order Request documents, and create hearing screening Result Report documents.
  
 +
A system which implements the Care Summary Generator actor, such as an Electronic Health Records system (EHR), can consume and update EHDI-WD Workflow Documents. They also can create Care Summary documents.
  
  
 
This page is based on the [[Profile Overview Template]]
 
This page is based on the [[Profile Overview Template]]
 +
[[Category:Profiles]]
 +
[[Category:QRPH Profile]]
 +
[[Category:XDW]]
 +
[[Category:DocShare]]
 +
[[Category:Hearing]]

Latest revision as of 18:30, 4 November 2019

This IHE Early Hearing Detection and Intervention-Workflow Definition (EHDI-WD) profile specifies a standard workflow to orchestrate the collection and exchange of data between clinical and program-specific public health information systems.

Part of the Early Hearing Detection and Intervention - Family of Profiles.

Summary

This IHE Early Hearing Detection and Intervention-Workflow Definition (EHDI-WD) profile specifies a standard workflow to orchestrate the collection and exchange of data between clinical and program-specific public health information systems. It defines a document-based workflow where multiple systems from different organizations can participate in producing a document or set of documents which record a patient’s history of care and support care planning and decision making. The purpose of the EHDI-WD profile is to improve the way newborn hearing screening information is tracked and shared between clinical care and public health. Automation of the Hearing Plan of Care is intended to improve health outcomes for children at risk for hearing loss. The EHDI-WD profile builds upon several other IHE profiles. It utilizes actors and transactions established by the IHE ITI Cross-enterprise Document Workflow (XDW) profile. The XDW profile builds upon the document sharing mechanisms defined in the IHE ITI Cross-enterprise Document Sharing profile.

Benefits

  • Ensure that the newborn hearing screening process is performed consistently
  • Standardize screening practices and hearing care planning for all infants
  • Provide interoperability between clinical EHRs at hospitals, doctor’s offices, and EHDI programs, for increased efficiency, better data quality, and better coordination of care


Details

This IHE Early Hearing Detection and Intervention-Workflow Definition profile specifies a standard workflow which covers the period of time from birth to the point where the newborn is discharged from the birthing facility.

The EHDI-WD process, orchestrates the creation of documents by systems which contribute data used to develop a newborn’s hearing plan of care.

The EHDI-WD profile specifies the type of information that various systems must contribute, and the order in which it can be collected, in order to produce a complete and accurate hearing plan of care. The hearing plan of care includes newborn demographic information from a system that can share this data at the point of birth. It includes screening results information from a system that can communicate data generated by hearing screening devices. It includes screening outcome information from a system that can apply assessment guidelines and determine how a set of screening results are interpreted for the purpose of care planning. It also includes other data gathered a system that produces a care summary generated at the point of discharge. The EHDI-WD profile ensures that a complete and consistent hearing plan of care document is available for the infant’s primary care provider, or other specialists to receive or access.

The EHDI-WD profile specifies a Workflow Document which tracks and informs the flow of data collection and processing. The data in the EHDI Workflow Document can be utilized to efficiently monitor and analyze the hearing screening process for each newborn.

The EHDI-WD profile does not define any new transactions.


Systems Affected

Actors & Transactions:

EHDI WD Picture 1.PNG

Table 1-1 lists the workflow participant actors defined in the EHDI-WD profile.

EHDI WD Picture 2.PNG
EHDI WD Picture 3.PNG
EHDI WD Picture 4.PNG
EHDI WD Picture 5.PNG
EHDI WD Picture 6.PNG

Figures 1-4 through 1-6 show the structure and content of the EHDI-WD Workflow Document as the tasks in the workflow are initiated and completed. Each numbered panel shows the content in the Workflow Document at a subsequent point in time. For example, Panel number 1 shows the creation of the Workflow Document which initiates the process, and then panel number 2 shows the content of the Workflow Document at the conclusion of that first task. Note: The figure is depicted in three parts due to its extended size. The panel numbers can be cross-referenced in the sequence diagram shown in figure X.4.2.1.2-1 of the EHDI-WD profile.

EHDI WD Picture 7.PNG
EHDI WD Picture 8.PNG
EHDI WD Picture 9.PNG
EHDI WD Picture 10.PNG

Actor Options For each workflow participant actor, EHDI-WD defines a realm-based Actor Option. The realm-based actor option is used to connect the actor with a specific type of content document for creation or consumption in that jurisdiction. The binding of specific content documents to the EHDI-WD US Realm actor options are defined in volume 4 of the profile. Table 1-4 lists the document types define by EHDI-WD.


EHDI WD Picture 11.PNG
EHDI WD Picture 12.PNG

Actor Groupings Actor grouping mechanisms in a workflow definition profile are complex. Each workflow participant must be grouped with actors from the ITI XDW profile. These groupings specify each workflow participant’s capabilities for interacting with the workflow document content module. Also, each workflow participant may be grouped with actors from specific Content Profiles. The grouping with Content Profile actors provides the needed capabilities to create and consume the input and output documents that trigger the flow of information processing in a document-based workflow.

Specification

Profile Status: Trial Implementation

IHE PCC Supplement EHDI-WD

Underlying Standards:


See Also

Related Profiles

  • Basic Patient Privacy Consents [BPPC] profile can be used to capture and communicate parental consents associated with the hearing screening workflow, and these should be included in the EHCP metadata.

Systems Affected

A system which implements the Plan of Care Manager actor, such as a Public Health EHDI Information system (EHDI-IS), Health Information Exchange system (HIE), or Electronic Health Records system (EHR), can create, consume and update EHDI-WD Workflow Documents. They also can create and update Hearing Plan of Care documents.

A system which implements the Screening Requestor actor, such as a Public Health EHDI Information system (EHDI-IS), Health Information Exchange system (HIE), or Electronic Health Records system (EHR), can consume and update EHDI-WD Workflow Documents. They also can create Screening Outcome Reports.

A system which implements the Order Placer actor, such as an integrated EHDI application or Electronic Health Records system (EHR), can consume and update EHDI-WD Workflow Documents. They also can consume Order Request documents, and create hearing screening Result Report documents.

A system which implements the Care Summary Generator actor, such as an Electronic Health Records system (EHR), can consume and update EHDI-WD Workflow Documents. They also can create Care Summary documents.


This page is based on the Profile Overview Template