Confluence will be upgraded on October 20th, 2020 beginning at 6 AM EST. Estimated downtime is 2 hrs. Please email with any questions.
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


Call Details:

 Click for Call Details

Zoom Information

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:


 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!






Owned By

Export Records: 0



  1. Call to order 
  2. Call for Attendance

  1. STU/FHIR Tracker Comments resolution
    1. FHIR-24671 -DocumentReference.category and others
  2. 12:30 - UDI Discussion Marti Velezis
  3. New Comments process (Jira Migration)- Andrew


  1. STU/FHIR Tracker Comments resolution
    1. FHIR-24671 - DocumentReference.category and others
      1. The group reviewed 24671, the Document Class Value Set - there is a need for guidance documents (IHE has produced a document on this topic).
      2. May want to consider how to being this into HL7 to support the FHIR support for XDS support.
      3. we need some followup internally at HL7 on this issue and then talk to IHE.
  2. 12:30 - UDI Discussion Marti Velezis
    1. With UDI we have both supplemental C-CDA template or UDI and the C-CDA companion guide.
    2. Question do we need both?
      1. The only item identified is the UDI pattern which takes you to the C-CDA companion guide
      2. The Supplemental C-CDA template for UDI
    3. Given the different design principles, and potential use cases, there may be a need to adjust the requirements.
    4. If we need to make changes, then it could be submitted in a SFAB.  There are errata to both, a number of STU comments have been documented.
    5. Summarize - Take what is in the companion guide recommendation and move it over into the Supplemental as the relaxed historical data.
  3. New Comments process (Jira Migration)- Andrew
    1. Andrew shared some back ground on the changes occurring, a new process to capture comments and feedback from implementers of our standards and other documents.  They will all be stored in a single platform in Jira.  The Jira info will support links into confluence and can be used to display lists of Jira items.  What was shared is in the Dev environment
      1. Project = A. Specification Feedback (CDA) for all of the CDA stuff
      2. Issue Type = comment, question or a change request
      3. Specification = the specific document that you want to submit a comment on.
        1. A change will need to be made to change the version reference
      4. Version = needs to reference the version of the published standard documents.
      5. Summary = summarize the issue
      6. Related artifacts = (nothing specific called for)
      7. On the advanced tab - the Work Group
      8. The star fields are the required fields.



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.