Skip to end of metadata
Go to start of metadata

Date: 2020-03-12 

Facilitator:  Nick Radov

Note Taker: Riki Merrick

Join the online meeting:





Mayo Clinic
XUnited Healthcare

Kaiser Permanente
XVernetzt, LLC
X Constable Consulting 
XKnapp Consulting
XKeith SalzmanBookzurman
XJason SmithElemental Reasoning

Create Decision from template

Agenda Topics

Agenda Outline

Agenda Item

Meeting Minutes from Discussion

Decision Link(if not child)

ManagementNotification of planned block vote for DaVinci Notifications ballot

Notification was sent out to INM listserve on March 2, 2020:

about this planned Block Vote 1 for Da Vinci Unsolicited Notifications IG for next week's INM WG Conference Call:
Thursday Mar 12, 2020 - 03:00 PM (Eastern Time, GMT -04 DST)
call details

These are mostly technical errors.  Let me know if you would like to pull an item out to discuss. You will get another opportunity on the call to remove an item:

Jira Issue Summary (Reporter)

  1. J#26291: Thanks for reusing US Core resources (rgeimer)
  2. J#26287: "Remove ""{b}"" from profile references" (seanmcilvenna)
  3. J#26286: No need to explicitly require MessageHeader.focus.reference (seanmcilvenna)
  4. J#26283: Links to other specifications (seanmcilvenna)
  5. J#26281: "Change file name from ""guidance.html"" to ""Framework.html""" (seanmcilvenna)
  6. J#26279: "Suggest changing ""changes in patient status"" to ""changes in patient chart""" (seanmcilvenna)
  7. J#26263: fix typo (RikiM)
  8. J#26242: keep note to balloters2 (RikiM)
  9. J#26229: "[base]$process-message missing ""/""" (fangcao)
  10. J#26194: remove obscuring references (pknapp)
  11. J#26189: consistent use of Alert vs unsolicited notification (pknapp)
  12. J#26188: remove DEQM actors (pknapp)
  13. J#26185: Implementation Requirements: Profile Support (ginocanessa)
  14. J#26184: Question: Filtering / Patient Lists (ginocanessa)
  15. J#26183: Question: Out Of Scope: Endpoint Discovery and maintenance (ginocanessa)
  16. J#26180: Value Set Concept Duplicates (ginocanessa)
  17. J#26179: Value Set Naming Convention Consistency (ginocanessa)
  18. J#26174: "Figure 4, GET and Search" (ginocanessa)
  19. J#26170: Intro sentence is a fragment (ginocanessa)
  20. J#26102: Broken Link (Brett.Marquard)

Since this agenda wasn't prepared we postponed to next call.

Also we have a created a Block of A-T comments (pre-applied), which we hope to get a motion on:

MethodologyGuidance for data sharing (30 Minutes?)
  • see link to document below
    • VA stragey team shared their comment document (see below)

    • reviewed specifically the table in the aboe referenced document
      • Sync/Async – Sync = request/response, but there may not be a lot in the response

      • Process – if set to NO means it is about having the resource(s), not so much doing anything with it

      • This made bundle a packaging mechanism

      • Can make CRUDSH actionable by including an actionable tag

        • Double-check task in R4

          • How do you give timeframe in task?

          • Use restriction.period maybe

          • task requires the additional resource to give the detail around what needs to be done

          • for updating claims – how would that work – create a task and a service request that then references the existing claim?

      • this table compiles the features of the different FHIR exchange mechanisms
    • Next we need to identify the criteria we collected in the Data Sharing matrix first column and how they apply to the different FHIR mechanisms collected in the comment document
    • Then apply those findings to the different use cases to help identify which combination would apply to that use case
  • Created matrix: See Data Sharing matrix
    • added a row for examples and started writing up the unsolicited notification criteria
    • Will send feedback to Lloyd when summary has been completed

[to edit the spreadsheet in the confluence page: click on EDIT, make changes in the spreadsheet, make sure you save before closing the spreadsheet and then update the confluence page]

MethodologyV2 Quality Criteria Reconciliation

NOT DISCUSSED TODAY, kept here to carry forward to the next agenda

MethodologyAscii Character set GF25232

NOT DISCUSSED TODAY, kept here to carry forward to the next agenda

  • HL70396 update:
  • Suggest to delete the word ASCI from the description and the comment column and also fix the last sentence, which is not complete for 99zzz or L:
  • In description change: The 'zzz' SHALL be any printable ASCII string.  to: The 'zzz' SHALL be any printable string.
  • In comments change: The 'zzz' may be any printable ASCII string of variable length, but the recommendation is to generally use only numbers and upper
    to: The 'zzz' may be any printable string of variable length, but the recommendation is to generally use only numbers and upper case.
  • There are languages that don't have upper case - so remove the part of the sentence after the comma.
  • Do we need to mention alternative charactersets like unicode, but it could be others? - better not
  • This table is only used as ID datatype so that takes care of allowing white spaces
  • Proposal:
    • Remove ASCII from the description and Comment, and fix the last line of the comment. e.g.
    • The 'zzz' may be any printable ASCII string of variable length as restricted by the ID datatype., but the recommendation is to generally use only numbers and upper case. (Case is added)
  • There is an issue with the HL70396 content in V2.9 vs the webpage - we need a single source of truth
  • Defer to next teleconference and let Ted know to update the web

MethodolodyV2 Mgmt referred: GF15630

NOT DISCUSSED TODAY, kept here to carry forward to the next agenda

  • gForge ticket has the original proposal attached
  • Research and defer to next tcon

Management Next agenda

 Adjourned at 3:55 PM ET

Supporting Documents