Difference between revisions of "Product MR"
Mike kingery (talk | contribs) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 92: | Line 92: | ||
====Work Groups==== | ====Work Groups==== | ||
| − | [http://www.hl7.org/Special/committees/ | + | [http://www.hl7.org/Special/committees/homehealth/index.cfm Community Based Collaborative Care] (CBCC) |
====Education==== | ====Education==== | ||
* See more at http://www.hl7.org/implement/training.cfm | * See more at http://www.hl7.org/implement/training.cfm | ||
| Line 100: | Line 100: | ||
===Links to current projects in development=== | ===Links to current projects in development=== | ||
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=373 Project Insight ID#373], Composite Privacy Consent Directive | *[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=373 Project Insight ID#373], Composite Privacy Consent Directive | ||
| + | |||
| + | |||
| + | [[category:Products]] | ||
Latest revision as of 15:49, 29 November 2011
Product Brief - HL7 V3 Domain: Medical Records
Contents
- 1 Product Brief - HL7 V3 Domain: Medical Records
- 1.1 Product Name
- 1.1.1 Topics
- 1.1.2 Standard Category
- 1.1.3 Integration Paradigm
- 1.1.4 Type
- 1.1.5 Releases
- 1.1.6 Summary
- 1.1.7 Description
- 1.1.8 Business Case (Intended Use, Customers)
- 1.1.9 Benefits
- 1.1.10 Implementations/ Case Studies (Actual Users)
- 1.1.11 Resources
- 1.1.12 Relationship to/ Dependencies on, other standards
- 1.1.13 Links to current projects in development
- 1.2 Product Name- HL7 Version 3 Standard: Medical Records; Data Access Consent, Release 1
- 1.2.1 Topics
- 1.2.2 Standard Category
- 1.2.3 Integration Paradigm
- 1.2.4 Type
- 1.2.5 Releases
- 1.2.6 Summary
- 1.2.7 Description
- 1.2.8 Business Case (Intended Use, Customers)
- 1.2.9 Benefits
- 1.2.10 Implementations/ Case Studies (Actual Users)
- 1.2.11 Resources
- 1.2.12 Relationship to/ Dependencies on, other standards
- 1.2.13 Links to current projects in development
- 1.1 Product Name
back to Main_Page
back to Product_List
Product Name
HL7 V3: Medical Records/Information Management
Topics
- Document Management
- Document Query
- Data Consent
- ANSI/HL7 V3 MRDACM, R1-2008: HL7 Version 3 Standard: Medical Records; Data Access Consent, Release 1 - 11/10/2008
- Composite Privacy Consent Directive, R2 (Informative)
Standard Category
- Health Information Exchange Standards
Integration Paradigm
- Messaging
Type
- Normative, ANSI Standard (Release 1)
- DSTU (Release 2, expired May 2008)
Releases
- ANSI/HL7 V3 RCMR, R1-2006; HL7 Version 3 Standard: Medical Records/Information Management, Release 1 - 11/3/2006
- HL7 V3 RCMR, R2-2006 - HL7 Version 3 Standard: Medical Records/Information Management, Release 2; 2006
- ANSI/HL7 V3 MRDACM, R1-2008: HL7 Version 3 Standard: Medical Records; Data Access Consent, Release 1 - 11/10/2008; Composite Privacy Consent Directive, R2
Summary
The Medical Records standard defines the messages used to manage, organize, exchange and query documents.
Description
The Medical Records domain currently supports clinical document management, and document querying. In the future, it is intended also to support the data exchange needs of applications supporting other medical record functions, including chart location and tracking, deficiency analysis, consents, and release of information. The main purpose of the medical record is to produce an accurate, legal, and legible clinical document that serves as a comprehensive account of healthcare services provided to a patient, and which has the following characteristics:
Persistence: A clinical document continues to exist in an unaltered state, for a time period defined by local and regulatory requirements.
Stewardship: A clinical document is maintained by an organization entrusted with its care.
Potential for authentication: A clinical document is an assemblage of information that is intended to be legally authenticated.
Wholeness: Authentication of a clinical document applies to the whole and does not apply to portions of the document without the full context of the document.
Human readability: A clinical document is human readable.
These interactions are mainly associated with documents that will be or have been transcribed. The types and appearance of the transcribed documents can vary greatly within a healthcare organization and between organizations. However, the main purpose of the transcription process is to document patient care or diagnostic results in a legible manner; these documents then become part of the legal medical record.
Business Case (Intended Use, Customers)
Healthcare Providers, Healthcare IT Vendors, EHR Systems, Transcription Systems, Departmental Systems
Benefits
Provides a standards means of communicating clincial documents between transcription systems ad medical record systems. Also enables querying clinical document support from EHR systems for various use cases.
Implementations/ Case Studies (Actual Users)
Canada Health Infoway (CHI), UK National Health Service (NHS)
Resources
Work Groups
Education
- See more at http://www.hl7.org/implement/training.cfm
Presentations
Relationship to/ Dependencies on, other standards
Links to current projects in development
- Project Insight ID#373, Composite Privacy Consent Directive
Product Name- HL7 Version 3 Standard: Medical Records; Data Access Consent, Release 1
Topics
Data Access Consent, Release 1
Standard Category
- Health Information Exchange Standards
Integration Paradigm
- Messaging
Type
- Normative, ANSI Standard (Release 1)
Releases
- ANSI/HL7 V3 MRDACM, R1-2008: HL7 Version 3 Standard: Medical Records; Data Access Consent, Release 1 - 11/10/2008; Composite Privacy Consent Directive, R2
Summary
The Data Consent topic CMET and messages will allow patients to consent to their health information being collected, accessed, used or disclosed, or to rescind such consent. There is support for health care providers to gain emergency access and support for patients to utilize a 'shared secret' in managing their consents. Used in conjunction with the masking messages from the Shared Message Domain, the Data Consent messages will provide patients the appropriate tools to manage their health information. This version of the document includes improved documentation, vocabulary, business name changes for the Shared secret as agreed in reconciliation.
Description
Business Case (Intended Use, Customers)
Healthcare Providers, Healthcare IT Vendors, EHR Systems, Transcription Systems, Departmental Systems
Benefits
Implementations/ Case Studies (Actual Users)
Resources
Work Groups
Community Based Collaborative Care (CBCC)
Education
- See more at http://www.hl7.org/implement/training.cfm
Relationship to/ Dependencies on, other standards
Links to current projects in development
- Project Insight ID#373, Composite Privacy Consent Directive
