Difference between revisions of "Proposal for Data Consent Query"
(New page: '''“DATA CONSENT - QUERY”''' Title : StrucDoc Proposal for Data Consent Query<br/> Version : 1.0<br/> Status : Final Proposal<br/> Date : 20080721<br/> Author : Alexander Henket, ...) |
m (→Interactions) |
||
| Line 64: | Line 64: | ||
===Interactions === | ===Interactions === | ||
| − | RCMR_IN000032: Retrieve Consents Query | + | RCMR_IN000032: Retrieve Consents Query<br/> |
| − | Transmission Wrapper: MCCI_MT000100 Send Message Payload | + | Transmission Wrapper: MCCI_MT000100 Send Message Payload<br/> |
| − | ControlAct Wrapper: QUQI_MT021001 Query By Parameter | + | ControlAct Wrapper: QUQI_MT021001 Query By Parameter<br/> |
| − | Payload MT: RCMR_MT000032 Consents Query (based on the new RMIM described in this proposal) | + | Payload MT: RCMR_MT000032 Consents Query (based on the new RMIM described in this proposal)<br/> |
| − | RCMR_IN000033: | + | RCMR_IN000033: Response to consents query by Mgt Sys<br/> |
| − | Transmission Wrapper: MCCI_MT000300 Application Level Response | + | Transmission Wrapper: MCCI_MT000300 Application Level Response<br/> |
| − | ControlAct Wrapper: QUQI_MT120001 Query Control Act Acknowledgement / Response | + | ControlAct Wrapper: QUQI_MT120001 Query Control Act Acknowledgement / Response<br/> |
| − | Payload MT: | + | Payload MT: RCMR_MT010001UV Consent<br/> |
Latest revision as of 07:34, 22 July 2008
“DATA CONSENT - QUERY”
Title : StrucDoc Proposal for Data Consent Query
Version : 1.0
Status : Final Proposal
Date : 20080721
Author : Alexander Henket, Nictiz, alexander.henket@enovation.nl
The contents of this document have been placed in the public domain. Note that the images in this document are based on HL7 Artifacts, these are © HL7 Inc.
Contents
Introduction
The Medical Records domain covers a broad area of functionality related to document management systems and includes the topic Data Consent. The domain currently only describes data consent activate/revise/delete messages, but one cannot ask a system what the current data consent is by means of a version 3 message.
This proposal describes a query, its related response, and the underlying storyboard for inclusion in the Medical Records/Structured Documents domain.
| ACKNOWLEDGEMENTS:
The development of this document was financed by (NICTIZ), the Dutch Institute for ICT in Healthcare. |
Retrieve Consent Query
Storyboard
Purpose 1
Mr. Everyman logs on to a patient portal that connects into the central hub of interconnected healthcare systems. The patient portal determines his identifier based on this login, and uses it to retrieve his consent information from the consent maintaining system. Mr. Everyman sees that he currently dissents building a centralized index of references to parts of his medical data, but consents systems to directly exchange information.
Purpose 2
Mrs. Everyman logs on to a patient portal that connects into the central hub of interconnected healthcare systems. The patient portal determines her identifier based on this login, and uses this to retrieve her consent information from the consent maintaining system. Mrs. Everyman sees that she currently does not dissent anything.
Purpose 3
Mrs. Everyman logs on to a patient portal that connects into the central hub of interconnected healthcare systems. The patient portal determines her identifier based on this login, and allows Mrs. Everyman to switch to the context of her husband Mr. Everyman. Using his and her identifier the system retrieves his consent information from the consent maintaining system. Mrs. Everyman sees that her husband currently dissents building a centralized index of references to parts of his medical data, but consents systems to directly exchange information.
Diagram
Static models
This query (a new R-MIM, RCMR_RM000032) is used to retrieve documents from a consent maintainer.
The QueryByParameter class and related classes capture information related to queries sent to a Consent Registry. You are referred to the Version 3 ballot materials for a description of the QueryByParameter and SortControl classes.
QueryByParameter has a number of associated ParameterItem classes:
SubjectPatientId: Identifies the subject that the consent directive or consent override is about.
SubjectResponsibleId: Identifies the subject that the consent directive or consent override is about, if it is not the patient.
ConsentId: Uniquely identifies a specific consent directive or consent override.
ConsentType: Uniquely the type of the consent directive or consent override, with vocabulary from the ActConsentType domain
EffectiveTime: The effective time of the requested consent directives or consent overrides should fall within the time interval specified by this parameter value.
ConsenterId: The consenting author of the requested consent should be equal to one of the authors identified by this parameter value. Only applicable where the Patient is not the Consenter.
OverriderId: The overriding author of the requested consent override should be equal to one of the authors identified by this parameter value.
ResponsiblePartyId: The responsible party for the overriding author of the requested consent override should be equal to one of the parties identified by this parameter value.
Interactions
RCMR_IN000032: Retrieve Consents Query
Transmission Wrapper: MCCI_MT000100 Send Message Payload
ControlAct Wrapper: QUQI_MT021001 Query By Parameter
Payload MT: RCMR_MT000032 Consents Query (based on the new RMIM described in this proposal)
RCMR_IN000033: Response to consents query by Mgt Sys
Transmission Wrapper: MCCI_MT000300 Application Level Response
ControlAct Wrapper: QUQI_MT120001 Query Control Act Acknowledgement / Response
Payload MT: RCMR_MT010001UV Consent
