Profile for allergy intolerances relevant to immunization. The code (allergen/substance) may use SNOMED CT or ICD-10-CM. Reaction substances may use CVX, MVX, SNOMED CT, or RxNorm.

The forecast cicada returns. Constrains ImmunizationRecommendation to say which series group each recommendation belongs to, so that more than one recommendation for a single vaccine group can be told apart.

Profile for conditions where the code must be from the Vaccine Condition Codes value set. Accepts SNOMED CT and ICD-10-CM coded conditions.

Detailed information about each vaccination dose.

Profile for medical procedures related to immunization based on SNOMED CT or CPT codes.

Profile for medication administrations with vaccine codes from CVX or MVX.

Profile for medication dispenses with vaccine codes from CVX or MVX.

Profile for medication requests with vaccine codes from CVX or MVX.

Profile for medication statements with vaccine codes from CVX or MVX.

Profile for Observation resources carrying lab evidence of immunity or other findings relevant to immunization decisions. Codes may be from SNOMED CT, ICD-10-CM, or LOINC.

A profile that extends the base FHIR Patient resource to include detailed vaccination-related information.

Simple vaccine to easily obtain needed information for forecasting

Captures the reason for the allowed interval between vaccine doses.

Captures the status of the allowed interval for vaccination.

Captures the reason why a particular vaccine is allowed.

Indicates if the vaccine administered is allowed under certain conditions.

An antigen within this vaccine group that needs the forecast dose. A multi-antigen group forecasts as one recommendation, so without this a caller cannot tell whether all of MMR is due or only the measles component. Repeats, one per antigen.

The date on which the vaccination assessment was made.

The age at which the vaccine becomes applicable.

One contributing series: its own status, its own four dates, and the component dates that produced them. A vaccine group forecast reports the aggregate over several series, so without this a group covered by more than one reports a single answer for all of them, and a due date arrives with no way to see whether age or interval produced it. Repeats, one per series.

How many doses remain in the series after the one being forecast, or 'Recurring' where the series ends in a recurring dose. seriesDoses and doseNumber allow a reader to subtract, but no arithmetic says the series never ends.

The age at which the vaccine is no longer applicable.

The engine build and the CDSi supporting-data release that produced this resource. A forecast is a function of both, so a stored response naming neither cannot be traced to what produced it. Parameters is not a DomainResource and carries no extension, so the stamp sits on each evaluation and on each recommendation.

The CDSi Chapter 6 sub-step outcomes behind a dose's evaluation: which of age, interval, conflict and vaccine choice passed, and for those that failed, which rule failed. doseStatusReason carries ten ImmDS codes; the engine knows more than that.

Indicates if the vaccine was administered inadvertently.

Captures the reason for the preferred interval between vaccine doses.

Indicates if the vaccine was administered at the preferred interval.

Captures the reason why a particular vaccine is preferred.

Indicates if the vaccine administered is the preferred vaccine.

The series group this forecast is scoped to, per CDSi FORECASTVG-1. recommendation.series names the series; core FHIR has nowhere for the group.

Whether this recommendation came from the standard series group or a risk series group. Present so a client receiving two recommendations for one vaccine group can tell which pathway each describes.

The CDSi target dose status this administered dose produced.

Indicates any conflicts with other vaccinations.

Type of the vaccine.

Captures the reason why the vaccine was administered at a particular age.

Indicates if the vaccine was administered at the correct age.

Reasons a dose was reported rather than evaluated.

Forecast reasons the engine can report.

Value set for dose evaluation status reasons, referencing the published ImmDS IG StatusReason CodeSystem.

The reason for the evaluation.

Combined value set for dose evaluation status, including HL7 THO standard codes (valid, notvalid) and the Cicada extension code (extraneous).

Combined value set for immunization forecast status, referencing published standard CodeSystems. Includes ImmDS IG ForecastStatus (CDSi-compatible), HL7 THO immunization-recommendation-status, and LOINC answer list LL940-8.

RxNorm codes for medications relevant to immunization decision support, including antivirals and aspirin.

CPT codes for procedures relevant to immunization decision support, including splenectomy and cochlear implant.

This value set includes codes for the reason an interval is considered to be invalid.

LOINC codes for laboratory tests that provide evidence of immunity, mapped to CDSi observation codes for immunization decision support.

Value set for medications and substances based on SNOMED CT, including both active ingredients and marketed products.

Comprehensive Value Set for medical procedures based on SNOMED CT codes.

Reasons why certain doses are Preferred or Allowed doses

Series types a forecast can be scoped to. In practice a forecast carries standard or risk: CDSi Table 8-14 excludes Evaluation Only series from best patient series.

CDSi target dose statuses.

Value set for conditions based on SNOMED CT, that may impact immunization.

Value set for conditions based on ICD-10-CM that may impact immunization decisions, mapped to CDSi observation codes.

Value set for gender categories relevant to vaccination data.

Value set for reasons why a patient's age is considered valid/invalid for a vaccine.

Observations and Conditions that are important to indications or contraindications in vaccine forecasting

Records that cannot describe an administration. CDSi evaluates a vaccine dose administered and defines the assessment date as the current date, so these doses are excluded from evaluation and forecasting and reported in an OperationOutcome. They are statements about the data, never about the patient's immunity, which is why they are not evaluation statuses.

Extension codes for dose evaluation status beyond the HL7 THO immunization-evaluation-dose-status CodeSystem. Only codes not covered by the standard are defined here.

Why the engine forecast what it did. The ImmDS ForecastReason code system covers four of these; the rest have no ImmDS concept, and the ImmDS binding on ImmunizationRecommendation.recommendation.forecastReason is example strength, so they travel as a second coding rather than being dropped.

The reason for the evaluation.

This value set includes codes for the reason an interval is considered to be invalid.

Reasons why certain doses are Preferred or Allowed doses

CDSi series type: whether a patient series is the routine schedule, one indicated by a risk condition, or evaluation-only. Mirrors the seriesType attribute of the CDSi antigen supporting data.

CDSi Table 3-2. The status of the target dose an administered dose was evaluated against. R4 ImmunizationEvaluation carries only doseNumber, derived from this, so a skipped target dose and a satisfied one are otherwise indistinguishable.

Value set for gender categories relevant to vaccination data.

Value set for reasons why a patient's age is considered valid/invalid for a vaccine.

Define the usage of FHIR resource types with specific aliases

Maps ICD-10-CM diagnosis codes to CDSi observation codes used in immunization decision support.

Maps SNOMED CT codes to CDSi observation codes used in immunization decision support.

A resource to store supporting data for antigens including target disease, vaccine groups, immunity criteria, contraindications, and vaccination series.

This resource consolidates various mapping and conflict information related to vaccine scheduling to support decision-making processes.