FHIR Chat · Announcements · Da Vinci CDex

Stream: Da Vinci CDex

Topic: Announcements

view this post on Zulip Eric Haas (Mar 03 2021 at 18:33):

Just a reminder that we will have our community today on Wednesday March 3/3/2021 2 - 3 PM ET

Conference Call Schedule & Dial-Ins

Wednesdays at 2pm Eastern

Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/514633709

You can also dial in using your phone.
United States: +1 (872) 240-3311

Access Code: 514-633-709

Agenda: Jan 2021 Ballot Reconciliation:

Review FHIR-30868 and FHIR-30869

FHIR#30867 - Lloyd proposed wording agreed to on call 2/17
FHIR#30868 - review Kathleen proposed wording based on 30867.
FHIR#30869 - review Kathleen proposed wording based on 30867.

On 2/24 - Left off with FHIR#30489 - add a section on Administrative Documentation TRIAGED - Eric to Draft resolution.

HREX related CDEX Comments:

FHIR#26855 CDex documents require signature, but don't explain how used
FHIR#30490 TRIAGED clinician burden reduction
FHIR#30858 TRIAGED Perhaps just call for current published version?
FHIR#30863 TRIAGED Is it purely a workflo decision whether a request is required to release patient data?

AMA Comments:

FHIR#30815 Not Persuasive Provider to Provider use case should be out of scope as it has not been tested.
FHIR#30816 Unresolved Please clarify whether any human involvement is required, and an example, as well as define the term fulfillment as it relates to attestation.
FHIR#30820 Unresolved When a task is complete what triggers the termination of a payer's ability to fetch data?
FHIR#30821 Unresolved When and how do data servers terminate a client's set of requests?
FHIR#30822 Unresolved What method is used to determine the end of a client's access to a data server?

3/10 Agenda: HRex Vassil's last question FHIR-28892 - The decision points tree does not seem to follow a natural approach TRIAGED

view this post on Zulip Eric Haas (Mar 09 2021 at 21:07):

Just a reminder that we will have our community today on Wednesday March 3/10/2021 2 - 3 PM ET

Conference Call Schedule & Dial-Ins

Wednesdays at 2pm Eastern

Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/514633709

You can also dial in using your phone.
United States: +1 (872) 240-3311

Access Code: 514-633-709

Agenda: Jan 2021 Ballot Reconciliation:

Review FHIR-30868 and FHIR-30869

FHIR#30867 - Lloyd proposed wording agreed to on call 2/17
FHIR#30868 - review Kathleen proposed wording based on 30867.
FHIR#30869 - review Kathleen proposed wording based on 30867.

On 2/24 - Left off with FHIR#30489 - add a section on Administrative Documentation TRIAGED - Eric to Draft resolution.

HREX related CDEX Comments:

FHIR#26855 CDex documents require signature, but don't explain how used
FHIR#30490 TRIAGED clinician burden reduction
FHIR#30858 TRIAGED Perhaps just call for current published version?
FHIR#30863 TRIAGED Is it purely a workflo decision whether a request is required to release patient data?
FHIR#30870 TRIAGED Clarifications

AMA Comments:

FHIR#30815 Not Persuasive Provider to Provider use case should be out of scope as it has not been tested.
FHIR#30816 Unresolved Please clarify whether any human involvement is required, and an example, as well as define the term fulfillment as it relates to attestation.
FHIR#30820 Unresolved When a task is complete what triggers the termination of a payer's ability to fetch data?
FHIR#30821 Unresolved When and how do data servers terminate a client's set of requests?
FHIR#30822 Unresolved What method is used to determine the end of a client's access to a data server?

Block Vote 1 Pulls:

FHIR#30831 TRIAGED Not Persuasive More missing content.
FHIR#30832 TRIAGED Not Persuasive The content of this IG wasn't quite ready for ballot. What HL7 process improvement is needed to prevent this in the future?

3/10 Agenda: HRex Vassil's last question FHIR-28892 - The decision points tree does not seem to follow a natural approach TRIAGED

view this post on Zulip Eric Haas (Apr 14 2021 at 00:08):

Just a reminder that we will have our Community Call on Wednesday March 4/14/2021 2 - 3 PM ET

Conference Call Schedule & Dial-Ins

Wednesdays at 2pm Eastern

Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/514633709

You can also dial in using your phone.
United States: +1 (872) 240-3311

Access Code: 514-633-709

Agenda: Jan 2021 Ballot Reconciliation:

