eDCI Project Meeting

/ June 29, 2007
10:00 AM – 11:00 AM
Teleconference
Telecon Info: / Phone Number: 702-894-2444
Participant Passcode: 74859677
Participant Passcode: 74859677
Webinar Info: / Guest Attend URL:

Event ID:
SLR494593
Event Password:
edci2007
References: / BRIDG Wiki (

Attendees

First Name / Last Name / Email
Margaret / Gronvall /
David / Iberson-Hurst /
Stephen / Johnson /
Donald / Kacher /
Ken / Light /
Charlie / Mead /
Joyce / Niland /
Terry / Quinn /
Mitra / Rocca /
Jason / Rock /
Aaron / Seib /
Marti / Velezis /
Gary / Walker /
Denise / Warzel /
Thomas / White /

Minutes

Agenda item: / Project Kick-off / Presenter: / Charlie Mead
Discussion: / Overview of the eDCI Project History
Agenda item: / Review of eDCI – Early Adopter Artifacts / Presenter: / Don Katcher
Discussion:
The eDCI message developed in the Early Adopter project followed the HL7 Development Framework (HDF), which included use cases, static model, dynamic model and RMIM. This documentation is the starting point of the RCRIM approved project to develop the specification for eDCI.
The message is composed of the following three components:
  • Instrument – includes sections and groups derived from HL7 RIM. (Often referred to as the “Collector”)
  • Global Definition – includes the Unique Identifier or Concept Identifier (ID and Domain) derived from HL7 RIM.
  • Institution/Organization Specific Content – includes a proprietary XML blob (XSD should be published and publicly available. This is not derived from the HL7 RIM.
Don reviewed the Static Model in Enterprise Architect as well as several sample forms.
Discussion: / NCI’s status of using the eDCI message created
The eDCI message was restructured and its feasibility was tested in a test environment. There were questions about the payload and transport wrappers.
The rendering information is included in their messages.
Discussion: / Rendering Information – Inclusion or Exclusion in eDCI Message
The scope of the message was to provide the semantics, logical structure and relative position, but not how the message should be rendered (i.e., stylesheet).
Refer to both the Project Description and Project Scope documents on the BRIDG Wiki.
Discussion: / Mapping terminology
There was question as to whether there were plans to map to terminology in LOINC and SNOMED for the questions and allowable answers.
There has been some work done with HL7 v2.5 and CCD; and there could be some work with HL7 v3.
The mapping terminology topicshould be discussed at a future meeting.

Other Information

Special notes:
Meetings will be held on a weekly basis and serve as working sessions to complete the required artifacts to take the message to ballot.
Conclusions:
N/A
Action items / Person responsible / Deadline
Send meeting documents to participants / Marti Velezis / 07/06/07
Post documents to eDCI BRIDG Wiki / Marti Velezis / 07/06/07

070629_eDCI_MM.doc1 of 3June 29, 2007