Skip to end of metadata
Go to start of metadata



To record your attendance at the SDWG Conference Call, click the sign-on button to the right:


Facilitator:

Austin Kreisler


Date:


Call Details:


 Click for Call Details

Zoom Information

https://us02web.zoom.us/j/465862913?pwd=cUllR1BndVpYNVpyR3dzc3VIUERTZz09

Meeting ID: 465 862 913

Passcode: 310940

Phone Information:

+1 312 626 6799 US (Chicago)
+1 929 436 2866 US (New York)
+1 301 715 8592 US (Germantown)
+1 346 248 7799 US (Houston)
+1 669 900 6833 US (San Jose)
+1 253 215 8782 US (Tacoma)
Find your local number: https://us02web.zoom.us/u/kb1hK2eKvz




Attendees:


 Click here to expand...

Meeting Attendance

To add your name to the attendance, exit Edit mode for this page and then click on the Submit button at the top of the page. Once you have submitted your attendance, the screen will indicate that you have already signed-in. Thank you!

Edit

Name

Name

Affiliation

E-mail

Owned By

Export Records: 0

Agenda:


10:00am EST

  1. Call to order 
    1. Call for Attendance


  2. Business Updates (10 min)
    1. Additions/modifications to the agenda
    2. Approve minutes from 2020-06-04 Agenda and Minutes

    3. HL7
  3. External Updates - ONC and others
  4. Project Updates
    1. Value Set Issues

      1. see 11:00am
    2. Provenance
    3. Other Project Updates
  5. Additional Items
    1. David Riddle If Brett Marquard is on, David had a topic from  that he wanted to touch on. Propagation of context.
    1. Administrative Review
      1. Normative specifications approaching expiration
        1. HL7 Implementation Guide for CDA® Release 2 - Level 3: Healthcare Associated Infection Reports, Release 2 - US RealmANSI/HL7 CDAR2IG HAIRPT, R2-20152015-11-16 00:00:00.02020-11-16 00:00:00.0Revision of ANSI/HL7 CDAR2IG HAIRPT, R1-2013
      2. Expiring STU's
        1. STUs Expiring in Next 6 Months
    2. RIM Modelling for Identifiers from CDA R3 (Austin)
    3. Tenative: HAI Ballot Comment Sarah Gaunt
  6. STU Comments
    1. #1971 - Name field vs US Realm Name
    2. #1980 - UDI Schematron Extension has leading spaces
    3. #1981 - Lot or Batch Number type of ED vs ST
    4. #1982 - Manufacturing date observations in Appendix B which is an optional template are imposing constraints that should be removed.
    5. #1983 - Order fulfillment conformance statement that are contradictory
    6. #1984 - Appendix C has a constraint with root, extension and NULL of UNK
    7. #1985 - The Provenance entry in the Appendix C is inconsistent with the author entry in the C-CDAr2.1 IG in terms of allowable values and it is misleading.
    8. #1986 - For the UDI information, can we get clarification on whether it is possible to send other information when we do not have the DI information?

11:00am EST

  1. Value Set Updates
  2. Value Set STU Comments
    1. #nnnn
  3. Adjournment

Notes/Minutes:


