Difference between revisions of "Retrieval for Clinical Knowledge"

From IHE Wiki
Jump to navigation Jump to search
(Created page with "The Retrieval Clinical Knowldege Profile how Health IT systems, Person Health Records, and HIEs can retrieve clinical knowledge on a topic suitable for presentation to a clini...")
 
 
(42 intermediate revisions by one other user not shown)
Line 1: Line 1:
−
The Retrieval Clinical Knowldege Profile how Health IT systems, Person Health Records, and HIEs can retrieve clinical knowledge on a topic suitable for presentation to a clinician or patient.
+
The Retrieval for Clinical Knowledge Profile describes how Health IT systems, Person Health Records, and HIEs can retrieve clinical knowledge on a topic suitable for presentation to a clinician or patient.
  
 
__TOC__
 
__TOC__
  
 
==Summary==
 
==Summary==
−
The Dynamic Care Team Management (DCTM) Profile will provide a mechanism to facilitate system interactions to support care team membership such as:
 
−
*Discovering Care Teams
 
−
*Creating/updating Care Teams
 
−
*Listing Care Teams
 
  
−
DCTM Profile provides the structures and transactions for care team management and sharing information about Care Teams that meet the needs of many, such as providers, patients and payers. Care Teams can be dynamically updated as the patient interacts with the healthcare system. A patient and providers may be associated with multiple types of care teams at any given time. This profile depicts how information about multiple care teams can be shared and used to coordinate care. The care team concepts described in this profile are patient centered with the overarching goal to support collaborative care. Care teams have many different meanings to many different people.  
+
[[File: RCK Intro Pic.jpg|250px]]
  
−
[[Image:DCTM_marketing.jpg|250px]]
+
 
 +
Each time an EHR or PHR wants to integrate with a new provider of clinical content, a new interface needs to be developed. The Retrieval for Clinical Knowledge (RCK) Profile provides a more complete implementation specification that will ensure that the same interface can be used across a wide variety of clinical content.The profile combines information presently found in standards and implementation guides from Health Level 7 International (HL7), the Internet Engineering Task Force (IETF), the World Wide Web Consortium (W3C) and IHE to describe a single interface that can be used by any system needing access to clinical content.
  
 
==Benefits==
 
==Benefits==
−
Effective collaboration and communication is needed to support the provision of patient-centered care. DCTM would enable the efficient provision of health information that is needed for effective care planning and collaboration between applicable care team members and the patient.
+
This profile provides a consistent set of rules for issuing knowledge requests for information that is either patient-, clinician- or payer-oriented, and on how to return results so that EHRs and PHRs can process the results and display them in a uniform way.
  
 
==Details==
 
==Details==
  
−
The DCTM Profile provides the structures and transactions for sharing Care Team information dynamically as the patient interacts with the healthcare system. FHIR resources and transactions are used by this profile. This profile does not define, nor assume, a single Care Team for a patient. The care team functionalities are derived from the HL7 Care Coordination Service (CCS) Functional Model  care team membership sub-capabilities.
+
There are a great number of web resources available that support access of Clinical Knowledge on a specific disease, medical condition, set of symptoms or complaints, medications, et cetera for both clinicians and patients. However, these resources have inconsistent representations of content, search APIs, and responses, making them difficult to integrate into Healthcare IT solutions. Clinical content is typically organized using different kinds of index terms. A system that wishes to locate relevant content (a Clinical Knowledge Requester) supplies the terms of interest it knows, and the system retrieving the content (a Clinical Knowledge Directory) matches these terms against the index terms it has for the clinical content. A variety of different technical approaches allow results to be ranked according to relevance and/or filtered based on content in the index terms provided.
 +
 
 +
 
 +
The Retrieve Clinical Knowledge (RCK) profile specifies the names of the different index terms that can be used to retrieve relevant content, and the range of possible values that can be used for those terms. It also places requirements upon which terms must be used in the request. Receivers of the request are free to ignore search terms that they do not use. Foreknowledge of the index terms allows content suppliers to appropriately index and or map requests into the values they use to access content. It also makes it possible for applications making requests to use a common interface, without requiring complex interface configuration to enabling discovery and mapping to index terms used by the content supplier.
  
 
==Systems Affected==
 
