Difference between revisions of "SSDMeeting2008 06 02"
Calvinbeebe (talk | contribs) (New page: <p><center><big><b>SSD Steering Group</b></big></center></p> <center><small>Minutes of June 2, 2008</small></center> <p></p> <table width=100%> <tr><th width=20%>Name</th><th width=35%>Org...) |
Calvinbeebe (talk | contribs) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 13: | Line 13: | ||
<tr><td>James R.Campbell</td><td>University of Nebraska Medical Center</td><td>campbell@unmc.edu</td><td></td></tr> | <tr><td>James R.Campbell</td><td>University of Nebraska Medical Center</td><td>campbell@unmc.edu</td><td></td></tr> | ||
</table> | </table> | ||
| − | |||
<p> | <p> | ||
SSD-SD co-chair e-mail votes received in advance: | SSD-SD co-chair e-mail votes received in advance: | ||
| Line 21: | Line 20: | ||
===Record Management & Evidentiary Support Functional Profile :=== | ===Record Management & Evidentiary Support Functional Profile :=== | ||
| − | <p>Record Management & Evidentiary Support Electronic Health Record System Functional Profile (RM-ES EHR-S Functional Profile). The profile is unique because it does not stand on its own. | + | <p>Record Management & Evidentiary Support Electronic Health Record System Functional Profile (RM-ES EHR-S Functional Profile).</p><p> The profile is unique because it does not stand on its own. |
</p> | </p> | ||
| − | <p>'''Motion:''' Accept contingent on approval by the EHR | + | <p>'''Motion:''' Accept contingent on approval by the EHR WG.</p> |
Made by: EHR (Corey) Seconded by: PA (Gregg) | Made by: EHR (Corey) Seconded by: PA (Gregg) | ||
<p>'''Abstain: 0 Approve: 7 Against: 0 Motion Passed'''</p> | <p>'''Abstain: 0 Approve: 7 Against: 0 Motion Passed'''</p> | ||
| − | |||
| − | |||
===Long Term Care Profile :=== | ===Long Term Care Profile :=== | ||
| − | <p> | + | <p> The LTC EHR-S Functional Profile will serve as a key resource to CCHIT in the development of certification requirements for EHR systems in the Long Term Care – nursing home community. CCHIT has road-mapped LTC certification committee work to begin in late 2008. In addition, this functional profile will provide the foundation for vendor/provider communication regarding expectations and requirements for EHR systems deployed in this care setting. |
| + | </p><p> | ||
| + | Logically should an implementation profile be normative or informative, does a profile require 2 implementers. Check with Dave Hamill about this. Is an EHR Functional Profile a normative? | ||
| + | </p><p> | ||
| + | EHR will revise and identify 2 implementers on the form. | ||
| + | </p> | ||
| − | <p>'''Motion:''' Accept | + | <p>'''Motion:''' Accept contigent upon approval by EHR WG.</p> |
| − | Made by: EHR ( | + | Made by: EHR (Corey) Seconded by: CDS (Matt) |
| − | <p>'''Abstain: 0 Approve: | + | <p>'''Abstain: 0 Approve: 7 Against: 0 Motion Passed'''</p> |
===Order Sets Publication Standard :=== | ===Order Sets Publication Standard :=== | ||
| − | <p> | + | <p>In this project, Clinical decision Support Workgroup will develop a standard and associated implementation guidelines for the publishing and sharing of structured order sets between collaborating institutions and clinical system vendors. This will be a V3 standard developed as a specialized instance of Structured Documents.</p> |
| + | <p> | ||
| + | The goal of the project is to enable sharing of interoperable order set content between knowledge developers, vendors of CPOE systems and healthcare institutions which will employ these knowledge structures in the implementation of computerized order entry and guideline decision support. Knowledge developers such as Thomson Reuters will be able to publish their order sets, communicate them to healthcare institutions such as the University of Nebraska and UNMC in turn can deploy those order sets in their clinical information system. In advanced applications, the order set may be integrated directly into a decision support system which will customize the order set for patient care at the time that it is employed by the clinician during an order session. | ||
| + | </p> | ||
| − | <p>'''Motion:''' | + | <p>'''Motion:''' to approve.</p> |
| − | Made by: | + | Made by: CDS (Matt) Seconded by: SD (Keith) |
| − | <p>'''Abstain: 0 Approve: | + | <p>'''Abstain: 0 Approve: 7 Against: 0 Motion Passed'''</p> |
===Implementation Guide for Healthcare Associated Infection Rpts :=== | ===Implementation Guide for Healthcare Associated Infection Rpts :=== | ||
| − | <p> | + | <p>With cooperation from CDC and Healthcare Associated Infections (HAI) software vendors, this project will develop an implementation guide constraining CDA Release 2. The implementation guide will support electronic submission of HAI data to the National Healthcare Safety Network.</p> |
| − | <p>'''Motion:''' | + | <p>'''Motion:''' to approve.</p> |
Made by: EHR (Pat) Seconded by: CDS (Matt) | Made by: EHR (Pat) Seconded by: CDS (Matt) | ||
| − | <p>'''Abstain: 0 Approve: | + | <p>'''Abstain: 0 Approve: 7 Against: 0 Motion Passed'''</p> |
===HL7 Canada project proposal for Special Authorization :=== | ===HL7 Canada project proposal for Special Authorization :=== | ||
| − | <p> | + | <p>This project will create a new topic area within the FM domain to deal with Special Authorization. Special Authorization is the process by which insured patients are covered for products and services that are not part of their regular plan. The initial scope of the topic area will include interactions for requesting special authorizations, notification of special authorization dispositions and querying of special authorizations at both a summary and detail level.</p> |
<p>'''Motion:''' Accept the behavioural health profile submitted with the changes suggested by Hans for clarification.</p> | <p>'''Motion:''' Accept the behavioural health profile submitted with the changes suggested by Hans for clarification.</p> | ||
| − | Made by: EHR (Pat) Seconded by: | + | Made by: EHR (Pat) Seconded by: PA (Gregg) |
| − | <p>'''Abstain: 0 Approve: | + | <p>'''Abstain: 0 Approve: 7 Against: 0 Motion Passed'''</p> |
Latest revision as of 15:57, 13 August 2008
| Name | Organization | Group | |
|---|---|---|---|
| Calvin Beebe | Mayo Clinic | cbeebe@mayo.edu | SD |
| Gregg Seppala | VHA | Gregg.seppala@va.gov | PA |
| Matt Sailors | The Methodist Hospital | MSailors@tmhs.org | CDS, Arden |
| Corey Spears | Practice Partner | cspears@practicepartner.com | EHR |
| Patrick Loyd | Gordon Point Informatics Ltd. | patrick.loyd@gpinformatics.com | OO |
| Mary Kay McDaniel | Markam, Inc. | mk_mcdaniel@hotmail.com | FM |
| Keith Boone | GE Healthcare Integrated IT Solutions | keith.boone@ge.com | SD |
| James R.Campbell | University of Nebraska Medical Center | campbell@unmc.edu |
SSD-SD co-chair e-mail votes received in advance: McDaniel, Mary Kay votes affirmative on all 5 (FM) Matt, Sailors votes affirmative on all 5 (CDS, Arden)
Contents
Record Management & Evidentiary Support Functional Profile :
Record Management & Evidentiary Support Electronic Health Record System Functional Profile (RM-ES EHR-S Functional Profile).
The profile is unique because it does not stand on its own.
Motion: Accept contingent on approval by the EHR WG.
Made by: EHR (Corey) Seconded by: PA (Gregg)
Abstain: 0 Approve: 7 Against: 0 Motion Passed
Long Term Care Profile :
The LTC EHR-S Functional Profile will serve as a key resource to CCHIT in the development of certification requirements for EHR systems in the Long Term Care – nursing home community. CCHIT has road-mapped LTC certification committee work to begin in late 2008. In addition, this functional profile will provide the foundation for vendor/provider communication regarding expectations and requirements for EHR systems deployed in this care setting.
Logically should an implementation profile be normative or informative, does a profile require 2 implementers. Check with Dave Hamill about this. Is an EHR Functional Profile a normative?
EHR will revise and identify 2 implementers on the form.
Motion: Accept contigent upon approval by EHR WG.
Made by: EHR (Corey) Seconded by: CDS (Matt)
Abstain: 0 Approve: 7 Against: 0 Motion Passed
Order Sets Publication Standard :
In this project, Clinical decision Support Workgroup will develop a standard and associated implementation guidelines for the publishing and sharing of structured order sets between collaborating institutions and clinical system vendors. This will be a V3 standard developed as a specialized instance of Structured Documents.
The goal of the project is to enable sharing of interoperable order set content between knowledge developers, vendors of CPOE systems and healthcare institutions which will employ these knowledge structures in the implementation of computerized order entry and guideline decision support. Knowledge developers such as Thomson Reuters will be able to publish their order sets, communicate them to healthcare institutions such as the University of Nebraska and UNMC in turn can deploy those order sets in their clinical information system. In advanced applications, the order set may be integrated directly into a decision support system which will customize the order set for patient care at the time that it is employed by the clinician during an order session.
Motion: to approve.
Made by: CDS (Matt) Seconded by: SD (Keith)
Abstain: 0 Approve: 7 Against: 0 Motion Passed
Implementation Guide for Healthcare Associated Infection Rpts :
With cooperation from CDC and Healthcare Associated Infections (HAI) software vendors, this project will develop an implementation guide constraining CDA Release 2. The implementation guide will support electronic submission of HAI data to the National Healthcare Safety Network.
Motion: to approve.
Made by: EHR (Pat) Seconded by: CDS (Matt)
Abstain: 0 Approve: 7 Against: 0 Motion Passed
HL7 Canada project proposal for Special Authorization :
This project will create a new topic area within the FM domain to deal with Special Authorization. Special Authorization is the process by which insured patients are covered for products and services that are not part of their regular plan. The initial scope of the topic area will include interactions for requesting special authorizations, notification of special authorization dispositions and querying of special authorizations at both a summary and detail level.
Motion: Accept the behavioural health profile submitted with the changes suggested by Hans for clarification.
Made by: EHR (Pat) Seconded by: PA (Gregg)
Abstain: 0 Approve: 7 Against: 0 Motion Passed
