Call Details:
Attendees:
Agenda:
10:00am ET
- Call to order
- Business Updates (10 min)
- Additions/modifications to the agenda
- HL7
- Review Project Proposals
- External Updates - ONC and others
- Project Updates
- C-CDA - Roadmap: Errata Updates, changes, long-term plans
- Please sign up here if you want to participate - Wednesday, December 2nd at 11 am ET is winning so far for the start of 3-4 recurring meetings
- Additional Items
- Extensions
- Reballot of C-CDA on FHIR for "Mapping Rules" esp wrt participant mappings within the resources
- PCWG/SD/FHIR I notes: 2020 Sept WGM Patient Care Agenda and Minutes
- HAI ballot review David DeRoode
Personal Advance Care Plan STU comment 2062 Natasha Kreisle
- Need to evaluate all SDWG CDA standards to assign current status
- STU Comments [ Comment Tracker ]
- FHIR Tickets [ JIRA ]
Notes/Minutes:
- Business Updates (10 min)
- Additions/modifications to the agenda - none
Approve minutes from 2020-11-12 Agenda and Minutes
Approved by general consent- HL7
- RIM (Austin Kreisler) - no updates; possibly remove
- M&M call - reaffirmation of current version of RIM; remind other workgroups with RIM artifacts to consider evaluating
- Steering Division / TSC (Austin Kreisler)
- Ballot cycle deadlines: Dec 13 content deadline; Dec 18 ballot opens; Dec 27 deadline for 2021 TSC approval of PSS for 2021 MAY
- CDA-MG (Lisa R. Nelson, Linda Michaelsen )
- Review of value sets used in CDA standards in/not in UTG
- Web IG Publishing Scope - working on defining scope/focus
- CDA on FHIR "is available" is not a conversion; it's the CDA FHIR Logical Model - CDA mapped using StructureDefinition resources: https://build.fhir.org/ig/HL7/cda-core-2.0/index.html
- Vocab (Rob McClure) - not present
- Publishing, Electronic Services and Tools (PEST) (Andrew Statler) - not present
- Patient Care (Emma Jones)
- Working on Care Plan DAM 2.0
- Example Task Force (https://cdasearch.hl7.org) (Brett Marquard) - not present
- Will meet today
- RIM (Austin Kreisler) - no updates; possibly remove
- Review Project Proposals
- No changes
- External Updates - ONC and others
- Lindsey Hoggle - new US Realm Program Manager for HL7 - gather everything related to US Realm
- Project Updates - none
- C-CDA - Roadmap: Errata Updates, changes, long-term plans
- Please sign up here if you want to participate - Wednesday, December 2nd at 11 am ET is winning so far for the start of 3-4 recurring meetings
- Additional Items
- Extensions - no updates
- Reballot of C-CDA on FHIR for "Mapping Rules" esp wrt participant mappings within the resources
- Re-clarification that this is representing C-CDA using FHIR Resources
- PCWG/SD/FHIR I notes: 2020 Sept WGM Patient Care Agenda and Minutes
- Austin - consider adding this as a Parking Lot item/page in Confluence
- HAI ballot review David DeRoode
- Hoping to get an approval vote ready in a couple of weeks
- Adding COVID-related codes
- Problems with closed template "Confirmed or Suspected COVID-19" - people are encouraged to comment!
- How many people know these templates are being produced? Circulated by NHSN awhile ago.
- Will discuss in Examples Task Force
Personal Advance Care Plan STU comment 2062 Natasha Kreisle
Type Motion Motion Remove the word "the" from the sentence.
By NKreisle
Second CBeebe
Ref # comment 2062 For 26 Neg 0 Abs 0 Status APPROVED
Tally 26-0-0 - Will consider block vote for future comments
- Need to evaluate all SDWG CDA standards to assign current status
- Standards for Review - For Distribution-sdwg.xlsx
- Please review
- STU Comments [ Comment Tracker ]
HL7 CDA® R2 IG: C-CDA Templates for Clinical Notes DSTU Release 2 & 2.1 - US Realm
Type Motion Motion Motion to accept proposed rewording
By Second Date Ref # http://www.hl7.org/dstucomments/showdetail_comment.cfm?commentid=2080 Status APPROVED
Tally 26-0-0 - http://www.hl7.org/dstucomments/showdetail_comment.cfm?commentid=1981
- Lisa R. Nelson why can't this one example be ED?
- Marti Velezis it can; we should add guidance that if the data is not in the narrative, ED can still contain the text.
- Brett Marquard - table this for now; need to reopen a comment, but will discuss in task force first
Adding "sdtc:" before functionCode in companion guide
Type Motion Motion Motion to adopt the above proposed wording
By Second Date 11/19/2020
Ref # http://www.hl7.org/dstucomments/showdetail_comment.cfm?commentid=2048 Status APPROVED
Tally 25-0-0 Medication route translation restriction
Type Motion Motion Instead of the proposed wording, utilize the "such that it" Trifolia capability to enable sending additional translations. New Prposed wording: The routeCode, if present, SHOULD contain zero or more [0..*] translation (CONF:4483-32960) such that it 1. SHALL contain exactly one [1..1] @code, which SHALL be selected from ValueSet Medication Route urn:oid:2.16.840.1.113762.1.4.1099.12 DYNAMIC (CONF:4483-32961).
Motion: Accept the new proposed wording
By Second Date Ref # http://www.hl7.org/dstucomments/showdetail_comment.cfm?commentid=2035 Status APPROVED
Tally 23-00-00 ClinicalDocument/code/@code requirement on Consult note, Referral Note, Transfer Summary
Consult Note must be backwards compatible with 1.1, so this is fine to change (was already required via backwards compatibility). Referral Note / Transfer Summary were new in 2.0/2.1, so this would be a design change request for those two templates (however consistent and more usable it would be); motion limited to only changing this for Consult Note.Type Motion Motion This is an Errata for one of the three proposed changes: (Consult Note, R2.1) 3. SHALL contain exactly one [1..1] code (CONF:1198-17176). a. This code SHALL contain exactly one [1..1] @code, which SHALL be selected from ValueSet ConsultDocumentType urn:oid:2.16.840.1.113883.11.20.9.31 DYNAMIC (CONF:1198-17177). The other two proposed changes need to be resubmitted as a separate STU comment since they need to be handled as Design Changes (not errata).
Motion to alter CONF:1198-17176 & CONF:1198-17177 as worded above
By Second Date 11/19/2020
Ref # http://www.hl7.org/dstucomments/showdetail_comment.cfm?commentid=2039 Status APPROVED
Tally 23-0-0 Invalid example 2040
Type Motion Motion Motion to correct the example as proposed.
By Second Date 11/19/2020
Ref # http://www.hl7.org/dstucomments/showdetail_comment.cfm?commentid=2040 Status APPROVED
Tally 23-0-0 Invalid example 2047
Type Motion Motion Figure 137: Criticality Observation Example <value xsi:type="CD" code="High" displayName="High Criticality - NEED PROPER CODE" codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED CT"/>
Looks like we published this without ever fixing the code. The @code should be CRITH, the @displayName should be "high criticality", the @codeSystem should be 2.16.840.1.113883.5.10.63, and the @codeSystemName should be "HL7ObservationValue".
Proposed Wording <value xsi:type="CD" code="CRITH" displayName="high criticality" codeSystem="2.16.840.1.113883.5.10.63" codeSystemName="HL7ObservationValue"/>
Motion is to adopt proposed wording in the example
By Second Date Ref # http://www.hl7.org/dstucomments/showdetail_comment.cfm?commentid=2047 Status APPROVED
Tally 22-0-0
- FHIR Tickets [ JIRA ]
Copyright © Health Level Seven International ® ALL RIGHTS RESERVED. The reproduction of this material in any form is strictly forbidden without the written permission of the publisher.