This wiki has undergone a migration to Confluence found Here

Difference between revisions of "CDS on FHIR"

From HL7Wiki
Jump to navigation Jump to search
Line 24: Line 24:
  
 
Contraindication
 
Contraindication
- Should the name be something that allows non-true contraindications (e.g., interaction warnings)?  E.g., Warning, or ContraindicationOrWarning.  The severity attribute may be able to deal with this (e.g., absolute vs. relative contraindication).
+
 
 +
Should the name be something that allows non-true contraindications (e.g., interaction warnings)?  E.g., Warning, or ContraindicationOrWarning.  The severity attribute may be able to deal with this (e.g., absolute vs. relative contraindication).
 +
 
 +
What is the use case for this Resource?

Revision as of 19:46, 11 June 2015

Return to Clinical Decision Support Work Group

Project Co-Sponsors:

Project Information

This project will investigate the use of FHIR in a Clinical Decision Support context with the goal of identifying best practices for the use of FHIR in support of the primary use cases of Clinical Decision Support, namely 1) Sharing Clinical Decision Support (CDS) knowledge artifacts, and 2) Obtaining Clinical Decision Support guidance as part of a clinical workflow.

Meeting Information

The CDS on FHIR project subteam meets weekly: Conference call coordinates

Status

The Project Scope Statement for this project has been approved by the primary and co-sponsoring work groups and submitted to HL7.

Project Documents

FHIR-Based CDS Proposed Approach Slides - File:FHIR-Based CDS.pptx


Potential Issues Identified for FHIR Resources to be Officially Balloted in the Future

Contraindication

Should the name be something that allows non-true contraindications (e.g., interaction warnings)? E.g., Warning, or ContraindicationOrWarning. The severity attribute may be able to deal with this (e.g., absolute vs. relative contraindication).

What is the use case for this Resource?