CGIT WG MinutesAtlanta, GA, USA (10/0215)

HL7 Work Group Meeting

Atlanta, GA – October 2015

Attendees:

The list is provided in the Appendix.

Adding a typed listed is tedious, given that some names are hard to read.

Monday, October5, 2015

CGIT Q3: Administrivia

Chair: / Robert Snelick
Scribe: / Ioana Singureanu
Attendees: / Abdul-Malik Shakir, Sandra Martinez + chair + scribe
Quorum: / Yes

Agenda

  • approve agenda
  • approve minutes
  • projects (review)

Approved May WGM Minutes (motion made by Abdul-Malik, second Rob Snelik, 3-0-0)

Discussed the difference between compliance and conformance as it applies to “standard conformity” using profiles:

  • “compliant profile” is a profile that is properly derived from another profiles (a “parent” or “base” profile
  • Conformance not “compliance” should be used in reference to “standard conformity” using profiles.
  • Compatible profiles are sender and receiver specific profiles that are compatible (i.e. the sender is supplying a superset of data element required by the received.

[We should probably embed the diagram summarizing these concepts]

CGIT Q4: v2.9 Proposals

Chair: / Rob Snelick
Scribe: / Rob Snelick
Attendees: / Abdul-Malik Shakir, Sandra Martinez, Craig Newman + chair + scribe
Quorum: / Yes

Agenda

  • Create Position Statement for a HL7 v2 Standalone Conformance Specification (SCS)

Position Statement – Standalone Conformance Specification (SCS)

Scope: HLv2.x

Target: HL7 v2.+ (2016 Edition)

Pull Chapter 2B (Conformance) from the base standard and make it a standalone specification.

  1. Conformance chapter is not version specific
  2. Conformance is independent of the specifics that is being measured (claiming conformance to)
  3. Versions of the HL7 standard and versions of the conformance specification are independent
  4. having it embedded in the base standard confusing
  5. V2.7.1 was created “largely” because of changes in the conformance chapter
  6. Use the latest standalone conformance specification when creating conformance profiles
  7. Advantage to using the latest conformance constructs; improved granularly of specifications
  8. Better the specification better implementation and validation
  9. The specification will not invalidate existing profiles with this mechanism
  10. E.g, C and CE, and now C (a/b)  C(R/X) and C(RE/X)
  11. Publish on an independent cycle
  12. Long term goal is to be agnostic to product line (similar to the same approach vocabulary is taking). Initially HL7 v2.x.
  13. Improve consistency of specifying HL7 v2 implementation guides
  14. Companion best practices/how to document
  15. SCS will have normative statements indicating what is required of an IG, e.g., specifying the SCS version that it is using

Risks/Clarification

  1. Backwards compatibility
  2. Coordinate with education for HL7 certification (member certification)
  3. If not part of the base standard, will developers give it the same standing? Suggest to have a placeholder or reference to the conformance specification.

Tuesday

CGIT Q1:Tooling

Chair: / Rob Snelick
Scribe: / Frank Oemig
Attendees: / See Appendix
Quorum: / Yes

Some attendees presented an overview about their toolkit. The highlights are listed below:

Hi3 Toolkit

  • Validation of message instances on:
  • Syntax(by XML schema)
  • Structure
  • Semantics
  • Demo.hi3solutions.com:9000
  • Using InterfaceWare as the underlying engine

MWB

  • No major changes/updates during the last months
  • The current set of files compiles and builds in Delphi
  • Matt is trying to fix the latest issues, However, the last updates form Pete are lost.

NIST Validation – Web Service

  • Service for validation
  • Hl7v2.ws.nist.gv/hl7v2ws
  • Can be installed locally (war file)

AEGIS FHIR

  • AEGIS provides a high level overview about the developers integration lab (DIL)
  • Resource Testscript
  • Allow entry level test cases
  • Can host the scripts
  • HPSC (Health Platform Services Consortium)

NIST HL7 v2.x Message Validation Tool

  • NIST updated testing framework. Tool to support 2015 ONC Certification in progress with target release of December 2014. Certification tools include Immunization and Syndromic Surveillance. Other new tools include LOI, eDOS, LRI, and ELR in the Lab space.

CGIT: Q2: RCnL & Profile Discussion

Chair: / Frank Oemig
Scribe: / Robert Snelick
Attendees: / Please see Appendix
Quorum: / Yes

The group discussed the current status of the RCnL Rel.2 Reaffirmation project. According to everybody’s memories all comments are resolved, a recirculation ballot has passed, and the negative should have been withdrawn. However, this topic stays open in the PBMS matrix. (Note: after discussion with Lynn everything is fine and HL7 is waiting for ANSI approval. After that clarification CGIT also earns a gold star.)

The group also discussed whether RCnL Rel.3 project should be continued. With the upcoming interest in FHIR and the lack of resources with HL7 V3 this project should be closed. Instead, a new project for a more general conformance document should be established. Ioana has crafted an appropriate PSS which needs approval.

Action item: Ioana to follow up with TSC.

For the rest of the Guidance to FHIR on conformance strategy, i.e. profiles and implementation guides was discussed.

Profiles can be used for:

  • Assemble constraints, e.g. “cardinality equals 3” and bind it to an element
  • Discussion about how to use bundle to represent an ADT admission message
  • Demo of FORGE profile editor

CGIT: Q3

Chair: / Ioana Singureanu
Scribe: / Please see InM minutes
Attendees: / Please see InM minutes
Quorum

CGIT: Q4 cancelled

Chair: / Frank Oemig
Scribe: / -
Attendees: / None
Quorum / No

Wednesday

Q3 & Q4 FHIR, CGIT and Templates

Chair: / Ioana Singureanu
Scribe: / Frank Oemig
Attendees: / Please see Appendix
Quorum: / Yes

Presentation of thoughts about handling and managing Implementation Guides. Ewout and Kai have assembled a list of requirements and aspects they are presenting and which were discussed.

They identified different Kinds of IGs:

  • Strategy
  • Principles
  • Subject
  • Use Case

The kind of the IG determines the sections and components it should include. The list presented was discussed immediately and modified. The following presents the major headlines on the first two levels. The full list will be provided after the meeting:

  • Title of the guide
  • Language, identifier
  • Table of contents
  • Generated headers and links
  • Document information (meta data, “colophon”)
  • Structure of the guide
  • imprint
  • Primary contact party
  • Client, customer
  • Governance group
  • Editors, authors, contributors
  • Ballot and harmonization
  • Copyright + IP, licenses
  • acknowledgements
  • Revision list
  • disclaimer
  • Introduction to the guide
  • Rationale, purpose, context
  • Objective
  • audience
  • scope and boundaries
  • relationships with other projects and guides
  • legal obligation
  • principles and background
  • prerequisites
  • standards used and licensing
  • legend
  • general implementation guidance
  • conformance clause
  • (provided by Rob)
  • functional requirements and high-level use cases
  • overview of systems and architecture
  • system actors overview
  • use case
  • scenarios
  • trigger/reasons
  • dataset and data elements
  • business rules
  • implementation guide specific conformance rules
  • technical business rules and conventions
  • package contents (one per interaction) 1..*
  • introduction
  • scope
  • boundaries & relationships
  • actors involved
  • interactions
  • sender and receiver responsibilities
  • list of structures, extensions
  • list of invocations
  • terminology
  • naming systems
  • mappings
  • examples
  • implementation guidance
  • privacy and security guidance
  • privacy policy
  • security architecture
  • implementation guidance
  • testing and certification
  • test
  • certification procedure
  • appendix
  • acronyms and abbreviations
  • glossary
  • licenses
  • integrated examples
  • validation artifacts
  • links to platforms, binaries, software libraries
  • index
  • operational information
  • FAQs
  • Reference, literature

More details can be found in the document itself (on FHIR document server).

At you will be able to find the document we discussed in the Q3+Q4 meeting in Atlanta. It lists the suggested sections and content for an Implementation Guide, while being as standard-neutral (v2/v3/fhir) as possible.

Thursday

CGIT Q1: Vocabulary

Chair: / Ted Klein (Vocabulary)
Scribe: / Heather Graham
Attendees: / Please see vocabulary minutes
Quorum: / Yes
Remarks: / Please see vocabulary minutes

Q2 Vocabulary

Chair: / Ted Klein (Vocabulary)
Scribe: / Heather Graham
Attendees: / Please see vocabulary minutes
Quorum: / Yes
Remarks: / Please see vocabulary minutes

Friday

No meetings

Attendees:

1