The new draft proposed Immunization Decision Support Forecast IG is now available for review.
The format and layout are based on the current Skin Wound Assessment temporary IG . All of the current sections that are in bolded black below, existing text from the first round of balloting is in black, new sections and new content are in red have been incorporated:
- Home
Clinical Decision Support for Immunizations is increasingly being used in health information systems to indicate which vaccinations a patient is due for next. Many of these expert systems are built as stand-alone systems that respond to web service requests. While these independent systems have similar requirements and outputs they use different web service standards. This project aims to create a common FHIR implementation guide that these expert systems may use to provide a common consistent interface. This common interface will be used for two main purposes:
- Provide a common interface that health information systems may write to and gain access to their choice of CDS engines.
- Provide a common interface that may be used for testing and verifying the output of CDS engines.
From <http://hl7.org/fhir/uv/immds/2018Jan/index.html>
Add references to the people/organizations which contributed to the IG
- Guidance
Do we have general guidance to give? Is this where we talk about different ways of sending patient data (minimal demographics plus dataAbsentReason extension) versus more robust demographics)?
Is this were we discuss the meaning of "Must Support"?
List types of data (expiration date, volume, etc) that aren't required but that may improve the performance of the CDS engine
- Use Cases
Show Eric's swim lane diagrams along with a description
Note that the scope of the IG applies to all use cases
Define actors
- Profiles and Extensions
List of profiles (with links to individual pages)
Patient
Immunization - US Core
Explain why we don't use QICore - they flag several elements as Must Support that we don't think is critical to this use case
ImmunizationEvaluation - QICore (if they accept our profile proposal or our own constraint on the base resource)
Propose new QICore profile to use
ImmunizationRecommendation - base
Explain why we don't use QICore - they flag several elements as Must Support that we don't think is critical to this use case
Do we expect to have any extensions?
If we do, we need to take them back to QICore (and maybe US Core) to see if they should be unique to our IG or part of the higher profiles
- Examples (?)
Do we include examples in a separate section like this?
- Operation
OPERATION: CDS-Immunization Forecast
This is a Clinical Decision Support Immunization Forecast Request operation. It provides a standardized request and response interfaces to Immunization Forecasters.
URL: [base]/Parameters/$cds-immunization-forecast
Parameters
Use | Name | Cardinality | Type | Binding | Documentation |
IN | assessmentDate | 1..1 | The date on which to assess the forecast | ||
IN | patient | 1..1 | Patient information (only gender and birthDate) | ||
IN | immunization | 0..* | Patient immunization history | ||
OUT | Evaluation | 0..* | ImmunizationEvaluation | Evaluation against a schedule | |
OUT | recommendation | 1..1 | The CDS-Immunization engine produced forecast |
From <http://hl7.org/fhir/uv/immds/2018Jan/cdsi-operation.html>
- Terminology
Links to value sets
- Security
Do we have security considerations? Discussion about the sharing of patient demographics (see Guidance section above)?
Refer back to the US Core security considerations?
- Conformance
How are these created?
- Downloads
How are these created?