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

Difference between revisions of "Conformance Weekly Meeting 2017 01 30"

From HL7Wiki
Jump to navigation Jump to search
Line 22: Line 22:
 
***Tooling not working correctly due to Windows version. Tooling is on many different machines. Code can't be migrated.
 
***Tooling not working correctly due to Windows version. Tooling is on many different machines. Code can't be migrated.
 
***How to do edits, inserts are pretty tricky. This needs to be figured out. A lot of open questions that are not answered yet.
 
***How to do edits, inserts are pretty tricky. This needs to be figured out. A lot of open questions that are not answered yet.
 +
**Discussing length of fields in HL7 2.x
 +
*** Conformance length is informative
 +
*** When you profile then how do set a normative length? There is a gap in the profile for being able to specify this. Truncation is something we have.
 +
**Minutes approved (Rob/Frank) 2-0-1
 +
===Todo===
 +
*Nathan check to see if language change is in ballot reconciliation for InM.
 +
*Add to gForge, when we write 2B we need to address the issue of not having a normative declaration for length.

Revision as of 20:42, 30 January 2017

Return to Conformance

Meeting Information

Proposed Agenda Topics

  • Approve minutes from January WGM
  • Review of todo items

Attendees

Discussion

  • Going over minutes from WGM
    • Discussed Frank's HL7 v2+ tooling project
      • Will this tooling be used in previous versions? Still a work in progress, using 2.8.2 as the basis for development. Might be used for previous version, maybe 2.5, but might not have everything needed.
      • Extracting process is not 100% correct. Some things have to be adjusted by hand.
      • Tooling not working correctly due to Windows version. Tooling is on many different machines. Code can't be migrated.
      • How to do edits, inserts are pretty tricky. This needs to be figured out. A lot of open questions that are not answered yet.
    • Discussing length of fields in HL7 2.x
      • Conformance length is informative
      • When you profile then how do set a normative length? There is a gap in the profile for being able to specify this. Truncation is something we have.
    • Minutes approved (Rob/Frank) 2-0-1

Todo

  • Nathan check to see if language change is in ballot reconciliation for InM.
  • Add to gForge, when we write 2B we need to address the issue of not having a normative declaration for length.