This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Conformance and Guidance for Implementation/Testing"

From HL7Wiki
Jump to navigation Jump to search
 
(45 intermediate revisions by 6 users not shown)
Line 1: Line 1:
[[Image:Implementer.jpg|180px|right|thumb|Implementers since 1986]]
+
  '''Warning''': Archived web page, CGIT has been renamed to Conformance. Please see current [[Conformance_Workgroup]] page for latest information.
 +
 
 
''Note: during the May2011 WGM the Implementation and Conformance WG has renamed itself to clarify the scope.''
 
''Note: during the May2011 WGM the Implementation and Conformance WG has renamed itself to clarify the scope.''
  
Line 10: Line 11:
 
The HL7 Implementation committee supports HL7 members and other users of HL7 (draft) standard specifications, with the identification and resolution of issues related to successful implementation thereof.  
 
The HL7 Implementation committee supports HL7 members and other users of HL7 (draft) standard specifications, with the identification and resolution of issues related to successful implementation thereof.  
  
This Wiki is used to develop an implementation FAQ, as well as a place to maintain and evolve ideas that have been discussed in committee. Formal minutes and agendas will still be maintained and posted to the HL7.org website - with this space providing for a more fluid development of content, where meeting notes will be fleshed out beyond what may heve been said in the meeting, and then used as the basis for other documents.  The page history can be used to see what has been added since a particular meeting.
+
This Wiki is used to develop an implementation FAQ, as well as a place to maintain and evolve ideas that have been discussed in committee. Formal minutes and agendas will still be maintained and posted to the HL7.org website - with this space providing for a more fluid development of content, where meeting notes will be fleshed out beyond what may have been said in the meeting, and then used as the basis for other documents.  The page history can be used to see what has been added since a particular meeting.
 
==Meeting Information ==
 
==Meeting Information ==
  
Meeting INFO for Monday Nov 14, 2011 - 04:00 PM (Eastern Time, GMT -05)
+
* Every two weeks on Monday
Please consult http://www.timeanddate.com/worldclock for your local times
+
* 4:00 PM US Eastern Time  
 +
* Web Meeting Information:
  
Notes
+
Phone Number: +1 770-657-9270
DISREGARD HL7 CONFERENCE LINE and USE:  
 
U.S. & Canada: 866.740.1260
 
Germany: 08006645316 (Toll Free)
 
--&gt; Access Code: 9755924
 
  
'''Web Meeting Info'''  https://cc.readytalk.com/r/2pavfekjpcuy
+
Participant Passcode: 644843
  
