This wiki has undergone a migration to Confluence found Here
Conformance Weekly Meeting 2018 05 21
Revision as of 13:04, 21 May 2018 by Nathan Bunker (talk | contribs) (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...")
Contents
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
- Web Meeting: Free Conference Call
Proposed Agenda Topics
Topics to discuss:
- Cologne WGM
- Length Discussion
- Discussion about FHIR Strategy
- FHIR Ballot coming up, need to make sure all conformance issues have been addressed
Discussion
- Some adjustments to Cologne WGM
- FHIR Ballot - FHIR Strategy
- Sign up period is over now, no chance to sign up now
- Rob is signed up for some HL7 v2 but no one is signed up for FHIR
- Through vocabulary there has been some input to FHIR, but for conformance we have not had to have much impact on FHIR
- Here is what is normative for this ballot: http://hl7.org/fhir/2018May/ballot-intro.html
- Are there other areas we need to put a negative comment (somehow)?
- 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.
- Universal Terminology Governance (UTG) Project
- 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.
- Length Discussion
- General philosophy for how to define and constrain lengths between types and fields, and how derived specifications may modify these constraints.
- 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.
- General philosophy for how to define and constrain lengths between types and fields, and how derived specifications may modify these constraints.
Attendees
- Rob Snelick
- Frank Oemig
- Nathan Bunker
- Craig Newman
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
- 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
- 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
- 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.