Difference between revisions of "Immunization Content"

From IHE Wiki
Jump to navigation Jump to search
 
(15 intermediate revisions by one other user not shown)
Line 10: Line 10:
  
 
==Benefits==
 
==Benefits==
−
''<If the profile can improve Cost, Safety, Quality or Efficiency then list the specific examples of that benefit (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler). Consider using a bullet list for readability. Such benefits help users and vendors make the business case for the profile. If the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>''
+
 
 +
* Participation in an Immunization Information System (IIS) automates workflows of clinicians, saving time and reducing potential for data entry errors.
 +
* Provides a "yellow card" for parents and guardians of minors, reducing friction associated with acquiring child immunization records for purposes such as school enrollment.
 +
* Availability of immunization data in a patient's Personal Health Record (PHR) account, providing opportunities for the patient to better manage their own healthcare.
 +
* Integration with an immunization forecasting service that accepts the IC document as a payload to facilitate automated immunization recommendations.
  
 
==Details==
 
==Details==
  
−
''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
+
This profile covers document-based workflows involving Content Creator and Content Consumer as well as message-based workflows utilized in clinical decision support scenarios. In the latter the Content Creator and Content Consumer actors are grouped with the Care Manager and Decision Support actors of the Request for Clinical Guidance (RCG) profile.
  
−
''<If the user might be familiar with the mechanisms used by the profile, you can mention them here.  E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>''
 
  
−
''<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short. E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>''
+
# A Care Manager Actor acquires the medical and immunization history of a patient.
−
+
# The Care Manager Actor submits the relevant portions of this medical history along with the complete immunization history to the Decision Support Service using PCC-12 Request for Clinical Guidance Transaction.
−
==Systems Affected==
+
# The Decision Support Service processes the result and returns a response to the Care Manager Actor in that same transaction.
−
''<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.>''
+
# The care manager then applies the return information. How this information is used by the care manager is out of scope of this profile.
  
−
<!--
+
[[File:ICProcessFlow.png|700px]]
−
* ''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:'''
+
==Systems Affected==
 +
* EHR Systems
 +
* Immunization Registry Systems
  
−
[[Image: PCC Share Content Diagram.png | 450px]]
 
 
==Actors==
 
==Actors==
 
* [[Content Creator]]
 
* [[Content Creator]]
 
* [[Content Consumer]]
 
* [[Content Consumer]]
 +
 +
[[Image: PCC Share Content Diagram.png | 450px]]
  
 
==Specification==
 
==Specification==
Line 41: Line 43:
  
 
'''Documents:'''  
 
'''Documents:'''  
−
 
+
[http://ihe.net/Technical_Frameworks/#pcc IHE PCC Technical Framework]
−
''<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.>''
+
:* Vol. 1 - Section 6
−
 
+
:* Vol. 2 - Section 6.3.1.10
−
<!--
 
−
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
 
−
:* [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:'''
 
'''Underlying Standards:'''
  
−
:* HL7 CDAR2
+
:* HL7 CDA Release 2.0
  
 
==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'''
 
'''Related Profiles'''
−
 
+
*[[Document Sharing]]
 
* Cross-Enterprise Document Sharing (XDS)
 
* Cross-Enterprise Document Sharing (XDS)
 
* Cross-Enterprise Reliable Document Interchange (XDR)
 
* Cross-Enterprise Reliable Document Interchange (XDR)
Line 68: Line 61:
 
* Notification of Availability (NAV)
 
* Notification of Availability (NAV)
 
* Document Digital Signature (DSG)
 
* Document Digital Signature (DSG)
−
 
−
 
−
<!--
 
−
* ''[[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'''
 
'''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. >''
+
* [http://www.iheusa.org/docs/PMASuccessStorywithIHEProfiles_000.pdf Meaningful Use Immunization Reporting Success Story: San Diego Immunization Registry]
−
 
 
  
  
 
This page is based on the [[Profile Overview Template]]
 
This page is based on the [[Profile Overview Template]]
  
−
[[Category:Template]]
+
[[Category:Profiles]]
 +
[[Category:Patient Care Coordination]]
 +
[[Category:DocShare]]
 +
[[Category:CDA]]

Latest revision as of 10:19, 30 October 2017

The Immunization Content Profile describes the content and format of documents for exchange of immunization data.

Summary

The Immunization Content Profile provides a standard document to exchange immunization data among multiple systems belonging to a single or multiple organizations. Common data formats are providing to exchange immunization data only as well as exchanging immunization data along with medical summary data to provide information to care givers that is relevant to the overall care of a patient related to immunizations. The systems between which data is shared often include Electronic Health Record systems (EHRs), Health Information Exchanges (HIEs), and Personal Health Records (PHRs).


PCC IC diagram.png

Benefits

  • Participation in an Immunization Information System (IIS) automates workflows of clinicians, saving time and reducing potential for data entry errors.
  • Provides a "yellow card" for parents and guardians of minors, reducing friction associated with acquiring child immunization records for purposes such as school enrollment.
  • Availability of immunization data in a patient's Personal Health Record (PHR) account, providing opportunities for the patient to better manage their own healthcare.
  • Integration with an immunization forecasting service that accepts the IC document as a payload to facilitate automated immunization recommendations.

Details

This profile covers document-based workflows involving Content Creator and Content Consumer as well as message-based workflows utilized in clinical decision support scenarios. In the latter the Content Creator and Content Consumer actors are grouped with the Care Manager and Decision Support actors of the Request for Clinical Guidance (RCG) profile.


  1. A Care Manager Actor acquires the medical and immunization history of a patient.
  2. The Care Manager Actor submits the relevant portions of this medical history along with the complete immunization history to the Decision Support Service using PCC-12 Request for Clinical Guidance Transaction.
  3. The Decision Support Service processes the result and returns a response to the Care Manager Actor in that same transaction.
  4. The care manager then applies the return information. How this information is used by the care manager is out of scope of this profile.

ICProcessFlow.png

Systems Affected

  • EHR Systems
  • Immunization Registry Systems

Actors

PCC Share Content Diagram.png

Specification

Profile Status: Final Text

Documents: IHE PCC Technical Framework

  • Vol. 1 - Section 6
  • Vol. 2 - Section 6.3.1.10

Underlying Standards:

  • HL7 CDA Release 2.0

See Also

Related Profiles

  • Document Sharing
  • Cross-Enterprise Document Sharing (XDS)
  • Cross-Enterprise Reliable Document Interchange (XDR)
  • Cross-Enterprise Document Media Interchange (XDM)
  • Request for Clinical Guidance (RCG)
  • Notification of Availability (NAV)
  • Document Digital Signature (DSG)

Reference Articles


This page is based on the Profile Overview Template

Retrieved from "http://wiki.ihe.net/index.php?title=Immunization_Content&oldid=105426"