Clinical Practice Guidelines Example Implementation Guide - Anthrax Post-Exposure Prophylaxis
1.1.0 - ci-build
Clinical Practice Guidelines Example Implementation Guide - Anthrax Post-Exposure Prophylaxis - Local Development build (v1.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Official URL: http://cqframework.org/cpg-example-anthrax/ImplementationGuide/cqframework.cpg-example-anthrax | Version: 1.1.0 | |||
Active as of 2024-11-18 | Computable Name: CPGExampleAnthraxPostExposure |
This README.txt file describes the contents of this software delivery. Unless otherwise noted, this software carries an Apache 2.0 license.
(c) 2019 The MITRE Corporation. All Rights Reserved. Approved for Public Release: 19-2048. Distribution Unlimited.
The examples in this section were funded by CDC Contract No. HHSM-500-2012-00008I Task Order No. 200-2016-F-89363
The contents of these directories constitute the updates made to the Anthrax Post-Exposure Prophylaxis CDS Artifact as part of Task 1 of Part 2 of the Adapting Emergency Preparedness and Response Guidelines to the Digital Age (Clinical Decision Support) project. During Part 1 of said project, an Anthrax Post-Exposure Prophylaxis CDS Artifact was developed and validated by the Health FFRDC (operated by The MITRE Corporation). The updates made to the CDS Artifact are in response to feedback regarding the desire to include the most recent Fast Healthcare Interoperability Resources (FHIR) specification and standards.
Provides information for treating patients greater than or equal to 18 years old exposed to anthrax within the past 60 days, who do not have anthrax.
For patients that may be symptomatic, the artifacts flag the need to conduct a full diagnostic evaluation to rule out anthrax before proceeding with post-exposure prophylaxis (PEP)
For patients who are asymptomatic (not displaying signs and symptoms of anthrax), the artifacts provide a recommended PEP regimen
This software delivery includes the following directories, which are each described below.
PlanDefinition: Provides example PlanDefinition FHIR resources produced by the artifact.
The cql directory contains the following subdirectories.
Each subdirectory contains versions of the following CQL libraries:
In addition, each subdirectory may contain one or more text files with version-specific information.
The artifact CQL has the ability to generate one or more alerts using the FHIR DetectedIssue resource. The DetectedIssue directory contains examples of the different types of alerts which can be generated by the CQL. The DetectedIssue directory contains the following subdirectories:
Each subdirectory should contain the FHIR resources in JSON format, as well as a text file that captures the results from validating said resources using the FHIR Validator.
The artifact CQL uses a FHIR Device resource to identify itself in the other FHIR resources that it produces. The Device directory contains the following subdirectories:
Each subdirectory should contain the FHIR resources in JSON format, as well as a text file that captures the results from validating said resources using the FHIR Validator.
The artifact CQL has the ability to generate one or more alerts using the FHIR Flag resource. The Flag directory contains examples of the different types of alerts which can be generated by the CQL. The Flag directory contains the following subdirectories:
Each subdirectory should contain the FHIR resources in JSON format, as well as a text file that captures the results from validating said resources using the FHIR Validator.
FHIR Library resources were generated using the updated artifact CQL, and act as formatted containers for the artifact and provide key information in context. The Library directory contains the following subdirectories:
Each subdirectory contains the FHIR resources in JSON format, as well as a text file that captures the results from validating said resources using the FHIR Validator. Where appropriate, the resources are also validated against the profile available at:
The artifact CQL has the ability to generate an order set using the FHIR PlanDefinition and ActivityDefinition resources (the latter or which are contained in the former). The PlanDefinition directory contains examples of the different types of order sets which can be generated by the CQL. The PlanDefinition directory contains the following subdirectories:
Each subdirectory should contain the FHIR resources in JSON format, as well as a text file that captures the results from validating said resources using the FHIR Validator. Where appropriate, the resources are also validated against the profiles available at: