This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Consent Tracker FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 57: Line 57:
 
As a rule, resources should encompass all of these aspects.
 
As a rule, resources should encompass all of these aspects.
 
  -->
 
  -->
==Consent Tracker Scope of Coverage==
+
==='''Consent Tracker Scope of''' Coverage===
  
 
*The proposed Consent Tracker Resource is intended to meet a very basic yet unique healthcare domain business requirement, which is to convey the minimal set of consent directive metadata that has been used by the industry to manage consent directive workflow and access control.
 
*The proposed Consent Tracker Resource is intended to meet a very basic yet unique healthcare domain business requirement, which is to convey the minimal set of consent directive metadata that has been used by the industry to manage consent directive workflow and access control.

Revision as of 21:24, 1 June 2016



Consent Tracter

Owning committee name

Community-Based Collaborative Care

Committee Approval Date:

May 31, 2016

Approved during the May 31, 2016 CBCC Conference Call

Contributing or Reviewing Work Groups

FHIR Resource Development Project Insight ID

pending - reminder sent to CBCC cochairs June 1, 2016

Scope of coverage

Consent Tracker Scope of Coverage

  • The proposed Consent Tracker Resource is intended to meet a very basic yet unique healthcare domain business requirement, which is to convey the minimal set of consent directive metadata that has been used by the industry to manage consent directive workflow and access control.
  • The Consent Tracker Resource elements were selected based on mapping several current approaches to conveying consent directive metadata including:
    • v2 CON Medical Records Consent Segment;
    • v2 MDM/ACK - Document Status Change Notification (Event T03)
    • ADT ARV-3 Access Restriction Value;
    • OM 1-30 Master Files General Observations Confidentiality Code;
    • ORC-28 Common Order Segment Confidentiality Code;
    • Financial Management DG1-18 Confidential Indicator and DRG-10 Confidential Indicator; **eClaims EHC^E12 Request Additional Information (event E12) and EHC^E13 Additional Information Response (event E13)

Consent Tracker Breath of Scope

Consent Tracker scope, as listed below, is constrained during implementation to applicable policies. I.e., in some jurisdictions, there may be no opportunity for a patient to consent or dissent to uses of information or activities performed, either because there is no express consent or consent is implied/assumed.

For example, many jurisdictions collect, access, use, and disclose health care information without consent or implied consent for certain public health, safety, and legal purposes.

Consent Tracker Subjects

Persons who are the subject of information or activity governed by a consent directive.

Consent Tracker Disciplines

  • Any type of patient or subject specific health care provision, including physical, preventive, palliative, hospice, community-based, reproductive, maternity, neonatal, pediatric, geriatric, mental, behavioral, substance use, clinical trials, and public health
  • Any type of patient or subject specific administrative or financial activities permitted or required for purposes care delivery management, operations, or payment
  • Any secondary use of patient or subject specific health and administrative/financial information, including research, public health surveillance, immunization and cancer registries, quality measures, payment incentive programs.
  • Any patient or subject specific provision of services, such as health device platforms, or health and fitness APPs.

Care Delivery Environment

Any care delivery environment, including Community, Geriatric, Hospice, Home care, Emergency, Inpatient, Intensive, Neonatal, Pediatric, or Primary Care

Locale

Any jurisdiction in which consent directives are permitted or required by policy.

RIM scope

Resource appropriateness

Expected implementations

Content sources

Example Scenarios

Resource Relationships

Timelines

gForge Users

When Resource Proposal Is Complete

When you have completed your proposal, please send an email to FMGcontact@HL7.org