Immunization Project (archive)

[PHER main page]

Introduction

This is an archive page representing the first incarnation of the HL7 v3 Immunization Project. The first phase was a cross-committee effort, including external stakeholders, to define a broad "landscape" of use cases and requirements for the Immunization Domain. The project aimed to, in concert with all stakeholders, prioritize these requirements such to define an inital subset of requirements to be addressed by the first release of the v3 Immunization Domain.

Contact Information

HL7 immunization listserv

* No longer in use, immunization discussion now part of PHER list

         (view archive)

Project Leads

    Scott M Robertson, PharmD / Kaiser Permanente
    scott.m.robertson@kp.org

    Rob Savage / EDS
    SavagRB@dhfs.state.wi.us

Minutes

23 May 2006

20 June 2006

27 June 2006

11 July 2006

Project Scope Statement

Draft 06

Use Case Survey

Files

Survey Forms - Distributed to a variety of HL7 and non-HL7 groups in order to elicit as many different perspectives on the subject of Immunization

Responses - Survey responses received

Use Case Analysis Database (zipped) (history)

Process

06/26/2006 - First draft of documenting the process.

1. Consolidate Survey Results
   1. Create analysis database - Done
   2. Transcribe survey responses into database - Done
   3. Create seed lists for Actors and Use Cases - Done
   4. Demonstrate / Educate group on how to use the database - Ongoing
2. Actor Normalization(can be concurrent with Use Case Normalization)
   1. Review submitted scenarios to identify actors in each scenario. Can use actors developed from other scenarios or create new actors. Little restraint on creating new actors.
   2. Review actors to look for similarities, variations, relationships. In reviewing the derived actors, use the links back to the scenarios to assist in understanding the "intent" of the derived actor.
      1. Duplicates can be consolidated
      2. Variants should be clarified
      3. Relationships should be noted/defined
3. Use Case Normalization(can be concurrent with Actor Normalization)
   1. Review submitted scenarios to identify use case(s) in each scenario. Can use use case(s)developed from other scenarios or create new use case(s). Little restraint on creating new use case(s).
   2. Review use case(s)to look for similarities, variations, relationships. In reviewing the derived use case(s), use the links back to the scenarios to assist in understanding the "intent" of the derived use case(s).
      1. Duplicates can be consolidated
      2. Variants should be clarified
      3. Relationships should be noted/defined
4. Report on Normalized Actors and Use Cases
   1. Submit normalized Actors and Use Cases to HL7 Immunization Group for comment and prioritization
   2. Submit normalized Actors and Use Cases to survey respondants for comment and prioritaztion
   3. Established priority list for Normalized Actors and Use Cases.
5. Derive Message and Interaction requirements from Normalized Use Cases - (Process to be defined)
   1. TBD
6. Cross-reference Requirements to available HL7 v3 artefacts - (Process to be defined)
   1. TBD