Difference between revisions of "Guidance Response FHIR Resource Proposal"
Bryn rhodes (talk | contribs) |
Bryn rhodes (talk | contribs) |
||
| Line 26: | Line 26: | ||
* Be consistent with other similar resources | * Be consistent with other similar resources | ||
--> | --> | ||
| + | |||
| + | The GuidanceResponse resource provides a container to describe the results of a particular evaluation of a decision support artifact. | ||
==Owning committee name== | ==Owning committee name== | ||
| Line 72: | Line 74: | ||
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | * Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | ||
--> | --> | ||
| + | |||
| + | Decision Support Services are a critical aspect of healthcare delivery with numerous products in the space, both as stand-alone quality improvement services, as well as built-in rule-engine type deployments within EHRs. The focus of the GuidanceResponse resource is to provide a standardized mechanism for describing the results of an evaluation of decision support guidance. This functionality is described as Use Case 2" of the [http://cqframework.info Clinical Quality Framework Initiative]. A more in-depth discussion of this use case can be found here: [http://wiki.siframework.org/Clinical+Quality+Framework+Use+Cases Clinical Quality Framework Use Cases]. | ||
==Expected implementations== | ==Expected implementations== | ||
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | <!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | ||
| + | |||
| + | In addition to general interest from the Clinical Quality and Decision Support communities, the CQF initiative has several pilot projects in various phases of completion: | ||
| + | |||
| + | [http://wiki.siframework.org/Clinical+Quality+Framework+Pilots Clinical Quality Framework Pilots] | ||
==Content sources== | ==Content sources== | ||
| Line 82: | Line 90: | ||
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? --> | Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? --> | ||
| + | |||
| + | *[http://www.hl7.org/implement/standards/product_brief.cfm?product_id=391 Clinical Quality Common Metadata Conceptual Model] | ||
| + | *[http://www.hl7.org/implement/standards/product_brief.cfm?product_id=337 Clinical Decision Support Knowledge Artifact Specification] | ||
| + | *[http://www.hl7.org/implement/standards/product_brief.cfm?product_id=12 Decision Support Service] | ||
| + | *[http://www.hl7.org/implement/standards/product_brief.cfm?product_id=334 Decision Support Service Implementation Guide] | ||
| + | *[http://www.hl7.org/implement/standards/product_brief.cfm?product_id=208 Infobutton Specification] | ||
| + | *[http://www.hl7.org/implement/standards/product_brief.cfm?product_id=22 Infobutton Implementation Guide] | ||
| + | *[http://www.hl7.org/implement/standards/product_brief.cfm?product_id=283 SOA Infobutton Implementation Guide] | ||
==Example Scenarios== | ==Example Scenarios== | ||
| Line 97: | Line 113: | ||
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | ||
--> | --> | ||
| + | |||
| + | ===GuidanceRequest=== | ||
| + | Each GuidanceResponse will reference a single GuidanceRequest to identify the associated request. | ||
| + | |||
| + | ===KnowledgeModule=== | ||
| + | Each GuidanceResponse will reference a single KnowledgeModule to identify the artifact describing the guidance being returned. | ||
==Timelines== | ==Timelines== | ||
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | ||
| + | |||
| + | This work is being performed as part of the reconciliation of ballot comments received against the Clinical Quality Improvement Framework FHIR Implementation Guide. We hope to have the content ready in time to support the Jan 2016 FHIR Connectathon. | ||
==gForge Users== | ==gForge Users== | ||
<!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | <!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | ||
| + | |||
| + | brynrhodes | ||
Revision as of 15:47, 19 November 2015
This page documents a Pending FHIR Resource Proposal
Contents
- 1 GuidanceResponse
- 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
GuidanceResponse
The GuidanceResponse resource provides a container to describe the results of a particular evaluation of a decision support artifact.
Owning committee name
Clinical Decision Support Work Group
Contributing or Reviewing Work Groups
- Clinical Quality Information Work Group
- FHIR Management Group
- Service Oriented Architecture Work Group
FHIR Resource Development Project Insight ID
1187: FHIR-Based Clinical Decision Support (CDS-on-FHIR)
Scope of coverage
RIM scope
Resource appropriateness
Decision Support Services are a critical aspect of healthcare delivery with numerous products in the space, both as stand-alone quality improvement services, as well as built-in rule-engine type deployments within EHRs. The focus of the GuidanceResponse resource is to provide a standardized mechanism for describing the results of an evaluation of decision support guidance. This functionality is described as Use Case 2" of the Clinical Quality Framework Initiative. A more in-depth discussion of this use case can be found here: Clinical Quality Framework Use Cases.
Expected implementations
In addition to general interest from the Clinical Quality and Decision Support communities, the CQF initiative has several pilot projects in various phases of completion:
Clinical Quality Framework Pilots
Content sources
- Clinical Quality Common Metadata Conceptual Model
- Clinical Decision Support Knowledge Artifact Specification
- Decision Support Service
- Decision Support Service Implementation Guide
- Infobutton Specification
- Infobutton Implementation Guide
- SOA Infobutton Implementation Guide
Example Scenarios
Resource Relationships
GuidanceRequest
Each GuidanceResponse will reference a single GuidanceRequest to identify the associated request.
KnowledgeModule
Each GuidanceResponse will reference a single KnowledgeModule to identify the artifact describing the guidance being returned.
Timelines
This work is being performed as part of the reconciliation of ballot comments received against the Clinical Quality Improvement Framework FHIR Implementation Guide. We hope to have the content ready in time to support the Jan 2016 FHIR Connectathon.
gForge Users
brynrhodes