Signature/attestation: Pending further discussion on Architecture Calls:

  1. FHIR#26855 CDex documents require signature, but don't explain how used -
  2. FHIR#30816  Unresolved Please clarify whether any human involvement is required, and an example, as well as define the term fulfillment as it relates to attestation.

HREX related CDEX Comments:

  1. FHIR#30148 In which IG is it more appropriate to apply this one?

AMA Comments:

  1. FHIR#30820  Unresolved When a task is complete what triggers the termination of a payer's ability to fetch data?
  2. FHIR#30821  Unresolved When and how do data servers terminate a client's set of requests?
  3. FHIR#30822  Unresolved What method is used to determine the end of a client's access to a data server?

Review Kathleen wording:

  1. FHIR#30868 - review Kathleen proposed wording based on 30867.
  2. FHIR#30869 - review Kathleen proposed wording based on 30867.

view this post on Zulip Eric Haas (Apr 14 2021 at 00:19):

Block Vote 3 For the Da Vinci CDEX v0.2.0 January Ballot

Trackers have been grouped into Block Vote 3 with proposed dispositions created and available for your review below. The vote for these blocks is scheduled for the next Patient Care Co-Chair Call Mon Apr-26-2021 05:00PM EST. If there are any items below that you would like to withdraw from the block vote for discussion please email me or respond on this stream.

CDEX Implementation Guide Ballot Build

Call details: Join Zoom Meeting - https://zoom.us/j/5328571160 | Meeting ID: 532 857 1160 | +1 929-436-2866-US (New York) | Find your local number: Find your local number: https://zoom.us/u/aemmW7I5Zo

Key:Summary (Reporter) Resolution

  1. FHIR#30489:add a section on Administrative Documentation (tony.benson) Persuasive with Modification
  2. FHIR#30490:clinician burden reduction (gdickinson) Persuasive with Modification
  3. FHIR#30494:Delete use of word complete as it is too extreme. (celine_lefebvre) Persuasive
  4. FHIR#30813:Remove word complete. (celine_lefebvre) Persuasive
  5. FHIR#30814:Question about use of referred-to. (celine_lefebvre) Persuasive with Modification
  6. FHIR#30815:Provider to Provider use case should be out of scope as it has not been tested. (celine_lefebvre) Not Persuasive with Modification
  7. FHIR#30817:Rephrase. (celine_lefebvre) Persuasive
  8. FHIR#30818:When and how are subscriptions terminated? (celine_lefebvre) Considered - Question answered
  9. FHIR#30819:Unclear how this imposes excessive P&S risks? Please explain. (celine_lefebvre) Persuasive with Modification
  10. FHIR#30824:Recommendation for exchanging purpose of use. (Isaac.Vetter) Considered for Future Use
  11. FHIR#30829:When would Task.reasonReference be a ServiceRequest? (Isaac.Vetter) Persuasive with Modification
  12. FHIR#30831:More missing content. (Isaac.Vetter) Persuasive with Modification
  13. FHIR#30832:The content of this IG wasn't quite ready for ballot. What HL7 process improvement is needed to prevent this in the future? (Isaac.Vetter) Not Persuasive
  14. FHIR#30837:Messaging not reflected in data flow. (hbuitendijk) Considered for Future Use
  15. FHIR#30858:Perhaps just call for current published version? (Thomson.Kuhn) Not Persuasive
  16. FHIR#30863:Is it purely a workflo decision whether a request is required to release patient data? (pknapp) Persuasive with Modification
  17. FHIR#30867:Purpose of use for a Direct Query must be conveyed in some manner. (k.connor) Persuasive with Modification
  18. FHIR#31516:remove reference to CommunicationRequest plus Task (ehaas) Persuasive

view this post on Zulip Eric Haas (Apr 26 2021 at 23:04):

Block Vote 4 For the Da Vinci CDEX v0.2.0 January Ballot

Trackers have been grouped into Block Vote 4 with proposed dispositions created and available for your review below. The vote for these blocks is scheduled for the next Patient Care Co-Chair Call Mon May-10-2021 05:00PM EST. If there are any items below that you would like to withdraw from the block vote for discussion please email me or respond on this stream.

CDEX Implementation Guide Ballot Build

Call details: Join Zoom Meeting - https://zoom.us/j/5328571160 | Meeting ID: 532 857 1160 | +1 929-436-2866-US (New York) | Find your local number: Find your local number: https://zoom.us/u/aemmW7I5Zo

