Chair: Stan Huff
Scribe: Stan Huff
Attendees
Present | Name | Affiliation |
---|---|---|
PenRad | ||
Susan Matney | Intermountain | |
Reed Gelzer | ||
Nathan Davis | Intermountain | |
Paul Seville | ||
Kurt Allen | Eir Solutions | |
Stan Huff | Intermountain |
Minutes Approved as Presented
X |
---|
The detail proposed agenda is:
- Record this call
- Agenda review
- Meeting with AMA, discussion about device vs. measurementDeviceExt - Nathan Davis
- Suggested solution for now
- Need a codeable device and the observation.device (reference). This will be available as a choice in R5.
- We can precoordinate device and qualifiers (e.g. manual with adult cuff)
- We can make corrections as new use cases might require
- Suggested solution for now
- Call schedule
- Do we want to cancel on March 12 (HIMSS)?
- We will keep the meeting for now
- Do we want to cancel on March 12 (HIMSS)?
- Planning for upcoming ballots
- Vital signs (September)
- The goal would be that what we are balloting would become the FHIR Core vital signs
http://build.fhir.org/ig/HL7/cimi-vital-signs/branches/master/index.html
- Skin and wound and assessment (September with Podiatrists)
- Quantitative lab (January 2021)
- Pain assessment (January 2021)
- Breast radiology - CIC sponsor, CIMI co-sponsor (May ballot)
- Vital signs (September)
- Discussion about Connectathons - Susan Matney
- Planning for May Connectathon: Vital signs, Wound assessment
- Questions for HL7
- Do we need to test all attributes in the resource or profile?
- Besides knowing the structure is appropriate we need have some way of verifying that the clinical content covers the domain of interest
- Updates on a number of different fronts - Kurt and Richard
- Have made good progress on the high level model (template) for things like breast radiology, anatomic pathology, etc.
- Mark - may want to use abstract profile for some items (take up this topic in some "next" meeting)
- Quantitative lab, coded lab, panel, etc. (helper labs, patterns)
- Also show examples of specific patterns
- Also show the tables for detailed content
- Next week we will do a deep dive on high level structures - Richard and Kurt
- Review of CIMI sessions at Sydney
- Patient Care discussion
- Dependent Observation patient care discussion - https://confluence.hl7.org/pages/viewpage.action?pageId=66918525#id-2020FebWGMPatientCare-WedQ1
- Motion: Submit a Change Request to add a qualifier back bone element in Condition resource using a structure similar to Observation.component.
- Tracker item was entered by Stephen Chu
- Stan wants Observation to be contained within the Condition so that you do not have to step over to Observation. Mark notes that the backbone element in Observations should allow recursiveness. That would mean qualifier in qualifier. We do not want a reference. We want to be recursive.
- CIMI to model examples
- Susan schedule time on Patient care agenda with Michelle
- Motion: Submit a Change Request to add a qualifier back bone element in Condition resource using a structure similar to Observation.component.
- Precondition – CIMI using temporal period
- Proposed new backbone element “Temporal Period” instead of using Precondition
- CIMI discussion 20 Feb 2020
- To be added to a future agenda
- Issue of better structure for components on components (pertains to the discussion on abstract profiles)
- We need to define requirements first to make sure proposed solutions cover the requirements
- We need a "meaning code" in FHIR extensions
- Dependent Observation patient care discussion - https://confluence.hl7.org/pages/viewpage.action?pageId=66918525#id-2020FebWGMPatientCare-WedQ1
- Patient Care discussion
- Orders and Observations
- FHIR Body Site Data Type - https://confluence.hl7.org/display/OO/OO+WGM+Meeting+Minutes%3A+February+4+-+7%2C+2020#OOWGMMeetingMinutes:February47,2020-Q3.1
- Motion to recommend to FHIR-I create an Anatomical Location Data Type that enables post coordinated body locations documentation an establish an approach that enables consistent use of pre- and post-coordinated strategies given observation is normative by Stan Huff, Loraine Constable
- Next steps: Reach out to Patient Care and CDS to add it to procedure, Condition, etc. to the list.
- CIMI discussion 20 Feb 2020
- Separate the need for Anatomical Location DT from when to use it versus BodyStructure
- We (CIMI) need to join the O&O sessions where this will be discussed
- Susan will review the openEHR implementation of anatomic location
- FHIR Body Site Data Type - https://confluence.hl7.org/display/OO/OO+WGM+Meeting+Minutes%3A+February+4+-+7%2C+2020#OOWGMMeetingMinutes:February47,2020-Q3.1
- Meeting with U.S. Realm https://confluence.hl7.org/pages/viewpage.action?pageId=66943119
- Skin and Wound Assessment PSS
- PSS was approved
- Skin and Wound Assessment PSS
- Lunch meeting with FHIR-I
- New interpretation of use of SNOMED (or other proprietary terminologies) and International IGs
- Meaning of concepts defined by reference to SNOMED, but use of local codes with the same meaning would be considered as compliant
- Define a “SNOMED realm” – all the countries that have licenses for SNOMED
- We should do this also (second choice)
- Add needed items to the “free use” SNOMED list (first choice)
- Susan will send concepts to Grahame to add
- CIMI discussion 20 Feb 2020
- Issue of using SNOMED CT codes in international
* if the IG requires the use of SNOMED CT to conform to it, then it must be published by realm with a SNOMED CT license, or the concepts must be licensed for free use for all applicable implementers.
- Issue of using SNOMED CT codes in international
- How can CIMI be of most value to the FHIR community?
- Problem – many domain specific IGs
- Proposal
- CIMI review and vote on IGs to make them as consistent as possible
- Enumerate high level patterns for people to use
- Proposal
- Problem – many domain specific IGs
- Process for reuse of FHIR profiles in IGs – openEHR and Intermountain experience
- People should specify what “type” of IG they are using – domain, exchange, etc.
- Additional option: put all profiles in a library and “#include” the profiles in the implementation guides. All profiles are in one place and can be easily indexed. Usage information can also be included. For further discussion.
- New interpretation of use of SNOMED (or other proprietary terminologies) and International IGs
- Strategy for what content to ballot, all models, or just important patterns? - Stan Huff
- "Mixins" or "Fragments" that would be common building blocks for provenance, roles, participations, etc.
- Any other business
Conference Call Information
HL7 CIMI Planning and Oversight meeting
https://global.gotomeeting.com/join/455549973
United States: +1 (571) 317-3112
Access Code: 455-549-973