2021-04-21 CDex Meeting

• CDex Implementation Guide: http://build.fhir.org/ig/HL7/davinci-ecdx/ 

• Source Code in GitHub:

  • CDex Communication Response App

  • CDex Communication Request App

• HRex Sept Ballot IG: http://hl7.org/fhir/us/davinci-hrex/2020Sep/index.htm
• Note: 34 affirmatives of 35 approval threshold.

Block Vote 6 for HRex Submitted. 

1 ticket left - Vasil will try to come next week. 

IG changes to be applied in the next month. 

FHIR-29683 - Getting issue details... STATUS  - reviewed and approved disposition. 

FHIR-30446 - Getting issue details... STATUS  - Durwin Day, we reviewed and updated the resolution description, please review and/or come to a future meeting or let us know your approval as this was marked as in person review.  

FHIR-30820 - Getting issue details... STATUS  - Reviewed and discussed.  See the proposed disposition.   

VC note from call on 4/21 - Eric and Celine to review and pick up on FHIR#30819 on our next call in two weeks (5/5)

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? answered

AMA Comments:

1. FHIR#30494: Delete use of word complete as it is too extreme. (celine_lefebvre) Persuasive - reviewed and agreed quickly 4/14 
2. FHIR#30813: Remove word complete. (celine_lefebvre) Persuasive-- reviewed and agreed quickly 4/14 
3. FHIR#30814: Question about use of referred-to. (celine_lefebvre) Persuasive with Modification- reviewed and agreed quickly 4/14 
4. FHIR#30817: Rephrase. (celine_lefebvre) Persuasive- reviewed and agreed quickly 4/14 
5. FHIR#30818: When and how are subscriptions terminated? (celine_lefebvre) Considered - Question answered- reviewed and agreed quickly 4/14  
6. FHIR#30819: Unclear how this imposes excessive P&S risks? Please explain. (celine_lefebvre) Persuasive with Modification - reviewed 4/14 - pulled from Block 3 to discuss further
7. FHIR#30820  Unresolved When a task is complete what triggers the termination of a payer's ability to fetch data? - reviewed 4/14,4/21
8. FHIR#30821  Unresolved When and how do data servers terminate a client's set of requests?reviewed 4/21
9. FHIR#30822  Unresolved What method is used to determine the end of a client's access to a data server?reviewed 4/21
10. 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. reviewed 4/21
11. FHIR-29683 Interop Framework for Payer2Payer and Internal Systems - unable to contact commenter for clarification reviewed 4/21

For Next Time

1. FHIR#30819: Unclear how this imposes excessive P&S risks? Please explain. (celine_lefebvre) Persuasive with Modification - reviewed 4/14 - pulled from Block 3 to discuss further
2. FHIR-30497  Change should to SHALL as required by minimum necessary. Not Persuasive (celine_lefebvre)
3. FHIR-30826 Better standardize Task.reasonReference by formalizing (but not limiting) the current scenarios (Isaac is planning to be present to discuss)

Review Kathleen wording:

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