Difference between revisions of "FTSD-ConCall-20100629"

From HL7 TSC
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
=Foundation & Technology Steering Division - Conference Call June 29, 2010=  
 
=Foundation & Technology Steering Division - Conference Call June 29, 2010=  
  
==[[Foundation_%26_Technology_Meetings| Meeting Information]]==
+
==Attendees==
:'''Conference Call''' is scheduled for '''0.5 hour'''
+
Nelson, Julian, Laakso, Stuart, Walker, Knapp, Knight, Beeler
::'''12:00 PM''' (consult [http://www.timeanddate.com/worldclock http://www.timeanddate.com/worldclock for local times])
 
:'''''HL7 Conference Call Service'''''
 
::Phone Number: +1 770-657-9270 (Passcode: 943627)
 
:'''''Online Meeting Service''''' - GoToMeeting
 
::[https://www2.gotomeeting.com/join/385800034 https://www2.gotomeeting.com/join/385800034] (GoToMeeting ID: 385-800-034)
 
  
Members:
+
Representing:
 
*Implementable Technology Specifications (ITS)
 
*Implementable Technology Specifications (ITS)
*Implementation/Conformance
 
 
*Infrastructure & Messaging (InM)
 
*Infrastructure & Messaging (InM)
*RIM-Based Application Architecture (RIMBAA)
 
 
*Modeling & Methodology (MnM)
 
*Modeling & Methodology (MnM)
*Security
 
*Service Oriented Architecture (SOA)
 
*Templates
 
 
*Vocabulary
 
*Vocabulary
  
==Attendees==
+
===Approve [[FTSD-ConCall-20100601|Minutes of June 1]] & Accept Agenda===
 +
Beeler/Knapp 4-0-2
 +
==='''Project HD/Micro-ITS - Leads to Documents for Review===
 +
====Discussion====
 +
Currently, two documents have been issued in the last week from this project which are now under review by ITS.  Preliminary review suggests to the ITS co-chairs that this material contains static model, dynamic model and transport components.
 +
 
 +
From the documents: "The hData Record Format (HRF) describes an XML representation of the information in an electronic health record (EHR). ... This specification defines a network transport API for accessing components of an HRF and sending messages to an EHR system."
 +
 
 +
While some of these components may be the sole purview of ITS, the co-chairs feel that many appear to fall within the domains of other FT committees or even domain specific committees such as EHR, and therefore the co-chairs are seeking guidance from FT as to how to proceed.
 +
 
 +
The documents contain a RESTful transport, and the hData Record Format, no Micro-ITS is currently provided.
  
==Agenda==
+
A transport for REST (http-based, like WSI Web Services) that is not about moving native HL7 content but rather about moving an "hData record" containing a hData record format (a ZIP file and manifest) and a zipped set of "hData records" which are snippets of CDA documents, HL7 Messages, Micro-ITS, SOA or other HL7 content models.
#''(05 min)'' Roll Call
 
#''(05 min)'' Approve [[FTSD-ConCall-20100601|Minutes of June 1]] & Accept Agenda
 
#''(08 min)'' '''Project Scope re Neutral Mapping - ITS'''
 
#''(08 min)'' '''Project Scope re SKMT Glossary - Vocabulary'''
 
#''(08 min)'' '''Project Scope re Binding Syntax - Vocabulary'''
 
==='''Project HD/Micro-ITS - Leads to Documents for Review===
 
====Issues/Notes====
 
No micro ITS in the documents instead:
 
  
A transport for REST (http-based, like WSI Web Services) that is not about moving native HL7 content but rather about moving an "hData record" containing a hData record format (actually a ZIP file and manifest) and a zipped set of "hData record" which are snippets of CDA documents or other documents.
+
The hData component model (the packaging of harvested HL7 snippets)is outlined, but no specific mappings or the mechanisms for or responsibility for the mappings are detailed.
  
hData component model is expressed elsewhere and unclear. It is like starting with ITS and then defining the content rather than having a content standard and figuring how to transport it
+
Mitre is strongly interested in getting this voted in the next cycle. ITS seeks guidance as to requirements and mechanisms for engaging  appropriate stakeholders.
  
There is no ITS inside this.  Yet, Mitre is strongly interested in getting this voted in the next cycle. Approaching a project that is proceeding from an implementation without '''any consideration''' of the HL7 principles and foundation documents.
+
It clearly walks into spaces for ARB, Structured Documents, EHR, MnM, InM, etc. and only 30 days to ballot deadlines.  
  
Running down the railroad track, but no HL7-asserted requirements nor any constraint on the contents. It clearly walks into spaces for EHR, MnM, InM, etc. and only 30 days to ballot deadlines.
+
ITS, as facilitators of this project, should engage at a minimum: M&M, INM, ARB, RIMBAA, SD & EHR with respect to the Static model (HDR); the dynamic model (REST API) transport (REST) and SAIF implications.
  
 
====Dilemma and FTSD Motion====
 
====Dilemma and FTSD Motion====
Requires buy-in and consideration by a raft of HL7 Work Groups who have never heard of or seen this. It does not seem reasonable to try to do this in time for the September Ballot. It should be circulated, socialized and discussed in detail at the October WGM.
+
Observed that this requires buy-in and consideration by an additional raft of HL7 Work Groups who need to see this and yet are currently unaware of it. It does not seem reasonable to try to do this in time for the September Ballot. Move the action that this be circulated, socialized and discussed in detail at the October WGM, with ITS facilitating this action.
 +
 
 +
Beeler/Nelson 6-0-0
 +
===Unaddressed Agenda Items===
 +
#'''Project Scope re Neutral Mapping - ITS'''
 +
#:Updated scope statement was previously approved with amendments.  Will forward to other SD and TSC
 +
#'''Project Scope re SKMT Glossary - Vocabulary'''
 +
#:Updated scope statement needs review to assure met earlier objections.  Then consider  forward to other SD and TSC.
 +
#'''Project Scope re Binding Syntax - Vocabulary'''
 +
#:Updated scope statement was previously approved with amendments. Will forward to other SD and TSC
  
 
===[[FTSD Agenda item list|Agenda items]]===
 
===[[FTSD Agenda item list|Agenda items]]===

Latest revision as of 18:57, 29 June 2010

Foundation & Technology Steering Division - Conference Call June 29, 2010

Attendees

Nelson, Julian, Laakso, Stuart, Walker, Knapp, Knight, Beeler

Representing:

  • Implementable Technology Specifications (ITS)
  • Infrastructure & Messaging (InM)
  • Modeling & Methodology (MnM)
  • Vocabulary

Approve Minutes of June 1 & Accept Agenda

Beeler/Knapp 4-0-2

Project HD/Micro-ITS - Leads to Documents for Review

Discussion

Currently, two documents have been issued in the last week from this project which are now under review by ITS. Preliminary review suggests to the ITS co-chairs that this material contains static model, dynamic model and transport components.

From the documents: "The hData Record Format (HRF) describes an XML representation of the information in an electronic health record (EHR). ... This specification defines a network transport API for accessing components of an HRF and sending messages to an EHR system."

While some of these components may be the sole purview of ITS, the co-chairs feel that many appear to fall within the domains of other FT committees or even domain specific committees such as EHR, and therefore the co-chairs are seeking guidance from FT as to how to proceed.

The documents contain a RESTful transport, and the hData Record Format, no Micro-ITS is currently provided.

A transport for REST (http-based, like WSI Web Services) that is not about moving native HL7 content but rather about moving an "hData record" containing a hData record format (a ZIP file and manifest) and a zipped set of "hData records" which are snippets of CDA documents, HL7 Messages, Micro-ITS, SOA or other HL7 content models.

The hData component model (the packaging of harvested HL7 snippets)is outlined, but no specific mappings or the mechanisms for or responsibility for the mappings are detailed.

Mitre is strongly interested in getting this voted in the next cycle. ITS seeks guidance as to requirements and mechanisms for engaging appropriate stakeholders.

It clearly walks into spaces for ARB, Structured Documents, EHR, MnM, InM, etc. and only 30 days to ballot deadlines.

ITS, as facilitators of this project, should engage at a minimum: M&M, INM, ARB, RIMBAA, SD & EHR with respect to the Static model (HDR); the dynamic model (REST API) transport (REST) and SAIF implications.

Dilemma and FTSD Motion

Observed that this requires buy-in and consideration by an additional raft of HL7 Work Groups who need to see this and yet are currently unaware of it. It does not seem reasonable to try to do this in time for the September Ballot. Move the action that this be circulated, socialized and discussed in detail at the October WGM, with ITS facilitating this action.

Beeler/Nelson 6-0-0

Unaddressed Agenda Items

  1. Project Scope re Neutral Mapping - ITS
    Updated scope statement was previously approved with amendments. Will forward to other SD and TSC
  2. Project Scope re SKMT Glossary - Vocabulary
    Updated scope statement needs review to assure met earlier objections. Then consider forward to other SD and TSC.
  3. Project Scope re Binding Syntax - Vocabulary
    Updated scope statement was previously approved with amendments. Will forward to other SD and TSC

Agenda items

Action Item List

Back to Meetings