<br><br>
+
Web meeting [https://global.gotomeeting.com/join/647877325 https://global.gotomeeting.com/join/647877325]
Regular Call Info:
 
*Every week @ Monday 4:00 pm, Eastern Standard Time (New York, GMT-04:00) 
 
** Next meeting: [[CGIT concall 20111003| CGIT Conference Call - October 3rd, 2011]]
 
*Phone Number: +1 770-657-9270  Participant Passcode: 644843 
 
* Web meeting:
 
** [https://www1.gotomeeting.com/join/529886257 https://www1.gotomeeting.com/join/529886257]  
 
** Meeting ID: 529-886-257
 
  
 
== Projects ==
 
== Projects ==
Line 42: Line 33:
 
This section is for projects that have been considered in the Implementation committee and regarded as potentially useful, but for which there is no current activity:
 
This section is for projects that have been considered in the Implementation committee and regarded as potentially useful, but for which there is no current activity:
 
* Implementation Guide Authoring Tool (NIST)
 
* Implementation Guide Authoring Tool (NIST)
* MWB2
+
* Messaging Workbench 2 - MWB2
* RCnL: update
+
* [[Unified_Conformance_Guidance|Unified Conformance Guidance for HL7 Product Lines]] (previously "Refinement, Constraint, and Localization - version 3").
 +
* Functional Requirement Specification Guidance Document
  
 
=== Dormant Projects ===
 
=== Dormant Projects ===
Line 63: Line 55:
 
===General===
 
===General===
  
*[[ICTC SWOT-Analysis]]
+
*[[CGIT SWOT]]
*[[ICTC Strategic Plan]] (= 3 year roadmap)
+
*[[Conformance Strategic Plan]]
 +
**old: [[ICTC Strategic Plan]] (= 3 year roadmap)
 
*[[Implementation Register]]
 
*[[Implementation Register]]
 
*[[Implementation Case Studies]]
 
*[[Implementation Case Studies]]
Line 84: Line 77:
 
**[[File:V2UsageCodes1.3.pdf]]
 
**[[File:V2UsageCodes1.3.pdf]]
  
===together with Vocabulary===
+
===HL7 V2 Value Set Specification Proposal===
 +
*Proposal Slides
 +
**Slides coming soon...
 +
 
 +
===Joint with Vocabulary===
 
*[[Binding Syntax]]
 
*[[Binding Syntax]]
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=874 V2 code table versioning and alignment to V3 vocabulary mode]
+
*v2 code table project
 +
**[http://wiki.hl7.org/index.php?title=V2_Code_Table_Project Working Documents]
 +
**[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=874 Project details on Project Insight]
  
 
== Action Items ==
 
== Action Items ==
Line 140: Line 139:
 
*"Navigating the pitfalls: Implementing HL7 version 3", edited by Rene Spronk, see [http://www.ringholm.de/docs/04100_en.htm Ringholm whitepaper]. The contents have been included in the [[Implementation FAQ]].
 
*"Navigating the pitfalls: Implementing HL7 version 3", edited by Rene Spronk, see [http://www.ringholm.de/docs/04100_en.htm Ringholm whitepaper]. The contents have been included in the [[Implementation FAQ]].
  
==Testing Facilities==
+
==Tooling and Testing==
 +
List of known tools.
 +
===Profile Authoring Tools===
 +
*MWB (HL7v2)
 +
*IGAMT (HL7v2)
 +
*MDHT Model Drive Health Tools (CDA IG)
 +
*TriFolia - Lantana Group trifolia.lantana.com  (CDA IG)
 +
*Art-Decor  art-decor.org (HL7 v3 & CDA)
 +
*FHIR?
 +
*EHR Functional Modeling Tooling?
 +
 
 +
 
 +
===Conformance Validation Tools===
 +
*MWB
 +
*NIST v2 Validation Suite (IHE & MU)
 +
*NIST CDA Validation (IHE & MU)
 +
*SMART CDA
 +
*Detailed Clinical Models
 +
*Message Quality Framework?
 +
*HealthInfoWay V3 Validation Tool - Everest
 +
*HL7 Conformance Testing - Developer Integration Laboratory (DIL) by Aegis
 +
*Hi3 Solutions (HL7 v2)
 +
*AHML - Australian Health Messaging Lab (HL7 v2) http://www.ahml.com.au/
 +
*Art-Decor
 +
 
 +
===Links===
 +
 
 +
*[http://healthcare.nist.gov/NIST-TOOLS/index.html NIST Tools Portal]
 +
 
 +
* [http://hl7v2.ws.nist.gov/hl7v2ws NIST V2 Profile Schema]
 +
 
 
*NIST has installed a testserver for conformance testing of the POLB_IN111100 interaction (using May 2006 schema). E-mail your order message to v3receiver@gmail.com and it will respond with a one or more v3 interactions.
 
*NIST has installed a testserver for conformance testing of the POLB_IN111100 interaction (using May 2006 schema). E-mail your order message to v3receiver@gmail.com and it will respond with a one or more v3 interactions.
  
 
*[http://www.ahml.com.au Australian Healthcare Messaging Laboratory (AHML)] - HL7 Testing and Certification Services
 
*[http://www.ahml.com.au Australian Healthcare Messaging Laboratory (AHML)] - HL7 Testing and Certification Services
 +
 +
==Conformance Projects==
 +
Here is a list of Conformance Projects that are known to be in progress outside of HL7.
 +
 +
===US Meaningful Use Stage 2: HL7 Standards Referenced In the Final Rule ===
 +
The following link identifies the Implementation Guides required for MU2 certification:
 +
** http://www.hl7.org/implement/standards/hhsifr.cfm
 +
 +
===Conformance Facilitator===
 +
The Conformance Facilitator is a designated team member of a project intending to create an Implementation Guide of a existing HL7 standard (i.e. Product Line). The Conformance Facilitator is expected to have
 +
* implementing or testing solutions using of the base standard (e.g. HL7 Version 2.7, HL7 Version 3.0, HL7 CDA R2, HL7 FHIR)
 +
* representing interoperability requirements as base standard data element constraints, vocabulary specification, or functional criteria as required by the IG
 +
 +
The Conformance Facilitator informs the project team about conformance criteria, concepts, and best practices to create testable implementation guides.
  
 
== Working Group Meeting Agendas and Minutes==
 
== Working Group Meeting Agendas and Minutes==
 +
*[[Conformance_Jan_2017_WGM_Agenda]] San Antonio, TX, USA
 +
*[[CGITWG_Sep_2016_WGM_Agenda]] Baltimore, MD, USA
 +
*[[CGITWG_May_2016_WGM_Agenda]] Montreal, QC, Canada
 +
*[[CGITWG_Jan_2016_WGM_Agenda]] Orlando, FL, USA
 +
*[[CGITWG_Oct_2015_WGM_Agenda]] Atlanta, GA, USA
 +
*[[CGITWG May 2015 WGM Agenda]] Paris, France
 +
*[[CGITWG January 2015 WGM Agenda]] San Antonio, TX, US
 +
*[[CGITWG Sept 2014 WGM Agenda]] Chicago, IL, US
 +
*[[CGITWG May 2014 WGM Agenda]] Phoenix, AZ, US
 +
*[[CGITWG January 2014 WGM Agenda]] San Antonio, TX, US
 +
*[[CGITWG September 2013 WGM Agenda]] Cambridge, MD, US
 +
*[[CGITWG May 2013 WGM Agenda]] Atlanta, Georgia, US
 
*[[CGITWG January 2013 WGM Agenda]] Phoenix, Arizona, US
 
*[[CGITWG January 2013 WGM Agenda]] Phoenix, Arizona, US
*[[CGITWG Sept 2012 WGM Agenda]] Baltimore, Maryland, US ([http://www.hl7.org/documentcenter/public/wg/ictc/minutes/CGITWG%20Minutes%20-%20Sept%202012%20(Baltimore)%20draft.doc])
+
*[[CGITWG Sept 2012 WGM Agenda]] Baltimore, Maryland, US ([http://www.hl7.org/documentcenter/public/wg/ictc/minutes/CGITWG%20Minutes%20-%20Sept%202012%20(Baltimore)%20draft.doc minutes])
 
*[[CGITWG May 2012 WGM Agenda]] Vancouver, Canada ([http://www.hl7.org/documentcenter/public/wg/ictc/minutes/CGITWG%20Minutes%20-%20May%202012%20(Vancouver)%20v03.doc minutes])
 
*[[CGITWG May 2012 WGM Agenda]] Vancouver, Canada ([http://www.hl7.org/documentcenter/public/wg/ictc/minutes/CGITWG%20Minutes%20-%20May%202012%20(Vancouver)%20v03.doc minutes])
 
*[[CGITWG Jan 2012 WGM Agenda]] San Antonio ([http://www.hl7.org/documentcenter/public/wg/ictc/minutes/CGITWG%20Minutes%20-%20Jan%202011%20(San%20Antonio)%20v06.doc minutes])
 
*[[CGITWG Jan 2012 WGM Agenda]] San Antonio ([http://www.hl7.org/documentcenter/public/wg/ictc/minutes/CGITWG%20Minutes%20-%20Jan%202011%20(San%20Antonio)%20v06.doc minutes])
Line 171: Line 226:
 
== Conference Call Agenda and Minutes ==
 
== Conference Call Agenda and Minutes ==
  
 +
*[[Conformance ConCalls 2016]]
 +
*[[IC concalls 2015]]
 +
*[[IC concalls 2014]]
 +
*[[IC concalls 2013]]
 
*[[IC concalls 2012]]
 
*[[IC concalls 2012]]
 
*[[IC concalls 2011]]
 
*[[IC concalls 2011]]
Line 179: Line 238:
 
*[[IC concalls 2006]]
 
*[[IC concalls 2006]]
  
===Archived Links===
+
== New Wiki Page ==
 +
*[[Conformance_Workgroup|Conformance Workgroup]]
 +
 
 +
==Archived Links==
 
The following links are provided for convenience but should not be used any more!
 
The following links are provided for convenience but should not be used any more!
  
 +
*[[Conformance_and_Guidance_for_Implementation/Testing_archive2015]]
 
*[[Conformance Tel.Conf.]]
 
*[[Conformance Tel.Conf.]]
 
*[[Conformance Tel.Conf. Minutes]]
 
*[[Conformance Tel.Conf. Minutes]]
Line 187: Line 250:
 
*[[IC Older Conference Calls]]
 
*[[IC Older Conference Calls]]
 
*[[ICTC Telecon Chores]]
 
*[[ICTC Telecon Chores]]
 
+
[[Category:CGIT]]
 
[[Category:Work_Group]]
 
[[Category:Work_Group]]
 
[[Category:Foundation_and_Technology_Steering_Division]]
 
[[Category:Foundation_and_Technology_Steering_Division]]

Latest revision as of 15:29, 22 September 2016

  Warning: Archived web page, CGIT has been renamed to Conformance. Please see current Conformance_Workgroup page for latest information. 

Note: during the May2011 WGM the Implementation and Conformance WG has renamed itself to clarify the scope.

Note: during the May2007 WGM the Implementation Committee and the Conformance SIG became a new TC. See draft ImpConf Mission and Charter and Actions for ImpConf merger. The Implementation committee was formally wound up, and the Implementation Conformance TC (ICTC) was formed.

Conformance and Guidance for Implementation/Testing

This wiki page is a merger of the content from the two committee's original wiki pages.

The HL7 Implementation committee supports HL7 members and other users of HL7 (draft) standard specifications, with the identification and resolution of issues related to successful implementation thereof.

This Wiki is used to develop an implementation FAQ, as well as a place to maintain and evolve ideas that have been discussed in committee. Formal minutes and agendas will still be maintained and posted to the HL7.org website - with this space providing for a more fluid development of content, where meeting notes will be fleshed out beyond what may have been said in the meeting, and then used as the basis for other documents. The page history can be used to see what has been added since a particular meeting.

Meeting Information

  • Every two weeks on Monday
  • 4:00 PM US Eastern Time
  • Web Meeting Information:

Phone Number: +1 770-657-9270

Participant Passcode: 644843

Web meeting https://global.gotomeeting.com/join/647877325

Projects

Approved Projects

This section is for projects that are registered with the HL7 Project Office, and for which there are formal project scope documentation

Prospective Projects

This section is for projects that have been considered in the Implementation committee and regarded as potentially useful, but for which there is no current activity:

Dormant Projects

These are projects that have been active, but which are not currently being progressed within the committee.

Closed Projects

These are projects that have been closed.

Committee agenda topics

  • FAQs on the HL7.org website -- how are they maintained

Current Activities

This section is for projects that are actively being developed in the Implementation committee

General

V3

V2.x

HL7 V2 Value Set Specification Proposal

  • Proposal Slides
    • Slides coming soon...

Joint with Vocabulary

Action Items

Please find IC work group action items here: IC Action Items. They are categorized as Open and Closed.

Documents

Implementation related documents

Conformance related documents

These documents are open documents for editing by any interested party:

NICTIZ have created an implementation oriented discussion document related to conformance and artefact versioning:

Governance Committees

Work Group decision making process: http://www.hl7.org/Library/Committees/pi/Default_HL7_WG_DMP_v3.0.doc

Documents maintained by other committees

The following documents may be of interest / relevance to implementers, and you are encouraged to read / review / correct / improve them

External documents

  • Example implementation guide
  • Examples:
    • CDA Release 2, see [1] (10 Mb) for a collection of CDA R2 examples, stylesheets and implementation guides. Examples from various realms. A more up-to-date version of this example collection is available here.
    • Normative Edition 2006 examples and schema, see NE2006 Examples. The examples include examples from multiple Realms for multiple domains (e.g. Patient Admin, Lab, Medical Records)
    • May2006 Ballot schema and schema, see German Realm May2006 Examples. Most examples are related to Patient Registries or Financial Coverage. Some schema have been constrained to fit the requirements of the German realm.
    • NICTIZ (AORTA) schema and examples (mostly based on ballot 7), see Dutch Realm Ballot7 Examples. Most examples are related to PA, Pharmacy, Patient Care.
  • "Navigating the pitfalls: Implementing HL7 version 3", edited by Rene Spronk, see Ringholm whitepaper. The contents have been included in the Implementation FAQ.

Tooling and Testing

List of known tools.

Profile Authoring Tools

  • MWB (HL7v2)
  • IGAMT (HL7v2)
  • MDHT Model Drive Health Tools (CDA IG)
  • TriFolia - Lantana Group trifolia.lantana.com (CDA IG)
  • Art-Decor art-decor.org (HL7 v3 & CDA)
  • FHIR?
  • EHR Functional Modeling Tooling?


Conformance Validation Tools

  • MWB
  • NIST v2 Validation Suite (IHE & MU)
  • NIST CDA Validation (IHE & MU)
  • SMART CDA
  • Detailed Clinical Models
  • Message Quality Framework?
  • HealthInfoWay V3 Validation Tool - Everest
  • HL7 Conformance Testing - Developer Integration Laboratory (DIL) by Aegis
  • Hi3 Solutions (HL7 v2)
  • AHML - Australian Health Messaging Lab (HL7 v2) http://www.ahml.com.au/
  • Art-Decor

Links

  • NIST has installed a testserver for conformance testing of the POLB_IN111100 interaction (using May 2006 schema). E-mail your order message to v3receiver@gmail.com and it will respond with a one or more v3 interactions.

Conformance Projects

Here is a list of Conformance Projects that are known to be in progress outside of HL7.

US Meaningful Use Stage 2: HL7 Standards Referenced In the Final Rule

The following link identifies the Implementation Guides required for MU2 certification:

Conformance Facilitator

The Conformance Facilitator is a designated team member of a project intending to create an Implementation Guide of a existing HL7 standard (i.e. Product Line). The Conformance Facilitator is expected to have

  • implementing or testing solutions using of the base standard (e.g. HL7 Version 2.7, HL7 Version 3.0, HL7 CDA R2, HL7 FHIR)
  • representing interoperability requirements as base standard data element constraints, vocabulary specification, or functional criteria as required by the IG

The Conformance Facilitator informs the project team about conformance criteria, concepts, and best practices to create testable implementation guides.

Working Group Meeting Agendas and Minutes

Conference Call Agenda and Minutes

New Wiki Page

Archived Links

The following links are provided for convenience but should not be used any more!