10:00am EST

  1. Call to order 
    1. Meeting called to order at 10:05am EST by Austin Kreisler  
    2. Call for Attendance


  2. Business Updates (10 min)
    1. Additions/modifications to the agenda
    2. Approve minutes from 2020-06-04 Agenda and Minutes

      1. Minutes approved by consent
    3. HL7
  3. External Updates - ONC and others
    1. August 10-11 ONC Tech Forum - New name for Interop Forum.
      1. https://www.onctechforum.com/
    2. Implementation-a-Thon is scheduled for July 29, 2020
  4. Project Updates
    1. Value Set Issues

      1. see 11:00am
    2. Provenance
    3. Other Project Updates
  5. Additional Items
    1. David Riddle If Brett Marquard is on, David had a topic from  that he wanted to touch on. Propagation of context.
    1. Administrative Review
      1. Normative specifications approaching expiration
        1. HL7 Implementation Guide for CDA® Release 2 - Level 3: Healthcare Associated Infection Reports, Release 2 - US RealmANSI/HL7 CDAR2IG HAIRPT, R2-20152015-11-16 00:00:00.02020-11-16 00:00:00.0Revision of ANSI/HL7 CDAR2IG HAIRPT, R1-2013
      2. Expiring STU's
        1. STUs Expiring in Next 6 Months
    2. RIM Modelling for Identifiers from CDA R3 (Austin)
      1. discussion about an STU identifier around PatientRole id OID and getting it to align with Organization OID for MRN. There may be other things as well. 
      2. A couple of new modeling constructs: identifiedBy, AlternateIdentification
        1. This was used in V3 in later versions, but not in the version that CDA is built on.
        2. There was discussion about adopting an extension.
        3. Interest in seeing the modeling.
      3. The identifiedBy could be attached to any entity that has identifiers (PatientRole, HealthCareProvider, PersonEmployee, Employee, Guardian, Subscriber, OrganizationPartOf, AssignedAuthor, IntendedRecipient, AssignedCustodian, AssignedDevice, HealthCareFacility, AssignedEntity, AccreditedLocation, AssociatedEntity
    3. Tenative: HAI Ballot Comment Sarah Gaunt
      1. Negative Ballot Comment - 3.70 NHSN Comment - Freetext field of less than 2000 characters. Discussed with the team and have proposed disposition of not persuasive. 
      2. We need to take this back to the team and look at the technical requirements.
      3. This is an IG from a specific implementation. If you have another implementation and you only want last name, how is that different?
        1. The difference is that the box is a freetext, and that imparts on application design.
      4. Consider for future use. Would need to change on the NHSN processing end. 
      5. We will have a meeting next week.
  6. STU Comments
    1. #1971 - Name field vs US Realm Name
      1. why didn't we use either of the templates? preference would be to use the person name template.
      2. US Person Name - shall be conformant with US Person Name or a string. Doesn't seem to be very strong to use these statements.
      3. Matt Szczepankiewicz has the use case where the result person is a free text string. It is a freetext string.
        1. Lisa R. Nelson states that is the performer rather than the author.
      4. Matt Szczepankiewicz talks more about the 
      5. Fallback is that you don't know the person name is that you populate the organization name. If you don't have it, you just paste in the org name.
      6. Because it has to do with Provenance. You only hang your hat on information you can hang your hat on. You can still put that information in the performer.
      7. We will need to come back to that.
      8. Matt Szczepankiewicz will come back with that.
    2. Emma Jones - Case Reporting - if she has comments, does she bring them to this workgroup? She can submit the comments as STU comments just like she does for comments on STUs owned by Structured Documents. The Case Reporting STU is owned by Public Health, so that Workgroup will need to take up those STU comments.
    3. #1980 - UDI Schematron Extension has leading spaces
      1. This appears to be a data entry error on the Lantana tooling for the Companion Guide Appendix B.
      2. TypeMotion
        Motion

        Motion to approve this disposition as noted

        By
        Second
        Date

         

        Ref #1980 
        For20
        Neg00
        Abs00
        Status

        APPROVED

        Tally20-00-00 
        Discussion

        No additional discussion

        Action

        Andrew Statlerto add to Companion Guide Errata Sheets

    4. #1981 - Lot or Batch Number type of ED vs ST
      1. Marti Velezis is going to take an action item to go research this one. The example does appear wrong. We will come back to this one. 
    5. #1982 - Manufacturing date observations in Appendix B which is an optional template are imposing constraints that should be removed.
      1. Marti Velezis is going to do some more research on this one and will bring this to the next meeting. She inherited this IG and her intent was to improve the quality. She needs to look at the history on this to understand the background on this conformance statement.
    6. These items were not covered today and will be moved to the next agenda:
      1. #1983 - Order fulfillment conformance statement that are contradictory
      2. #1984 - Appendix C has a constraint with root, extension and NULL of UNK
      3. #1985 - The Provenance entry in the Appendix C is inconsistent with the author entry in the C-CDAr2.1 IG in terms of allowable values and it is misleading.
      4. #1986 - For the UDI information, can we get clarification on whether it is possible to send other information when we do not have the DI information?
  7. Adjournment
    1. Our next meeting is on   
    2. Meeting adjourned at 12:02pm EST by Austin Kreisler

 


*Tip



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.