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
Line 167: Line 167:
 
==Conformance Projects==
 
==Conformance Projects==
 
Here is a list of Conformance Projects that are known to be in progress outside of HL7.  
 
Here is a list of Conformance Projects that are known to be in progress outside of HL7.  
−
*US Meaningful Use
+
*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==

Revision as of 21:06, 1 June 2015

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 Will not normally be joining the GoToMeeting, but if needed: 1. https://global.gotomeeting.com/join/249006993


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

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

Archived Links

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

Retrieved from "https://wiki.hl7.org/w/index.php?title=Conformance_and_Guidance_for_Implementation/Testing&oldid=100623"