==Systems Affected==
−
* EHR systems may manage care teams and also contribute to other care teams.
+
* Health IT systems
−
* Patients may query, retrieve and update care teams.
+
* Personal Health Records
 +
* Healthcare Information Exchange Systems
  
 
'''Actors & Transactions:'''
 
'''Actors & Transactions:'''
  
−
* [[Care Team Contributor]]
+
* Clinical Knowledge Directory
−
* [[Care Team Service]]
+
* Clinical Knowledge Requestor
−
[[Image:DCTMactorTransactions.jpg|450px]]
+
* Clinical Knowledge Resource Repository
 +
 
 +
 
 +
[[Image:RCK Transactions.png|350px]]
  
 
==Specification==
 
==Specification==
Line 37: Line 41:
  
 
[http://ihe.net/Technical_Frameworks/#pcc IHE Patient Care Coordination Technical Framework:]
 
[http://ihe.net/Technical_Frameworks/#pcc IHE Patient Care Coordination Technical Framework:]
−
:* [http://ihe.net/uploadedFiles/Documents/PCC/IHE_PCC_Suppl_DCTM.pdf DCTM Profile]
+
:* [http://ihe.net/uploadedFiles/Documents/PCC/IHE_PCC_Suppl_RCK.pdf RCK Profile]
 +
 
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
  
−
:* [http://hl7.org/fhir/index.html HL7 FHIR]
+
:* • [Infobutton] HL7 Version 3 Standard: Context-Aware Retrieval Application (Infobutton); Release 1 [http://www.hl7.org/implement/standards/product_brief.cfm?product_id=208]
−
:* [http://www.hl7.org/implement/standards/product_brief.cfm?product_id=452 HL7 Service Functional Model: Coordination of Care Service (CCS)]
 
−
:* [http://www.hl7.org/implement/standards/product_brief.cfm?product_id=435 HL7 Care Plan Domain Analysis Model]
 
  
−
==See Also==
+
:*• [InfobuttonURL] HL7 Version 3 Implementation Guide: URL-Based Implementations of the Context-Aware Information Retrieval (Infobutton) Domain, Release 3 [http://www.hl7.org/implement/standards/product_brief.cfm?product_id=22]
  
−
'''Related Profiles'''
+
:*• [InfobuttonSOA] Context-Aware Knowledge Retrieval (Infobutton) Service Oriented Architecture Implementation Guide, Release 1 [http://www.hl7.org/implement/standards/product_brief.cfm?product_id=208]
  
−
* [[Dynamic Care Planning]] [DCP] enables care team members to share the details of their specific care plans with other providers to coordinate care.
+
:*• [Atom] RFC-4287 The Atom Syndication Format [http://tools.ietf.org/html/rfc4287]
  
−
'''Consumer Information'''
+
:*• [DC] DCMI Metadata Terms (Dublin Core) [http://dublincore.org/documents/dcmi-terms/]
  
−
The [[Profile FAQ Template]] answers typical questions about what the Profile does.  ''<Replace the link with a link to the actual FAQ page for the Profile>''
+
:*• [RFC3986] Uniform Resource Identifier (URI): Generic Syntax [http://tools.ietf.org/html/rfc3986]
  
−
The [[Profile Purchasing Template]] describes considerations when purchasing equipment to deploy this Profile.  ''<Replace the link with a link to the actual Purchasing page for the Profile>''
+
:*• [HTML4] HTML 4.01 Specification [http://www.w3.org/TR/1999/REC-html401-19991224]
  
−
'''Implementer Information'''
+
==See Also==
  
−
The [[Profile Implementation Template]] provides additional information about implementing this Profile in software.  ''<Replace the link with a link to the actual Implementation page for the Profile>''
+
'''Related Profiles'''
  
−
'''Reference Articles'''
+
* Personal Health Records (XPHR) profile
 +
* Antepartum Laboratory (APL) profile
 +
* Request Form for Data Capture (RFD) profile
  
−
''<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis).  Go ahead, Google: IHE <Profile Name> abstract  or Google: IHE <Profile Name> and under the "more" select "Scholar".  You might be surprised. >''
 
  
  
−
[[Category:Profiles]][[Category:Patient Care Coordination]]
+
[[Category:Profiles]][[Category:Patient Care Coordination]][[Category:HL7v3]]

Latest revision as of 11:46, 4 November 2019

The Retrieval for Clinical Knowledge Profile describes how Health IT systems, Person Health Records, and HIEs can retrieve clinical knowledge on a topic suitable for presentation to a clinician or patient.

Summary

RCK Intro Pic.jpg


Each time an EHR or PHR wants to integrate with a new provider of clinical content, a new interface needs to be developed. The Retrieval for Clinical Knowledge (RCK) Profile provides a more complete implementation specification that will ensure that the same interface can be used across a wide variety of clinical content.The profile combines information presently found in standards and implementation guides from Health Level 7 International (HL7), the Internet Engineering Task Force (IETF), the World Wide Web Consortium (W3C) and IHE to describe a single interface that can be used by any system needing access to clinical content.

Benefits

This profile provides a consistent set of rules for issuing knowledge requests for information that is either patient-, clinician- or payer-oriented, and on how to return results so that EHRs and PHRs can process the results and display them in a uniform way.

Details

There are a great number of web resources available that support access of Clinical Knowledge on a specific disease, medical condition, set of symptoms or complaints, medications, et cetera for both clinicians and patients. However, these resources have inconsistent representations of content, search APIs, and responses, making them difficult to integrate into Healthcare IT solutions. Clinical content is typically organized using different kinds of index terms. A system that wishes to locate relevant content (a Clinical Knowledge Requester) supplies the terms of interest it knows, and the system retrieving the content (a Clinical Knowledge Directory) matches these terms against the index terms it has for the clinical content. A variety of different technical approaches allow results to be ranked according to relevance and/or filtered based on content in the index terms provided.


The Retrieve Clinical Knowledge (RCK) profile specifies the names of the different index terms that can be used to retrieve relevant content, and the range of possible values that can be used for those terms. It also places requirements upon which terms must be used in the request. Receivers of the request are free to ignore search terms that they do not use. Foreknowledge of the index terms allows content suppliers to appropriately index and or map requests into the values they use to access content. It also makes it possible for applications making requests to use a common interface, without requiring complex interface configuration to enabling discovery and mapping to index terms used by the content supplier.

Systems Affected

  • Health IT systems
  • Personal Health Records
  • Healthcare Information Exchange Systems

Actors & Transactions:

  • Clinical Knowledge Directory
  • Clinical Knowledge Requestor
  • Clinical Knowledge Resource Repository


RCK Transactions.png

Specification

Profile Status: Trial Implementation

Documents:

IHE Patient Care Coordination Technical Framework:


Underlying Standards:

  • • [Infobutton] HL7 Version 3 Standard: Context-Aware Retrieval Application (Infobutton); Release 1 [1]
  • • [InfobuttonURL] HL7 Version 3 Implementation Guide: URL-Based Implementations of the Context-Aware Information Retrieval (Infobutton) Domain, Release 3 [2]
  • • [InfobuttonSOA] Context-Aware Knowledge Retrieval (Infobutton) Service Oriented Architecture Implementation Guide, Release 1 [3]
  • • [Atom] RFC-4287 The Atom Syndication Format [4]
  • • [DC] DCMI Metadata Terms (Dublin Core) [5]
  • • [RFC3986] Uniform Resource Identifier (URI): Generic Syntax [6]
  • • [HTML4] HTML 4.01 Specification [7]

See Also

Related Profiles

  • Personal Health Records (XPHR) profile
  • Antepartum Laboratory (APL) profile
  • Request Form for Data Capture (RFD) profile
Retrieved from "http://wiki.ihe.net/index.php?title=Retrieval_for_Clinical_Knowledge&oldid=118094"