Difference between revisions of "Contraindication FHIR Resource Proposal"
| Line 45: | Line 45: | ||
The contraindication resource identifies a particular issue associated with a proposed or actual clinical action. For example, a drug-drug interaction, a procedure contraindicated based on weight or health condition, an out-of-range drug dose, etc. These may be identified by decision support systems or through human cognition. The scope includes both human and animal therapies and covers all disciplines and care environments. | The contraindication resource identifies a particular issue associated with a proposed or actual clinical action. For example, a drug-drug interaction, a procedure contraindicated based on weight or health condition, an out-of-range drug dose, etc. These may be identified by decision support systems or through human cognition. The scope includes both human and animal therapies and covers all disciplines and care environments. | ||
| − | QUESTION: should this be limited to clinical? Can administrative issues (lack of consent, permissions, etc.) fall here or is that always an OperationOutcome? | + | QUESTION: should this be limited to clinical? Can administrative issues (lack of consent, permissions, etc.) fall here or is that always an OperationOutcome? ANSWER: No, should not be limited to clinical - use wherever a persistent resource is required. OperationOutcome is not intended to be persistent, rather is a transport acknowledgment similar to HL7 v2 ack/nack. |
| + | |||
<!-- Define the full scope of coverage for the resource. The scope must be clearly delineated such that it does not overlap with any other existing or expected resource. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | <!-- Define the full scope of coverage for the resource. The scope must be clearly delineated such that it does not overlap with any other existing or expected resource. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | ||
Revision as of 17:34, 22 October 2014
This page documents a Pending FHIR Resource Proposal
Contents
- 1 Contraindication
- 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
Contraindication
Owning committee name
Clinical Decision Support Workgroup
Contributing or Reviewing Work Groups
FHIR Resource Development Project Insight ID
Pending
Scope of coverage
The contraindication resource identifies a particular issue associated with a proposed or actual clinical action. For example, a drug-drug interaction, a procedure contraindicated based on weight or health condition, an out-of-range drug dose, etc. These may be identified by decision support systems or through human cognition. The scope includes both human and animal therapies and covers all disciplines and care environments.
QUESTION: should this be limited to clinical? Can administrative issues (lack of consent, permissions, etc.) fall here or is that always an OperationOutcome? ANSWER: No, should not be limited to clinical - use wherever a persistent resource is required. OperationOutcome is not intended to be persistent, rather is a transport acknowledgment similar to HL7 v2 ack/nack.
RIM scope
Obvseration [classCode=OBS, moodCode=EVN, code <= ISSUE]
Resource appropriateness
Contraindications are a common concept in medicine, particularly in decision support. Contraindications tend to come into being as a result of some other resource, however they exist as separate structures and can be returned on their own. As well, they can have relationships to multiple resources. For example, in the case of a drug-drug interaction, the resource (prescription, dispense, etc.) for each of the two medications would be implicated and neither would have a stronger affiliation with the contraindication than the other. Therefore, the contraindication must be captured as a distinct resource.
Contraindications may be persisted and queried, though updates will be uncommon as they are typically point-in-time assessments.
Standardization of Contraindications is important for decision support purposes.
Expected implementations
- QUICK decision support/quality metric logical model
- CQF pilots including Health eDecisions
- OpenCDS (longer term)
- SocraticGrid (longer term)
- Canadian pharmacy implementations (eventually)
Content sources
- QUICK model
- v3 CMET
- OpenEHR?
- CIMI DCM models?
Example Scenarios
- Drug-drug interaction detected between a prescription and an existing medication statement
- Dose out of range by age
- Contraindicated medical procedure based on existing condition
Resource Relationships
- OperationOutcome: A rejection or warning operation outcome may include an extension linking to a Contraindication providing the clinical basis for the rejection or warning
- The various clinical resources (MedicationPrescription, AllergyIntolerance, Observation, Procedure, CarePlan, etc.) may all be triggers of a Contraindication
Timelines
At least a draft prepared for the Jan 2015 DSTU ballot
