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

Difference between revisions of "Conformance Weekly Meeting 2018 05 21"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "=Meeting Information= *Date: Monday, April 23, 2018 *Time: 10:00 am, North America Eastern Time (New York, GMT-04:00) *Phone Number: +1 515-739-1227 *Pass Code: 732544 *We...")
 
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
=Meeting Information=
 
=Meeting Information=
  
*Date: Monday, April 23, 2018
+
*Date: Monday, May 21, 2018
 
*Time: 10:00 am, North America Eastern Time (New York, GMT-04:00)   
 
*Time: 10:00 am, North America Eastern Time (New York, GMT-04:00)   
 
*Phone Number: +1 515-739-1227  
 
*Phone Number: +1 515-739-1227  
Line 9: Line 9:
 
===Proposed Agenda Topics===
 
===Proposed Agenda Topics===
 
Topics to discuss:
 
Topics to discuss:
*Cologne WGM
+
*Cologne WGM Debrief
 +
**Next Action items
 +
*Baltimore WGM Room Assignments
 
*Length Discussion
 
*Length Discussion
 
*Discussion about FHIR Strategy
 
*Discussion about FHIR Strategy
 
**FHIR Ballot coming up, need to make sure all conformance issues have been addressed
 
**FHIR Ballot coming up, need to make sure all conformance issues have been addressed
 +
*Ballot reconciliation of the standardized data type flavors library
  
 
===Discussion===
 
===Discussion===
*Some adjustments to Cologne WGM
+
*Going over agenda for these meetings
*FHIR Ballot - FHIR Strategy
+
*Data Type Flavors Library Ballot Reconciliation
**Sign up period is over now, no chance to sign up now
+
**Some discussion about comments during Cologne meeting
**Rob is signed up for some HL7 v2 but no one is signed up for FHIR
+
**Nothing overwhelmingly negative
**Through vocabulary there has been some input to FHIR, but for conformance we have not had to have much impact on FHIR
+
**Need to make sure that the actual data types have been reviewed, not just the overall concept, need to reach out to authors of V2 guides to ask them to look at them
**Here is what is normative for this ballot: http://hl7.org/fhir/2018May/ballot-intro.html
+
*Cologne debrief
**Are there other areas we need to put a negative comment (somehow)?
+
**Steering Division: Gave a brief presentation of the PSS for conformance model for V2. They approved it. So we are on track to ballot in September.  
**Need to join FHIR Infrastructure calls? Will be another meeting in 4 hours today. Frank and Rob will try to join, to listen to what is going on.  
+
**Reviewed the data type flavors from the ballot
*Universal Terminology Governance (UTG) Project
+
**Tooling session: Rob presented on NIST tooling and Richard both presented on Touchstone. There was a contingent of students there interested in tooling.  
**Next meeting is tomorrow. Looking to see what to do with the vocabulary concepts, moving into FHIR. Moving in a very different direction, and this will be problematic. Doing it the easiest way. The past work that HL7 has done is being ignored.  
+
**FHIR topic, FHIR strategy. Had a fairly large crowd. Michel and Grahame. Representing FHIR in v2 structures. Connectathon track for validation and compare it to V2.  
*Length Discussion
+
**Interesting discussion with Vocabulary about extensibility. If I don't know anything I can go ahead and send you a code. But how do you profile something that is extensible? There are a lot of mechanics that are not well defined or explained. Not really in V2 either but will be addressed by new conformance methodology. Talking about value set being required.
**General philosophy for how to define and constrain lengths between types and fields, and how derived specifications may modify these constraints.
+
*Rob is going to prepare for discussion next week about Data Type Flavors ballot.
***Is length something that should even be constrained? Conformance length is just an idea.  
 
***Was going to propose a normative statement. If we want to keep length in V2 then this would be useful.
 
  
 
===Attendees===
 
===Attendees===
*Rob Snelick
+
* Craig Newman
*Frank Oemig
+
* Nathan Bunker
*Nathan Bunker
+
* Rob Snelick
*Craig Newman
 
  
 
===Todo List===
 
===Todo List===
*Nathan
 
**Send out notes for WGM
 
**Create PSS for Unified Conformance and Constraint Modeling
 
