FHIR IG analytics| Package | hl7.ehrs.us.dhfpr2 |
| Resource Type | Requirements |
| Id | Requirements-DHFPR2-CP.1.6.json |
| FHIR Version | R5 |
| Source | https://build.fhir.org/ig/HL7/dhfp-ig/Requirements-DHFPR2-CP.1.6.html |
| URL | http://hl7.org/ehrs/us/dhfpr2/Requirements/DHFPR2-CP.1.6 |
| Version | 2.0.0-ballot |
| Status | active |
| Date | 2025-12-19T08:44:27+00:00 |
| Name | CP_1_6_Manage_Immunization_List |
| Title | CP.1.6 Manage Immunization List (Function) |
| Realm | us |
| Authority | hl7 |
| Description | Create and maintain patient-specific immunization lists. |
| Purpose | Immunization lists are managed over time, whether over the course of a visit or stay, or the lifetime of a patient. Details of immunizations administered are captured as discrete data elements including date, type, manufacturer and lot number. The entire immunization history is viewable. Dental Note: Immunizations by dental providers may become more important as states are starting to compel them by law. There are still questions as to whether or not dental practices will need to be able to track immunizations. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Immunization lists are managed over time, whether over the course of a visit or stay, or the lifetime of a patient. Details of immunizations administered are captured as discrete data elements including date, type, manufacturer and lot number. The entire immunization history is viewable. Dental Note: Immunizations by dental providers may become more important as states are starting to compel them by law. There are still questions as to whether or not dental practices will need to be able to track immunizations.
| CP.1.6#01 | SHOULD |
The system SHOULD provide the ability to manage all immunizations associated with a patient. |
| CP.1.6#02 | SHOULD dependent |
The system SHOULD provide the ability to maintain immunization details, as discrete data, including:
|
| CP.1.6#03 | SHALL |
The system SHALL provide the ability to manage, as discrete elements, data associated with an immunization that was not given to a patient (e.g., due to a contraindication or a patient's refusal). Data associated with an immunization that was not given to a patient includes date-and-time, immunization type, series, exception reason, and immunization-withholding provider. |
| CP.1.6#04 | SHALL dependent |
The system SHALL provide the ability to render (e.g., print or transmit) a report of a patient's immunization history (e.g., for appropriate authorities such as schools, day-care centers or public health immunization registries) according to scope of practice, organizational policy, and/or jurisdictional law. |
| CP.1.6#05 | SHALL |
The system SHALL provide the ability to capture the currently recommended date for a companion immunization (e.g., a subsequent or booster dose) with each immunization (if such a companion immunization is needed). |
| CP.1.6#06 | SHALL |
The system SHALL provide the ability to capture, maintain and render population-based immunization schedules from relevant public health immunization authorities (e.g., CDC for US realm). |
FHIR
FHIRsmith{
"resourceType": "Requirements",
"id": "DHFPR2-CP.1.6",
"meta": {
"profile": [
"http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction"
]
},
"language": "en",
"text": {
"status": "extensions",
"div": "<!-- snip (see above) -->"
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode": "informative"
},
{
"url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "C"
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "ehr"
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger": 1,
"_valueInteger": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/ehrs/us/dhfpr2/ImplementationGuide/hl7.ehrs.us.dhfpr2"
}
]
}
}
],
"url": "http://hl7.org/ehrs/us/dhfpr2/Requirements/DHFPR2-CP.1.6",
"version": "2.0.0-ballot",
"name": "CP_1_6_Manage_Immunization_List",
"title": "CP.1.6 Manage Immunization List (Function)",
"status": "active",
"date": "2025-12-19T08:44:27+00:00",
"publisher": "HL7 International / Electronic Health Records",
"contact": [
{
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description": "Create and maintain patient-specific immunization lists.",
"jurisdiction": [
{
"coding": [
{
"system": "urn:iso:std:iso:3166",
"code": "US"
}
]
}
],
"purpose": "Immunization lists are managed over time, whether over the course of a visit or stay, or the lifetime of a patient. Details of immunizations administered are captured as discrete data elements including date, type, manufacturer and lot number. The entire immunization history is viewable. Dental Note: Immunizations by dental providers may become more important as states are starting to compel them by law. There are still questions as to whether or not dental practices will need to be able to track immunizations.",
"derivedFrom": [
"http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-CP.1.6"
],
"statement": [
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "DHFPR2-CP.1.6-01",
"label": "CP.1.6#01",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to manage all immunizations associated with a patient.",
"derivedFrom": "CP.1.6#1"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": true
},
{
"url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "DHFPR2-CP.1.6-02",
"label": "CP.1.6#02",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to maintain immunization details, as discrete data, including:\n- the immunization name/type, seqeunce number in the series & series identifier, strength and dose;\n- the date and time of administration;\n- manufacturer, lot number, expiration date,\n- route and site of administration;\n- administering provider;\n- observations, reactions and complications;\n- reason immunization not given, and/or immunization related activity not performed;\naccording to scope of practice, organizational policy, and/or jurisdictional law.",
"derivedFrom": "CP.1.6#2"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "DHFPR2-CP.1.6-03",
"label": "CP.1.6#03",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to manage, as discrete elements, data associated with an immunization that was not given to a patient (e.g., due to a contraindication or a patient's refusal). Data associated with an immunization that was not given to a patient includes date-and-time, immunization type, series, exception reason, and immunization-withholding provider.",
"derivedFrom": "CP.1.6#3"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": true
},
{
"url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "DHFPR2-CP.1.6-04",
"label": "CP.1.6#04",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to render (e.g., print or transmit) a report of a patient's immunization history (e.g., for appropriate authorities such as schools, day-care centers or public health immunization registries) according to scope of practice, organizational policy, and/or jurisdictional law.",
"derivedFrom": "CP.1.6#4"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "DHFPR2-CP.1.6-05",
"label": "CP.1.6#05",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to capture the currently recommended date for a companion immunization (e.g., a subsequent or booster dose) with each immunization (if such a companion immunization is needed).",
"derivedFrom": "CP.1.6#5"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "DHFPR2-CP.1.6-06",
"label": "CP.1.6#06",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to capture, maintain and render population-based immunization schedules from relevant public health immunization authorities (e.g., CDC for US realm).",
"derivedFrom": "CP.1.6#6"
}
]
}