Difference between revisions of "Immunization Registry Content"

From IHE Wiki
Jump to navigation Jump to search
m
 
(69 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
==== Data Element Index ====
+
=Introduction=
−
{{Fixme|We want to add definitions to all of the element names. Some may be self-explanatory}}
+
''This is a draft of the Immunization Registry Content Profile (IRC) supplement to the PCC Technical Framework.  This draft is a work in progress, not the official supplement or profile.''
−
{| cellspacing=0 border=1 align='center'
+
 
−
!style='background-color:#cfcfcf' |Data Elements
+
__TOC__
−
!style='background-color:#cfcfcf' |Element from Care Record Root
+
 
−
!style='background-color:#cfcfcf' |Element from POIZ Root
+
==Profile Abstract==
−
!style='background-color:#cfcfcf' |Other Reference
+
===The Immunization Content Profile (IC)===
−
|-
+
 
−
| '''Patient Elements for Immunization Content'''|| || ||
+
The Immunization Content Profile defines standard immunization data content for Immunization Information Systems (IISs), other public health systems, electronic medical records (EMR) systems, Health Information Exchanges, and others wishing to exchange immunization data electronically in a standard format.
−
|-
+
 
−
|Patient ID ||patient.id||subject.id||not required for Vaccine Decision Support
+
==Glossary==
−
|-  
+
<!--; Term : Definition-->
−
|DOB ||patient.birthTime||subject.birthTime ||only required for Vaccine Decision Support
+
 
−
|-
+
; Immunization Information System (IIS) : ''Preferred term of the American Immunization Registry Association for "Immunization Registry"''
−
|Gender ||patient.administrativeGender||subject.administrativeGender||only required for Vaccine Decision Support
+
 
−
|-
+
==Issue Log==
−
| || || ||
+
===Open Issues===
−
|-
+
Public comment is solicited on all of the following issues:
−
|'''History of Immunizations'''|| || ||
+
# In preparation for the development of this profile, the compatibility of HL7 Version 3 POIZ and CareRecord were analyzed. The standards were found to be highly compatible. A few differences were identified and referred back to the HL7 Public Health and Emergency Response (PHER) Work Group for resolution through comments on both Draft Standards for Trial Use (DSTU).  The approach taken in the Immunization Content (IC) Profile is to update the current PCC-2 Immunization Summary template to contain all the fields in POIZ that are also supported in CareRecord.  Template for Immunizations needs to be fixed to include Lot #, Manufacturer, and Expiration Date, and a few other items.  The updated template is the equivalent of a POIZ template on CareRecord. This update needs to be completed by the appropriate means.
−
|-  
+
# Template for Advanced Directives needs to be fixed to include Immunization Refusal Reasons.
−
|Immunization Record ID ||id  ||id || instance identifier
+
# It is expected that ballot comments on the CareRecord DSTU within HL7 will include requests to add elements available in POIZ but not accommodated in CareRecord.  Assuming those elements are eventually added, this IC profile will have to be updated to also include them.
−
|-  
+
# Not enough is said about precisely how the HL7 Version 2 messages are to be used. HL7 Version 2 couples content more tightly with message syntax than Verion 3. Care Management (CM) provides the notification-based integration profile, and Query for Existing Data (QED) provides a query-based integration profile for the HL7 V3 portions of this profile.  However, it is unclear how CM and QED will handle V2.  V2.3.1 messages blend identity resolution, which is outside the scope of this profile, with transmission of clinical data; how will this be handled?  Also, if a Version 2 Implementation Guide is referenced, how will updates to that document be handled?
−
|Negation Indicator ||negationInd ||negationInd ||
+
# This IC profile contains three options for each actor.  This has been thought to be problematic because two systems implementing different options may not be able to communicate.  Another approach would be to break this profile into two or even three profiles, i.e. , one for HL7 Version 2, and one or two for HL7 Version 3 (depending upon whether the Immunization Summary and Care Record options are combined).
−
|-
+
# Implementation of this profile within PCC Volumes I and II will involve a two-part exercises:  (1) update of the existing PCC-2 Immunization Summary template to reflect missing POIZ fields; and (2) creation of a new profile for the Care Record Option that includes Allergies, Problems, etc. - something that looks more like a discharge summary or a transfer of care summary, etc.
−
|Description ||text ||text  ||
+
# We assume we can use the Simple Observation template of Care Record to record Vaccine Information Statement Given (VIS Given) and VIS Version fields. Is this the best approach?
−
|-
+
 
−
|Immunization Date ||effectiveTime ||effectiveTime ||
+
 
−
|-
+
 
−
|Confidentiality Code || ||confidentialityCode || not defined in Care Record
+
===Closed Issues===
−
|-
+
# Where CareRecord and POIZ have different tags for the same elements, we have chosen to use the CareRecord tags in the templates and sample messages. The other possibility is to use the POIZ tags, which may be more meaningful to immunization domain experts. However, we felt that the POIZ tag names and definitions within the HL7 POIZ HMD were not significantly more descriptive to warrant "breaking" software that currently parses Care Record messages and may expect Care Record tags.
−
|Uncertainty Code ||||uncertaintyCode  || not defined in Care Record
+
 
−
|-
+
=Volume I=
−
|Dose Quantity ||doseQuantity.value - units||doseQuantity.value - units ||
+
<pre>Add the following bullet to the list of profiles</pre>
−
|-
+
* Immunization Content - The Immunization Content Profile defines standard immunization data content for Immunization Information Systems, other public health systems, EMR systems, Health Information Exchanges, and others wishing to exchange immunization data electronically in a standard format.
−
|Route ||routeCode ||routeCode  ||  
+
===Dependencies===
−
|-
+
<pre>Add the following row(s) to the list of dependencies</pre>
−
|Approach Site ||approachSiteCode ||approachSiteCode  ||
+
{{T|Integration Profile|Dependency|Dependency Type|Purpose|Rows=
−
|-  
+
{{R|Immunization Content (IC)|Care Management (CM)|The Content Creator actor of the IC profile must be grouped with the Clinical Data Source Actor of the CM profile|The IC profile defines the content sent in the PCC-11 transaction specified in the CM profile}}
−
|Vaccine Code ||consumable. administerableMaterial. administerableMaterial. code||consumable. administerableMedication. administerableMedicine. code || CDC CVX code in US
+
{{R|Immunization Content (IC)|Care Management (CM)|The Content Consumer actor of the IC profile must be grouped with the Care Manager Actor of the CM profile|The IC profile defines the content recieved in the PCC-11 transaction specified in the CM profile}}
−
|-  
+
{{R|Immunization Content (IC)|ATNA|Actors the IC profile shall implement the Secure Node Actor of the ATNA profile|Ensures that transmissions and changes to patient health information are logged in an audit repository, and that communication is secured between nodes.}}
−
|Vaccine Name ||consumable. administerableMaterial. administerableMaterial. name ||consumable. administerableMedication. administerableMedicine. name||
+
{{R|Immunization Content (IC)|ATNA|Actors the IC profile shall implement the Time Client Actor of the CT profile|Ensures that concistent time is used in all messages.}}
−
|-
+
}}
−
|Vaccine Lot # ||consumable. administerableMaterial. administerableMaterial. lotNumberText||consumable. administerableMedication. administerableMedicine. lotNumberText || 
+
 
−
|-
+
==The Immunization Content Profile (IC)==
−
|Vaccine Expiration Date ||consumable. administerableMaterial. administerableMaterial. expirationTime ||consumable. administerableMedication. administerableMedicine. expirationTime ||
+
The Immunization Content Profile (IC) provides a standard message, document and web service formats for exchanging immunization data. It is intended to facilitate the exchange of immunization data among multiple systems belonging to a single or to multiple organizations. Data exchange with and among the installed base of U.S. Immunization Information System (IIS) base was a critical consideration in formulating this profile. However, its intention is to go beyond data exchange among IISs, and facilitate immunization data exchange on a healthcare information network that includes electronic medical record (EMR) systems, Health Information Exchanges, other public health systems, Personal Health Record (PHR) systems, and other stakeholder systems.  Thus, the profile specifies common data formats for exchanging immunization data only, or for exchanging immunization data along with medical summary data needed for the overall care of a patient related to immunizations.
−
|-
+
 
−
|Manufacturer ID ||consumable. administerableMaterial. administerableMaterial. asMedicineManufacturer. manufacturer.id ||consumable. administerableMedication. administerableMedicine. asMedicineManufacturer. manufacturer.id  || CDC MVX code in US 
+
To accomplish this, IC draws from two HL7 Version 3 message standards:  Immunizations and Care Provision. Immunizations contains a message information model which handles detailed immunization information only. It includes history of administered vaccines with such details as lot number, who administered the shot, and so forth. Care Provision contains a message information model which handles immunization as well as other information related to the patient's care. For example, it includes medical history, medications, allergies, vital signs, and so forth. To provide for compatibility with the U.S. installed base of Immunization Information Systems (IISs), an HL7 Version 2.3.1 content option is also included.
−
|-  
+
 
−
|Manufacturer name ||consumable. administerableMaterial. administerableMaterial. asMedicineManufacturer. manufacturer. name ||consumable. administerableMedication. administerableMedicine. asMedicineManufacturer. manufacturer. name || 
+
The format of data is treated here as a separate topic from whether the data communicated in message, service, or document format, or whether an enclosing message is query-based or notification-based. By isolating content description from transaction description, the same content can be exchanged both in query and notification (unsolicited update) transaction styles, or in a service. IC is intended to be used in conjunction with integration profiles such as Query for Existing Data (QED) and Care Management (CM) to create architectures for immunization information exchange. It is also hoped that in the future, IC can be used in document-oriented profiles such as XDS.  Finally, the IC Profile is also intended to pave the way for content to be passed to immunization-related decision support services.  Decision support, however, is out of scope for the 2007-2009 IHE cycle and is on the IHE roadmap for the future.
−
|-  
+
 
−
|Vaccine Lot # Recalled Effective Date ||consumable. administerableMaterial. administerableMaterial. asMedicineManufacturer. entryRelationship. observation. effectiveTime||consumable. administerableMedication. administerableMedicine. asMedicineManufacturer. entryRelationship. observation. effectiveTime || Date Recall was effective
+
 
−
|-  
+
===Use Cases===
−
|Vaccine Lot # Recalled Code ||consumable. administerableMaterial. administerableMaterial. asMedicineManufacturer. entryRelationship. observation. code||consumable. administerableMedication. administerableMedicine. asMedicineManufacturer. entryRelationship. observation. code||SNOMED code for vaccine recalled
+
The following progression of use cases is illustrated in the drawing below.
−
|-
+
 
−
|Vaccine Lot # Recalled Noted Time ||consumable. administerableMaterial. administerableMaterial. asMedicineManufacturer. entryRelationship. observation. value||consumable. administerableMedication. administerableMedicine. asMedicineManufacturer. entryRelationship. observation. value||Date Recall was noted
+
====Use Case 1:  Immunization Information System Participation====
−
|-
+
Various provider organizations - airport flu shot clinics, storefront vaccine clinics, and hospital vaccine clinics - wish to submit immunization histories for patients to a regional Immunization Information System (IIS) with appropriate patient consent. The provider IT departments configure HL7 Verion 2.3.1 connections with the IIS. Each time immunizations are recorded, records of the administered vaccines are automatically sent to the IIS using an HL7 version 2.3.1 standard format.
−
|Adverse Event ||entryRelationship. observation. code ||entryRelationship. observation. code || 6.4.4.15.8 - Observation w/SNOMED code
+
 
−
|-
+
This is representative of the present-state use case in the U.S.
−
|Adverse Event Time ||entryRelationship. observation. effectiveTime||entryRelationship. observation. effectiveTime|| 6.4.4.15.8
+
 
−
|-  
+
====Use Case 2:  Immunization Yellow Card====
−
|Adverse Event Severity||entryRelationship. observation. entryRelationship. observation. code||entryRelationship. observation. entryRelationship. observation. code|| 6.4.4.15.8
+
A pediatrician's office produces official immunization records (sometimes called "Yellow Card") for patients. The provider electronic medical record (EMR) system retrieves demographic information and records of immunization its immunization repository. To supplement its records with immunizations that the patient may have received from other providers, it queries the regional Immunization Information System (IIS). It passes the immunization content to a software module or service that prints the information in the official Yellow Card format.
−
|-  
+
 
−
|Performer ID ||performer. assignedEntity. id ||performer. assignedEntity. id ||
+
====Use Case 3:  Personal Health Record====
−
|-
+
The provider wishes to make the assembled immunization information available in the patient's Personal Health Record (PHR). The pediatrician's office EMR system includes the retrieved immunization information in its complete care provision information about the patient. The standard Care Provision information contains current conditions, allergies and past adverse events, medications, vital signs, past medical history such as disease history, and so forth, in addition to immunizations. Knowing that the patient also has visited providers in a neighboring state, the EMR system queries the neighboring state's Health Information Exchange (HIE) to retrieve additional care provision information in a standard format. Since the neighboring state IIS is also part of the HIE, the retrieved information also includes immunizations. The pediatrician's office EMR system combines the retrieved and local information and sends it to the provider's PHR system in a standard format.
−
|Performer Name ||performer. assignedEntity. assignedPerson. name ||performer. assignedEntity. assignedPerson. name ||
+
 
−
|-
+
====Use Case 4:  Vaccine Forecast====
−
|Performer Organization ID ||performer. assignedPerson. representedOrganization. id ||performer. assignedPerson. representedOrganization. id ||
+
The pediatrician's office wishes to run an automated Vaccine Forecast Decision Support Service to calculate which vaccines due on the next visit, and to assist with reminder/recall. The service may be integrated within the EMR or may be accessed externally using a web service interface. The service accepts a standard XML-based payload in Immunization Content format. The pediatrician's EMR system submits the patients Care Provision data that it has previously assembled to the Vaccine Forecast Decision Support Service and receives a vaccine forecast care plan in return. It records the care plan and uses it in reminder/recall.
−
|-
+
 
−
|Performer Organization Name ||performer. assignedPerson. representedOrganization. name ||performer. assignedPerson. representedOrganization. name ||
+
===Actors/Transaction===
−
|-
+
There are two actors in this profile, the Content Creator and the Content Consumer. Content is created by a Content Creator and is to be consumed by a Content Consumer. The sharing or transmission of content from one actor to the other is addressed by the appropriate use of IHE profiles described below, and is out of scope of this profile. <!--A [[Document Source]] or a [[Portable Media Creator]] may embody the [[Content Creator]] Actor. A [[Document Consumer]], a [[Document Recipient]] or a [[Portable Media Importer]] may embody the [[Content Consumer]] Actor.
−
|Author ID ||author. assignedEntity. id ||author. assignedEntity. id ||
+
The sharing or transmission of content or updates from one actor to the other is addressed by the use of appropriate IHE profiles described by section 3.7 Content Bindings with XDS, XDM and XDR found in the [[Frameworks#IHE_Patient_Care_Coordination_Technical_Framework|Patient Care Coordination Technical Framework]]-->
−
|-  
+
 
−
|Author Name ||author. assignedEntity. assignedPerson. name ||author. assignedEntity. assignedPerson. name ||  
+
[[image:cccc.png|frame|center|Immunization Registry Content Actor Diagram]]
−
|-
+
 
−
|Informant Name ||informant. assignedEntity. assignedPerson. name ||informant. assignedEntity. assignedPerson. name ||  
+
=== Options ===
−
|-
+
{|style='background-color:#cfcfcf;' align='center' border='1' cellspacing='0'
−
|Informant Mode ||||informant. modeCode || written/verbal/electronic
+
!Actor
−
|-  
+
!Option
−
|Informant Source ||||informant. informationSource. code || patient/relative/provider
+
|+Immunization Content Options
−
|-
+
|- style='background-color:#ffffff;' align='center'
−
|Informant Name||informant. relatedEntity. assignedPerson. name|| || Care Record also defines options for informant by electronic data transfer
+
|Content Consumer
−
|-  
+
|No Options Defined
−
|Reason Not Administered || ||reason. noImmunizationReason. reasonCode ||  
+
|- style='background-color:#ffffff;' align='center'
−
|-  
+
|Content Creator
−
|Vaccine Information Statement Given ||observation. code ||observation. code ||
+
|Immunization Summary Option [[#note1|(1)]]<br/>
−
|-
+
Immunization Detail Option [[#note1|(1)]]<br/>
−
|VIS Version ||observation. value ||observation. value ||  
+
V2 Immunization Update Option [[#note1|(1)]]<br/>
−
|-
 
−
|Shot Comments / Notes ||annotation. text ||annotation. text ||
 
 
|}
 
|}
 +
 +
''Note <sup ID=note1>(1)</sup>: The Actor shall support at least one of these options.''
 
<br>
 
<br>
−
{| cellspacing=0 border=1 align='center'
 
−
!style='background-color:#cfcfcf' |Data Elements
 
−
!style='background-color:#cfcfcf' |Other Reference
 
−
!style='background-color:#cfcfcf' |Care Record Element
 
−
|-
 
−
| || ||
 
−
|-
 
−
| '''Existing Problem Record Data Elements''' || use as-is||templateId=1.3.6.1.4.1.19376.1.5.3.1.4.5
 
−
|-
 
−
| || || 
 
−
|-
 
−
|'''Existing Allergy and Intolerance Data Elements'''|| use as-is||templateId= 1.3.6.1.4.1.19376.1.5.3.1.4.6
 
−
|-
 
−
|Allergen Substance || substance causing allergy (allergy to eggs must be noted) ||intolerances.participant.code 
 
−
|-
 
−
|Allergic Reaction History || ||intolerances.reactions
 
−
|-
 
−
|Severity || ||intolerances.severity
 
−
|-
 
−
|Clinical Status || ||intolerances.clinicalStatus
 
−
|-
 
−
|Comments || ||intolerances.comments
 
−
|-
 
−
| || || 
 
−
|-
 
−
|'''Existing Medications Data Elements'''|| use as-is||templateId= 1.3.6.1.4.1.19376.1.5.3.1.4.7
 
−
|-
 
−
| || || 
 
−
|-
 
−
|'''Existing Simple Observations for Labs'''|| use as-is||templateId= 1.3.6.1.4.1.19376.1.5.3.1.4.13
 
−
|-
 
−
| || || 
 
−
|-
 
−
|'''Existing Vital Signs Data Elements'''|| use as-is||templateId= 1.3.6.1.4.1.19376.1.5.3.1.4.13.1 templateId= 1.3.6.1.4.1.19376.1.5.3.1.4.13.2
 
−
|-
 
−
|Observation Code || LOINC: 8310-5 body temp (must be noted if reason for not immunizing) ||vitalSigns.code 
 
−
|-
 
−
|Observation Value - Units || ||vitalSigns.value
 
−
|-
 
−
| || || 
 
−
|-
 
−
|'''Existing Pregnancy Data Elements'''|| use as-is||templateId= 1.3.6.1.4.1.19376.1.5.3.1.4.13.5
 
−
|-
 
−
| || || 
 
−
|-
 
−
|'''Existing Advanced Directives Data Elements'''|| use as-is||templateId= 1.3.6.1.4.1.19376.1.5.3.1.4.13.7
 
−
|-
 
−
|Scope (Refusal Reason Code) || <additions to list of SNOMED code(s) to include IZ Refusal Reasons> ||advanceDirectives.code
 
−
|-
 
 
<br>
 
<br>
 +
==== Immunization Summary Option ====
 +
The Immunization Summary Option is based upon HL7 Version 3.  It includes information about immunization history of a patient.
 +
==== Immunization Detail Option ====
 +
The Immunization Detail Option is also based upon HL7 Version 3.  It includes all of the requirements of the Immunization Summary Option, plus ancillary information to support decisions about the treatment of a patient related to immunizations.  For example, it includes the patient's allergies, which may be relevant in deciding whether or not to give certain vaccines.
 +
==== V2 Immunization Update Option ====
 +
The V2 Immunization Update Option is for backwards compatibility with existing HL7 Version 2.3.1 immunization messaging.
 +
 +
=== Grouping ===
 +
==== Care Management (CM) ====
 +
The [[Content Creator]] of this profile must be grouped with the [[Clinical Data Source]] of the Care Management profile.  The Clinical Data Source actor must implement the V2 Care Management Update Option.
 +
 +
The [[Content Consumer]] Actor of this profile must be grouped with the [[Care Manager]] actor of the Care Management profile.

Latest revision as of 13:37, 2 June 2008

Introduction

This is a draft of the Immunization Registry Content Profile (IRC) supplement to the PCC Technical Framework. This draft is a work in progress, not the official supplement or profile.

Profile Abstract

The Immunization Content Profile (IC)

The Immunization Content Profile defines standard immunization data content for Immunization Information Systems (IISs), other public health systems, electronic medical records (EMR) systems, Health Information Exchanges, and others wishing to exchange immunization data electronically in a standard format.

Glossary

Immunization Information System (IIS)
Preferred term of the American Immunization Registry Association for "Immunization Registry"

Issue Log

Open Issues

Public comment is solicited on all of the following issues:

  1. In preparation for the development of this profile, the compatibility of HL7 Version 3 POIZ and CareRecord were analyzed. The standards were found to be highly compatible. A few differences were identified and referred back to the HL7 Public Health and Emergency Response (PHER) Work Group for resolution through comments on both Draft Standards for Trial Use (DSTU). The approach taken in the Immunization Content (IC) Profile is to update the current PCC-2 Immunization Summary template to contain all the fields in POIZ that are also supported in CareRecord. Template for Immunizations needs to be fixed to include Lot #, Manufacturer, and Expiration Date, and a few other items. The updated template is the equivalent of a POIZ template on CareRecord. This update needs to be completed by the appropriate means.
  2. Template for Advanced Directives needs to be fixed to include Immunization Refusal Reasons.
  3. It is expected that ballot comments on the CareRecord DSTU within HL7 will include requests to add elements available in POIZ but not accommodated in CareRecord. Assuming those elements are eventually added, this IC profile will have to be updated to also include them.
  4. Not enough is said about precisely how the HL7 Version 2 messages are to be used. HL7 Version 2 couples content more tightly with message syntax than Verion 3. Care Management (CM) provides the notification-based integration profile, and Query for Existing Data (QED) provides a query-based integration profile for the HL7 V3 portions of this profile. However, it is unclear how CM and QED will handle V2. V2.3.1 messages blend identity resolution, which is outside the scope of this profile, with transmission of clinical data; how will this be handled? Also, if a Version 2 Implementation Guide is referenced, how will updates to that document be handled?
  5. This IC profile contains three options for each actor. This has been thought to be problematic because two systems implementing different options may not be able to communicate. Another approach would be to break this profile into two or even three profiles, i.e. , one for HL7 Version 2, and one or two for HL7 Version 3 (depending upon whether the Immunization Summary and Care Record options are combined).
  6. Implementation of this profile within PCC Volumes I and II will involve a two-part exercises: (1) update of the existing PCC-2 Immunization Summary template to reflect missing POIZ fields; and (2) creation of a new profile for the Care Record Option that includes Allergies, Problems, etc. - something that looks more like a discharge summary or a transfer of care summary, etc.
  7. We assume we can use the Simple Observation template of Care Record to record Vaccine Information Statement Given (VIS Given) and VIS Version fields. Is this the best approach?


Closed Issues

  1. Where CareRecord and POIZ have different tags for the same elements, we have chosen to use the CareRecord tags in the templates and sample messages. The other possibility is to use the POIZ tags, which may be more meaningful to immunization domain experts. However, we felt that the POIZ tag names and definitions within the HL7 POIZ HMD were not significantly more descriptive to warrant "breaking" software that currently parses Care Record messages and may expect Care Record tags.

Volume I

Add the following bullet to the list of profiles
  • Immunization Content - The Immunization Content Profile defines standard immunization data content for Immunization Information Systems, other public health systems, EMR systems, Health Information Exchanges, and others wishing to exchange immunization data electronically in a standard format.

Dependencies

Add the following row(s) to the list of dependencies
Integration Profile Dependency Dependency Type Purpose
Immunization Content (IC) Care Management (CM) The Content Creator actor of the IC profile must be grouped with the Clinical Data Source Actor of the CM profile The IC profile defines the content sent in the PCC-11 transaction specified in the CM profile
Immunization Content (IC) Care Management (CM) The Content Consumer actor of the IC profile must be grouped with the Care Manager Actor of the CM profile The IC profile defines the content recieved in the PCC-11 transaction specified in the CM profile
Immunization Content (IC) ATNA Actors the IC profile shall implement the Secure Node Actor of the ATNA profile Ensures that transmissions and changes to patient health information are logged in an audit repository, and that communication is secured between nodes.
Immunization Content (IC) ATNA Actors the IC profile shall implement the Time Client Actor of the CT profile Ensures that concistent time is used in all messages.

The Immunization Content Profile (IC)

The Immunization Content Profile (IC) provides a standard message, document and web service formats for exchanging immunization data. It is intended to facilitate the exchange of immunization data among multiple systems belonging to a single or to multiple organizations. Data exchange with and among the installed base of U.S. Immunization Information System (IIS) base was a critical consideration in formulating this profile. However, its intention is to go beyond data exchange among IISs, and facilitate immunization data exchange on a healthcare information network that includes electronic medical record (EMR) systems, Health Information Exchanges, other public health systems, Personal Health Record (PHR) systems, and other stakeholder systems. Thus, the profile specifies common data formats for exchanging immunization data only, or for exchanging immunization data along with medical summary data needed for the overall care of a patient related to immunizations.

To accomplish this, IC draws from two HL7 Version 3 message standards: Immunizations and Care Provision. Immunizations contains a message information model which handles detailed immunization information only. It includes history of administered vaccines with such details as lot number, who administered the shot, and so forth. Care Provision contains a message information model which handles immunization as well as other information related to the patient's care. For example, it includes medical history, medications, allergies, vital signs, and so forth. To provide for compatibility with the U.S. installed base of Immunization Information Systems (IISs), an HL7 Version 2.3.1 content option is also included.

The format of data is treated here as a separate topic from whether the data communicated in message, service, or document format, or whether an enclosing message is query-based or notification-based. By isolating content description from transaction description, the same content can be exchanged both in query and notification (unsolicited update) transaction styles, or in a service. IC is intended to be used in conjunction with integration profiles such as Query for Existing Data (QED) and Care Management (CM) to create architectures for immunization information exchange. It is also hoped that in the future, IC can be used in document-oriented profiles such as XDS. Finally, the IC Profile is also intended to pave the way for content to be passed to immunization-related decision support services. Decision support, however, is out of scope for the 2007-2009 IHE cycle and is on the IHE roadmap for the future.


Use Cases

The following progression of use cases is illustrated in the drawing below.

Use Case 1: Immunization Information System Participation

Various provider organizations - airport flu shot clinics, storefront vaccine clinics, and hospital vaccine clinics - wish to submit immunization histories for patients to a regional Immunization Information System (IIS) with appropriate patient consent. The provider IT departments configure HL7 Verion 2.3.1 connections with the IIS. Each time immunizations are recorded, records of the administered vaccines are automatically sent to the IIS using an HL7 version 2.3.1 standard format.

This is representative of the present-state use case in the U.S.

Use Case 2: Immunization Yellow Card

A pediatrician's office produces official immunization records (sometimes called "Yellow Card") for patients. The provider electronic medical record (EMR) system retrieves demographic information and records of immunization its immunization repository. To supplement its records with immunizations that the patient may have received from other providers, it queries the regional Immunization Information System (IIS). It passes the immunization content to a software module or service that prints the information in the official Yellow Card format.

Use Case 3: Personal Health Record

The provider wishes to make the assembled immunization information available in the patient's Personal Health Record (PHR). The pediatrician's office EMR system includes the retrieved immunization information in its complete care provision information about the patient. The standard Care Provision information contains current conditions, allergies and past adverse events, medications, vital signs, past medical history such as disease history, and so forth, in addition to immunizations. Knowing that the patient also has visited providers in a neighboring state, the EMR system queries the neighboring state's Health Information Exchange (HIE) to retrieve additional care provision information in a standard format. Since the neighboring state IIS is also part of the HIE, the retrieved information also includes immunizations. The pediatrician's office EMR system combines the retrieved and local information and sends it to the provider's PHR system in a standard format.

Use Case 4: Vaccine Forecast

The pediatrician's office wishes to run an automated Vaccine Forecast Decision Support Service to calculate which vaccines due on the next visit, and to assist with reminder/recall. The service may be integrated within the EMR or may be accessed externally using a web service interface. The service accepts a standard XML-based payload in Immunization Content format. The pediatrician's EMR system submits the patients Care Provision data that it has previously assembled to the Vaccine Forecast Decision Support Service and receives a vaccine forecast care plan in return. It records the care plan and uses it in reminder/recall.

Actors/Transaction

There are two actors in this profile, the Content Creator and the Content Consumer. Content is created by a Content Creator and is to be consumed by a Content Consumer. The sharing or transmission of content from one actor to the other is addressed by the appropriate use of IHE profiles described below, and is out of scope of this profile.

Immunization Registry Content Actor Diagram

Options

Actor Option
Immunization Content Options
Content Consumer No Options Defined
Content Creator Immunization Summary Option (1)

Immunization Detail Option (1)
V2 Immunization Update Option (1)

Note (1): The Actor shall support at least one of these options.

Immunization Summary Option

The Immunization Summary Option is based upon HL7 Version 3. It includes information about immunization history of a patient.

Immunization Detail Option

The Immunization Detail Option is also based upon HL7 Version 3. It includes all of the requirements of the Immunization Summary Option, plus ancillary information to support decisions about the treatment of a patient related to immunizations. For example, it includes the patient's allergies, which may be relevant in deciding whether or not to give certain vaccines.

V2 Immunization Update Option

The V2 Immunization Update Option is for backwards compatibility with existing HL7 Version 2.3.1 immunization messaging.

Grouping

Care Management (CM)

The Content Creator of this profile must be grouped with the Clinical Data Source of the Care Management profile. The Clinical Data Source actor must implement the V2 Care Management Update Option.

The Content Consumer Actor of this profile must be grouped with the Care Manager actor of the Care Management profile.

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