**Ask Dave Hammill why projects 1097,1096, and 1095 are still open
 
**Create Position Statements:
 
***Version Support
 
***Conformance Length and Truncation (one PS or two)
 
***Assumptions
 
***Query Ids and Versions
 
***Best Practice for Conformance Statement vs Small Value Set
 
**Send link to blog to group https://www.linkedin.com/pulse/fhir-nuts-bolts-versioning-chris-grenz
 
**Reach to Ioana to get the Cross Paradigm Implementation Guide so group can review and will put agenda to discuss
 
**Follow up with InM about proposal to retire "original mode"
 
*Ioana
 
**FHIR Versions: Ioana was going to work with Mario from AEGIS to write test scripts for testing version support in FHIR. Mario is going to take the first step and then work with Ioana.
 
*Rob
 
**Data Type Flavors: Rob and Craig will continue to work on this and then evaluate at next WGM to see if this should become an official conformance PSS
 
  
 
===Discussion===
 
===Discussion===
*HL7 WGM Agenda
 
**Discussed WGM, updated plans
 
**Rob will reach out an invite people to the Conformance in the Immunization Space
 
*Testing FHIR Version
 
**There is a test track in the next FHIR Connectathon to test versioning
 
**Here is the link to the track: [http://wiki.hl7.org/index.php?title=201801_Versioned_API http://wiki.hl7.org/index.php?title=201801_Versioned_API]
 
**Questions or comments just email to Richard
 
*Data Type Library
 
**Went through V2 Ig's, lab, immunization and newer vital records guide. Skipped some older guides that had poor examples of data types. Added a context for each of the data types. There is word document that is an output from IGAMT and a spreadsheet with a tab for every type. Looks pretty close for what would go out for balloting. Need an introduction that Rob Snelick is going to write. But the technical content is basically ready. The group needs to review this work.
 
***Need to define a set of attribute: Versions, Description/Purpose, Recommended Use, Example (?). Need to add a summary table, either in the appendix or at the front. That can be added to the IGAMT tool as a new requirement.
 
**Next steps and planning
 
***Ready for a May ballot? Craig things so as long as we don't go in a different direction. Group seems to be on board with this direction. May ballot is due mid-to-late March. What is holding us up is the PSS. Has to
 

Latest revision as of 14:49, 21 May 2018

Meeting Information

  • Date: Monday, May 21, 2018
  • Time: 10:00 am, North America Eastern Time (New York, GMT-04:00)
  • Phone Number: +1 515-739-1227
  • Pass Code: 732544
  • Web Meeting: Free Conference Call

Proposed Agenda Topics

Topics to discuss:

  • Cologne WGM Debrief
    • Next Action items
  • Baltimore WGM Room Assignments
  • Length Discussion
  • Discussion about FHIR Strategy
    • FHIR Ballot coming up, need to make sure all conformance issues have been addressed
  • Ballot reconciliation of the standardized data type flavors library

Discussion

  • Going over agenda for these meetings
  • Data Type Flavors Library Ballot Reconciliation
    • Some discussion about comments during Cologne meeting
    • Nothing overwhelmingly negative
    • Need to make sure that the actual data types have been reviewed, not just the overall concept, need to reach out to authors of V2 guides to ask them to look at them
  • Cologne debrief
    • Steering Division: Gave a brief presentation of the PSS for conformance model for V2. They approved it. So we are on track to ballot in September.
    • Reviewed the data type flavors from the ballot
    • Tooling session: Rob presented on NIST tooling and Richard both presented on Touchstone. There was a contingent of students there interested in tooling.
    • FHIR topic, FHIR strategy. Had a fairly large crowd. Michel and Grahame. Representing FHIR in v2 structures. Connectathon track for validation and compare it to V2.
    • Interesting discussion with Vocabulary about extensibility. If I don't know anything I can go ahead and send you a code. But how do you profile something that is extensible? There are a lot of mechanics that are not well defined or explained. Not really in V2 either but will be addressed by new conformance methodology. Talking about value set being required.
  • Rob is going to prepare for discussion next week about Data Type Flavors ballot.

Attendees

  • Craig Newman
  • Nathan Bunker
  • Rob Snelick

Todo List

Discussion