Immunization FHIR Resource Proposal
Contents
- 1 Immunization
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
- 1.13 Issues
Immunization
Owning committee name
Public_Health_and_Emergency_Response_work_group_(PHER)
Contributing or Reviewing Work Groups
None
FHIR Resource Development Project Insight ID
967
Scope of coverage
Administration of vaccines to patients across all healthcare disciplines in all care settings and all regions. Includes immunization of both humans and animals.
Does not include the administration of non-vaccine agents, even those that may have or claim immunological effects.
RIM scope
The immunization resource corresponds to the RIM Act of Substance Administration (SBADM) as constrained in the Immunization Domain model POIZ_RM030050UV.
Resource appropriateness
The immunization resource is expected to cover key concepts related to the creation, revision and querying of a patient's immunization history. This resource - through consultation with the PHER work group - is believed to meet key use cases and information requirements as defined in the existing HL7 v2.x immunization implementation guide, HL7 v3 POIZ domain and Immunization Domain Analysis Model.
Expected implementations
TBD
Content sources
- HL7 v2.x immunization implementation guides
- Normative HL7 v3 POIZ domain
- HL7 Immunization Domain Analysis Model
Example Scenarios
Resource Relationships
This resource references the following resources:
- AdverseReaction
- Patient
- Practioner
- Location
This resource is referenced by the ImmunizationProfile resource.
Timelines
Expected to be part of the September 2013 DSTU ballot.
gForge Users
jmadra
Issues
- Is the definition of what constitutes a vaccine clearly defined? I.e. No possibility of confusion
- Need to provide specific RIM constraints. Referencing an RMIM doesn't identify what's necessary or sufficient.
- Need to fill in the "example scenarios" section