Key: Summary (Reporter) Resolution

  1. FHIR#29683: Interop Framework for Payer2Payer and Internal Systems (michaelykim) Not Persuasive
  2. FHIR#30446: Scenarios to include the Payer's ability to use CDex to request additional information from the Provider that will be used to support claim submission - Attachments. (durwin_day) Persuasive with Modification
  3. FHIR#30820: When a task is complete what triggers the termination of a payer's ability to fetch data? (celine_lefebvre) Persuasive with Modification
  4. FHIR#30821: When and how do data servers terminate a client's set of requests? (celine_lefebvre) Persuasive with Modification
  5. FHIR#30835: Add to the benefits that it enables a transition strategy towards direct queries to individual resources to gather data of interest. (hbuitendijk) Persuasive with Modification
  6. FHIR#30836: Suggest to remove the statements as there always is authorization somewhere (hbuitendijk) Persuasive with Modification
  7. FHIR#31884: Expand paragraph with further explanation/examples (ehaas) Persuasive with Modification
  8. FHIR#31885: direct links to the specific section of HRex. (ehaas) Persuasive
  9. FHIR#31886: Specification re Authorization (ehaas) Persuasive with Modification
  10. FHIR#31887: restrict access to pertinent patients (ehaas) Not Persuasive with Modification

for an update on our progress towards resolving all the ballots comments see the CDEX tracker Dashboard

To see already applied comments, check out the Da Vinci CDex Continuous Integration Build

view this post on Zulip Eric Haas (May 14 2021 at 03:27):

Note Block Vote 4 has been moved to a new date and time - see next post below....

view this post on Zulip Eric Haas (May 14 2021 at 03:32):

Block Vote 4 For the Da Vinci CDEX v0.2.0 January Ballot

Trackers have been grouped into Block Vote 4 with proposed dispositions created and available for your review below. The vote for these blocks is scheduled for the MAY HL7 WGM Patient Care Monday May 24 Q4 Session (That is 12-1:30 Eastern) Mon May-10-2021 05:00PM EST. If there are any items below that you would like to withdraw from the block vote for discussion please email me or respond on this stream.

CDEX Implementation Guide Ballot Build

Call details: See the registration information for the HL7 May WGM.

Key: Summary (Reporter) Resolution

  1. FHIR#29683: Interop Framework for Payer2Payer and Internal Systems (michaelykim) Not Persuasive
  2. FHIR#30446: Scenarios to include the Payer's ability to use CDex to request additional information from the Provider that will be used to support claim submission - Attachments. (durwin_day) Persuasive with Modification
  3. FHIR#30497: Change should to SHALL as required by minimum necessary. (celine_lefebvre) Not Persuasive
  4. FHIR#30820: When a task is complete what triggers the termination of a payer's ability to fetch data? (celine_lefebvre) Persuasive with Modification
  5. FHIR#30821: When and how do data servers terminate a client's set of requests? (celine_lefebvre) Persuasive with Modification
  6. FHIR#30826: Better standardize Task.reasonReference by formalizing (but not limiting) the current scenarios (Isaac.Vetter) Persuasive with Modification
  7. FHIR#30835: Add to the benefits that it enables a transition strategy towards direct queries to individual resources to gather data of interest. (hbuitendijk) Persuasive with Modification
  8. FHIR#30836: Suggest to remove the statements as there always is authorization somewhere (hbuitendijk) Persuasive with Modification
  9. FHIR#30868: Confidentiality protection in a Direct Query must be conveyed in some manner. (k.connor) Persuasive with Modification
  10. FHIR#30869: The Sensitivity of the information in a Direct Query must be conveyed in some manner. (k.connor) Persuasive with Modification
  11. FHIR#31884: Expand paragraph with further explanation/examples (ehaas) Persuasive with Modification
  12. FHIR#31885: direct links to the specific section of HRex. (ehaas) Persuasive
  13. FHIR#31886: Specification re Authorization (ehaas) Persuasive with Modification
  14. FHIR#31887: restrict access to pertinent patients (ehaas) Not Persuasive with Modification
  15. FHIR#31888: audit trail available for clinician/patient (ehaas) Persuasive with Modification

view this post on Zulip Eric Haas (Jun 23 2021 at 23:46):

Block Vote 6 For the Da Vinci CDEX v0.2.0 January Ballot

Trackers have been grouped into Block Vote 6 with proposed dispositions created and available for your review below. he vote for these blocks is scheduled for the next Patient Care Co-Chair Call July-12-2021 05:00PM EST. If there are any items below that you would like to withdraw from the block vote for discussion please email me or respond on this stream.

