This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Role codes for information recipient and other participations"
Jump to navigation
Jump to search
(New page: {{CDA R3 Open Proposals}} Return to SDTC page; Return to CDA R3 Formal Proposals page. {|width=100% cellspacing=0 cellpa...) |
|||
| (11 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | {{CDA R3 | + | {{CDA R3 Approved Proposals}} |
Return to [[Structured Documents TC|SDTC]] page; Return to [[:category:CDA R3 Formal Proposals|CDA R3 Formal Proposals]] page. | Return to [[Structured Documents TC|SDTC]] page; Return to [[:category:CDA R3 Formal Proposals|CDA R3 Formal Proposals]] page. | ||
| Line 5: | Line 5: | ||
{|width=100% cellspacing=0 cellpadding=2 border=1 | {|width=100% cellspacing=0 cellpadding=2 border=1 | ||
|| '''Submitted by:''' Ioana Singureanu | || '''Submitted by:''' Ioana Singureanu | ||
| − | || '''Revision date:''' | + | || '''Revision date:''' 12/1/2009 |
|- | |- | ||
|| '''Submitted date:''' 11/17/2009 | || '''Submitted date:''' 11/17/2009 | ||
| Line 13: | Line 13: | ||
== Issue == | == Issue == | ||
| − | Currently there is no way to specify the functional or structural role of the information recipient in the document header. This information is often required in specifying the Consent Directive or Privacy Policy. | + | Currently there is no way to specify the functional or structural role of the information recipient in the document header or the structured body. This information is often required in specifying the Consent Directive or Privacy Policy. |
| + | ===Severity: Medium === | ||
| + | '''Medium''': This is an enhancement to better support functional vs. structural roles. | ||
| + | [[Community-Based Collaborative Care|CBCC WG Wiki]] | ||
| + | == Recommendation == | ||
| − | + | * Add "functionCode" and "code" to the "informationRecipient" participations and roles in the entry. | |
| − | * Add "functionCode" | ||
| − | |||
== Rationale == | == Rationale == | ||
| Line 26: | Line 28: | ||
The item was introduced during the SDWG meeting - Nov. 17th, 2009. | The item was introduced during the SDWG meeting - Nov. 17th, 2009. | ||
The role codes may be relevant for other participations and roles. | The role codes may be relevant for other participations and roles. | ||
| + | * This item was discussed on Dec. 1st 2009 during the Security/CBCC and the WG could not decide whether to endorse it as is. The consensus seems to be that it is necessary to include the roles in the structured body entry (e.g. to specify the role of the user allowed to receive the data disclosed based on a patient's authorization) | ||
| + | * The current workaround in the structured body uses entry/organizer/participant to specify both structural and functional roles related to a specific consent directive statement. | ||
| + | <!-- Included Roles: structural and functional --> | ||
| + | <participant typeCode="IRCP"> | ||
| + | <participantRole classCode="AGNT"> | ||
| + | <code code="ATND" displayName="Attending Physician" | ||
| + | codeSystemName="HL7 HealthcareProviderRole Type" | ||
| + | codeSystem="2.16.840.1.113883.1.11.19682"/> | ||
| + | </participantRole> | ||
| + | </participant> | ||
| + | <participant typeCode="IRCP"> | ||
| + | <participantRole classCode="AGNT"> | ||
| + | <code code="RN" displayName="Registered Nurse" | ||
| + | codeSystemName="HL7HealthcareProviderRole Type" | ||
| + | codeSystem="2.16.840.1.113883.1.11.19682"/> | ||
| + | </participantRole> | ||
| + | </participant> | ||
| + | |||
| + | instead of | ||
| + | entry/act/informationRecipient/@functionRole | ||
| + | entry/act/informationRecipient/intendedRecipient/@roleCode | ||
== Recommended Action Items == | == Recommended Action Items == | ||
| Line 31: | Line 54: | ||
== Resolution == | == Resolution == | ||
| − | + | April 13, 2010: Add functionCode to all participants in header/body/section where we can come up with 3+ example codes; Add role.code to all roles in header/body/section where we can come up with 3+ example codes. Opposed: 0; Abstain: 0: In favor: 7. | |
Latest revision as of 21:36, 13 April 2010
Return to SDTC page; Return to CDA R3 Formal Proposals page.
| Submitted by: Ioana Singureanu | Revision date: 12/1/2009 |
| Submitted date: 11/17/2009 | Change request ID: <<Change Request ID>> |
Contents
Issue
Currently there is no way to specify the functional or structural role of the information recipient in the document header or the structured body. This information is often required in specifying the Consent Directive or Privacy Policy.
Severity: Medium
Medium: This is an enhancement to better support functional vs. structural roles. CBCC WG Wiki
Recommendation
- Add "functionCode" and "code" to the "informationRecipient" participations and roles in the entry.
Rationale
Needed for Consent Directive representations.
Discussion
The item was introduced during the SDWG meeting - Nov. 17th, 2009. The role codes may be relevant for other participations and roles.
- This item was discussed on Dec. 1st 2009 during the Security/CBCC and the WG could not decide whether to endorse it as is. The consensus seems to be that it is necessary to include the roles in the structured body entry (e.g. to specify the role of the user allowed to receive the data disclosed based on a patient's authorization)
- The current workaround in the structured body uses entry/organizer/participant to specify both structural and functional roles related to a specific consent directive statement.
<participant typeCode="IRCP">
<participantRole classCode="AGNT">
instead of
entry/act/informationRecipient/@functionRole entry/act/informationRecipient/intendedRecipient/@roleCode
Recommended Action Items
Resolution
April 13, 2010: Add functionCode to all participants in header/body/section where we can come up with 3+ example codes; Add role.code to all roles in header/body/section where we can come up with 3+ example codes. Opposed: 0; Abstain: 0: In favor: 7.
