Difference between revisions of "Product vMR DAM"
(New page: {{subst::Product_Brief}}) |
|||
| Line 1: | Line 1: | ||
| − | =Product Brief - = | + | =Product Brief - vMR-CDS DAM= |
__TOC__ | __TOC__ | ||
back to [[Main_Page]]<br/>back to [[Product_List]] | back to [[Main_Page]]<br/>back to [[Product_List]] | ||
==Product Name== | ==Product Name== | ||
| − | + | HL7 Version 3 Domain Analysis Model: Virtual Medical Record for Clinical Decision Support (vMR-CDS), | |
===Topics=== | ===Topics=== | ||
* | * | ||
===Standard Category=== | ===Standard Category=== | ||
| − | * | + | *Health Information Exchange Standards |
===Integration Paradigm=== | ===Integration Paradigm=== | ||
* | * | ||
===Type=== | ===Type=== | ||
| − | + | Informative ballot May 2010 | |
===Releases=== | ===Releases=== | ||
| − | + | Release 1 balloting May 2010 | |
===Summary=== | ===Summary=== | ||
| − | + | This project is developing a Domain Analysis Model for a Virtual Medical Record for clinical decision support. | |
===Description=== | ===Description=== | ||
| − | + | A Virtual Medical Record (vMR) for clinical decision support (CDS) is a data model for representing clinical information inputs and outputs that can be exchanged between CDS engines and local clinical information systems, through mechanisms such as CDS services. The goal of the overall vMR project is to create HL7 vMR data models capable of supporting scalable, interoperable CDS. This specific sub-project within the overall vMR project is developing a technology-neutral Domain Analysis Model (DAM) for the vMR that will serve as the foundation of vMRs for specific implementation technologies. | |
===Business Case (Intended Use, Customers)=== | ===Business Case (Intended Use, Customers)=== | ||
| − | + | In order to enable scalable and interoperable clinical decision support (CDS), there is a critical need for the definition and adoption of a common CDS information model, which has generally been referred to as a virtual medical record (vMR). The objective of this project is to address this need by establishing a standard information model for representing clinical information inputs and outputs that can be exchanged between CDS engines and clinical information systems, through mechanisms such as CDS services. | |
===Benefits=== | ===Benefits=== | ||
| − | + | vMR advantages to CDS are: - Creates one CDS data model, reducing data and terminology discrepancies. - Identifies restrictions that can be made to existing HL7 data models to simplify CDS development, while still ensuring support for needed CDS capabilities. - Enables CDS through a consistent set of standardized data inputs and outputs. - Encourages CDS at the point of care by reducing costs and response turn around time. - Eliminates the need for EHR vendors to maintain proprietary CDS structures and messages. | |
===Implementations/ Case Studies (Actual Users)=== | ===Implementations/ Case Studies (Actual Users)=== | ||
| − | + | Pending | |
===Resources=== | ===Resources=== | ||
====Work Groups==== | ====Work Groups==== | ||
| − | http://www.hl7.org/Special/committees/ | + | [http://www.hl7.org/Special/committees/dss/index.cfm Clinical Decision Support] |
| + | |||
====Education==== | ====Education==== | ||
| − | * | + | * http://wiki.hl7.org/index.php?title=Virtual_Medical_Record_(vMR) |
* See more at http://www.hl7.org/implement/training.cfm | * See more at http://www.hl7.org/implement/training.cfm | ||
| + | <!-- | ||
=====Certification Available===== | =====Certification Available===== | ||
*none | *none | ||
| Line 43: | Line 45: | ||
====Presentations==== | ====Presentations==== | ||
* | * | ||
| + | --> | ||
===Relationship to/ Dependencies on, other standards=== | ===Relationship to/ Dependencies on, other standards=== | ||
| − | * | + | *The foundation of vMRs for specific implementation technologies. |
===Links to current projects in development=== | ===Links to current projects in development=== | ||
| − | *[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber= | + | *[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=184 Project Insight ID # 184], Virtual Medical Record (vMR) for Clinical Decision Support |
Latest revision as of 18:18, 1 April 2010
Product Brief - vMR-CDS DAM
Contents
- 1 Product Brief - vMR-CDS DAM
- 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.1 Product Name
back to Main_Page
back to Product_List
Product Name
HL7 Version 3 Domain Analysis Model: Virtual Medical Record for Clinical Decision Support (vMR-CDS),
Topics
Standard Category
- Health Information Exchange Standards
Integration Paradigm
Type
Informative ballot May 2010
Releases
Release 1 balloting May 2010
Summary
This project is developing a Domain Analysis Model for a Virtual Medical Record for clinical decision support.
Description
A Virtual Medical Record (vMR) for clinical decision support (CDS) is a data model for representing clinical information inputs and outputs that can be exchanged between CDS engines and local clinical information systems, through mechanisms such as CDS services. The goal of the overall vMR project is to create HL7 vMR data models capable of supporting scalable, interoperable CDS. This specific sub-project within the overall vMR project is developing a technology-neutral Domain Analysis Model (DAM) for the vMR that will serve as the foundation of vMRs for specific implementation technologies.
Business Case (Intended Use, Customers)
In order to enable scalable and interoperable clinical decision support (CDS), there is a critical need for the definition and adoption of a common CDS information model, which has generally been referred to as a virtual medical record (vMR). The objective of this project is to address this need by establishing a standard information model for representing clinical information inputs and outputs that can be exchanged between CDS engines and clinical information systems, through mechanisms such as CDS services.
Benefits
vMR advantages to CDS are: - Creates one CDS data model, reducing data and terminology discrepancies. - Identifies restrictions that can be made to existing HL7 data models to simplify CDS development, while still ensuring support for needed CDS capabilities. - Enables CDS through a consistent set of standardized data inputs and outputs. - Encourages CDS at the point of care by reducing costs and response turn around time. - Eliminates the need for EHR vendors to maintain proprietary CDS structures and messages.
Implementations/ Case Studies (Actual Users)
Pending
Resources
Work Groups
Education
- http://wiki.hl7.org/index.php?title=Virtual_Medical_Record_(vMR)
- See more at http://www.hl7.org/implement/training.cfm
Relationship to/ Dependencies on, other standards
- The foundation of vMRs for specific implementation technologies.
Links to current projects in development
- Project Insight ID # 184, Virtual Medical Record (vMR) for Clinical Decision Support
