This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "KnowledgeModule FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
 
(7 intermediate revisions by one other user not shown)
Line 7: Line 7:
 
</div>
 
</div>
 
[[Category:FHIR Resource Proposal]]
 
[[Category:FHIR Resource Proposal]]
[[Category:Pending FHIR Resource Proposal]]
 
  
  
Line 26: Line 25:
 
* Be consistent with other similar resources
 
* Be consistent with other similar resources
 
  -->
 
  -->
 +
 +
The KnowledgeModule resource provides a structure for the representation of clinical quality artifacts for decision support and quality measurement domains.
 +
 +
'''NOTE: This resource proposal has been superseded by the following more granular proposals:'''
 +
 +
*[[ModuleMetadata_FHIR_Resource_Proposal|ModuleMetadata]]
 +
*[[ModuleDefinition_FHIR_Resource_Proposal|ModuleDefinition]]
 +
*[[Library_FHIR_Resource_Proposal|Library]]
 +
*[[OrderSet_FHIR_Resource_Proposal|OrderSet]]
 +
*[[DecisionSupportServiceModule_FHIR_Resource_Proposal|DecisionSupportServiceModule]]
 +
*[[DecisionSupportRule_FHIR_Resource_Proposal|DecisionSupportRule]]
 +
*[[Measure_FHIR_Resource_Proposal|Measure]]
  
 
==Owning committee name==
 
==Owning committee name==
Line 39: Line 50:
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
  
[http://www.hl7.org/Special/committees/dss/projects.cfm?action=edit&ProjectNumber=1187 FHIR-Based Clinical Decision Support (CDS-on-FHIR)]
+
[http://www.hl7.org/Special/committees/dss/projects.cfm?action=edit&ProjectNumber=1187 1187: FHIR-Based Clinical Decision Support (CDS-on-FHIR)]
  
 
==Scope of coverage==
 
==Scope of coverage==
Line 53: Line 64:
 
As a rule, resources should encompass all of these aspects.
 
As a rule, resources should encompass all of these aspects.
 
  -->
 
  -->
 +
 +
A knowledge module is a description of a quality improvement function made available by a knowledge evaluation service. A module may correspond directly to an artifact or group of related artifacts, or it may correspond to functionality provided by the service and not necessarily associated with any tangible knowledge artifact. The knowledge module serves as the descriptive unit for functionality supported by a knowledge service such as a decision support service, measure evaluation service, or other quality improvement service.
  
 
==RIM scope==
 
==RIM scope==
Line 72: Line 85:
 
* 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, Quality Measurement, and Population Health Management are critical aspects 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 KnowledgeModule resource is to provide a standardized mechanism for representation of the logic involved in these services, as well as a mechanism for invoking them. These have been described as "Use Case 1" and "Use Case 2", respectively, of the [http://cqframework.info Clinical Quality Framework Initiative]. A more in-depth discussion of these use cases 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 101:
  
 
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=97 Health Quality Measure Format]
 +
*[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==
  
 
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource.  They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
 
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource.  They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
 +
 +
===Knowledge Sharing===
 +
The ability to programmatically share executable knowledge artifacts as described in the Clinical Decision Support Knowledge Artifact Specification.
 +
 +
===Knowledge Evaluation===
 +
The ability to programmatically request and process decision support guidance and quality measurement as described in the Decision Support Service specification and relevant HQMF-related specifications.
  
 
==Resource Relationships==
 
==Resource Relationships==
Line 97: Line 131:
 
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)
 
  -->
 
  -->
 +
 +
===Person/Organization===
 +
A KnowledgeModule may reference a person or organization as contributors, publisher, and/or steward of the module.
 +
 +
===StructureDefinition===
 +
A KnowledgeModule may reference structure definitions as part of representing the data requirements for the module.
 +
 +
===ValueSet===
 +
A KnowledgeModule may reference a value set as part of representing the data requirements for the module.
 +
 +
===GuidanceRequest/GuidanceResponse===
 +
Each GuidanceRequest and its associated GuidanceResponse will reference a single KnowledgeModule to identify the module describing the guidance being requested.
  
 
==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

Latest revision as of 22:09, 14 April 2016



KnowledgeModule

The KnowledgeModule resource provides a structure for the representation of clinical quality artifacts for decision support and quality measurement domains.

NOTE: This resource proposal has been superseded by the following more granular proposals:

Owning committee name

Clinical Decision Support Work Group

Contributing or Reviewing Work Groups

FHIR Resource Development Project Insight ID

1187: FHIR-Based Clinical Decision Support (CDS-on-FHIR)

Scope of coverage

A knowledge module is a description of a quality improvement function made available by a knowledge evaluation service. A module may correspond directly to an artifact or group of related artifacts, or it may correspond to functionality provided by the service and not necessarily associated with any tangible knowledge artifact. The knowledge module serves as the descriptive unit for functionality supported by a knowledge service such as a decision support service, measure evaluation service, or other quality improvement service.

RIM scope

Resource appropriateness

Decision Support Services, Quality Measurement, and Population Health Management are critical aspects 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 KnowledgeModule resource is to provide a standardized mechanism for representation of the logic involved in these services, as well as a mechanism for invoking them. These have been described as "Use Case 1" and "Use Case 2", respectively, of the Clinical Quality Framework Initiative. A more in-depth discussion of these use cases 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

Example Scenarios

Knowledge Sharing

The ability to programmatically share executable knowledge artifacts as described in the Clinical Decision Support Knowledge Artifact Specification.

Knowledge Evaluation

The ability to programmatically request and process decision support guidance and quality measurement as described in the Decision Support Service specification and relevant HQMF-related specifications.

Resource Relationships

Person/Organization

A KnowledgeModule may reference a person or organization as contributors, publisher, and/or steward of the module.

StructureDefinition

A KnowledgeModule may reference structure definitions as part of representing the data requirements for the module.

ValueSet

A KnowledgeModule may reference a value set as part of representing the data requirements for the module.

GuidanceRequest/GuidanceResponse

Each GuidanceRequest and its associated GuidanceResponse will reference a single KnowledgeModule to identify the module describing the guidance being requested.

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