CDEX Implementation Guide Ballot Build

Call details: Join Zoom Meeting - https://zoom.us/j/5328571160 | Meeting ID: 532 857 1160 | +1 929-436-2866-US (New York) | Find your local number: Find your local number: https://zoom.us/u/aemmW7I5Zo

Key Summary (Reporter) Resolution

  1. FHIR-30497 Change should to SHALL as required by minimum necessary. (celine_lefebvre) Not Persuasive
  2. FHIR-32116 Need to express the relationship between this guide and others (lloyd) Persuasive with Modification
  3. FHIR-32841 Provide guidance on finding organization and provider identifiers (lloyd) Persuasive with Modification

view this post on Zulip Eric Haas (Nov 01 2021 at 18:45):

Block Vote 6 For the Da Vinci CDEX v0.2.0 January Ballot

Trackers have been grouped into Block Vote 6 with proposed dispositions created and available for your review below. he vote for these blocks is tentatively scheduled for the next Patient Care Co-Chair Call Nov 8 05:00PM Eastern. If there are any items below that you would like to withdraw from the block vote for discussion please email me or respond on this stream.

Call details

Commenters:

  • @Ioana Singureanu
  • @Lloyd McKenzie
  • @Celine A Lefebvre
  • @Peter Muir

Key: Summary (Reporter) Resolution

  1. FHIR#23556: Is the searchset bundle used anywhere? - CDex #174 (ioana13) Considered - Question answered
  2. FHIR#26855: CDex documents require signature, but don't explain how used (lloyd) Persuasive
  3. FHIR#30497: Change should to SHALL as required by minimum necessary. (celine_lefebvre) Not Persuasive
  4. FHIR#30816: Please clarify whether any human involvement is required, and an example, as well as define the term fulfillment as it relates to attestation. (celine_lefebvre) Persuasive with Modification
  5. FHIR#30870: clarify when attribution is not present or non-repudiable (peter.muir) Persuasive with Modification
  6. FHIR#31890: overflowing their workflow in-basket impacting patient care (ehaas) Persuasive with Modification
  7. FHIR#31996: Purpose of Use <> Task.reasonCode (ehaas) Persuasive with Modification
  8. FHIR#32116: Need to express the relationship between this guide and others (lloyd) Persuasive with Modification
  9. FHIR#32840: Add guidance on matching patients (lloyd) Persuasive with Modification
  10. FHIR#32841: Provide guidance on finding organization and provider identifiers (lloyd) Persuasive with Modification
  11. FHIR#33139: Push mechanism to support 'Unsolicited Claims Attachments (ehaas) Persuasive with Modification

Note that : FHIR#31889 tracker link is broken and has been duplicated as FHIR#31890 to address this issue. The JIra team has been notified of this issue. However, at this time there is no way to remove it or the the status of "unresolved".

view this post on Zulip Eric Haas (Mar 28 2022 at 21:54):

:point_right: CDEX 1.0.0 has been published! http://hl7.org/fhir/us/davinci-cdex/ :point_left:

view this post on Zulip Eric Haas (Mar 28 2022 at 22:02):

:point_right: ....and... CDEX is going back to ballot in the May 2022 Ballot: :point_left:

All comments for this ballot are restricted to the following Draft content in the STU 1.0 version of CDex which includes handling of Attachments and Digital Signatures:

Topic Page Section (Sneek Peak!)
Attachments Background 2.6.2
Attachments Attachments 3.4
Attachments OperationDefinition: Submit Attachment Operation 7.5.1
Attachments CDex Submit Attachment Parameters Resource Example 7.29.1
Signatures Direct Query 3.2.6
Signatures Task Based Approach 3.2.6
Signatures Attachments 3.4.5
Signatures Signatures 4
Signatures Signed SearchSet Bundle Example 4.1
Signatures Signed Document Bundle Example 4.2
Signatures CDEX Document with Digital Signature Example 7.11.1
Signatures CDEX Document with Electronic Signature Example 7.12.1
Signatures Example of Task Request for Signed Data 7.22.1
Signatures Example of Completed Task Request for Signed Data 7.23.1
Signatures CDEX SearchSet Bundle with Digital Signature Example 7.28.1

Don't delay ballot sign ups end this Thursday - March 31.

Last updated: Apr 12 2022 at 19:14 UTC


An HL7 Website -