On this page:
  • Additional Features
  • 40.0 Da Vinci Clinical Data Exchange (CDex)
  • 40.1 Da Vinci Health Record Exchange (HRex)
    • 40.1    Da Vinci Health Record Exchange (HRex)   
    Table of Contents

    Da Vinci Clinical Data Exchange (CDex)

    40.0.1Da Vinci Clinical Data Exchange (CDex)
    Experimental

     

    This page describes Smile CDR's support of various features as defined in the Da Vinci Clinical Data Exchange (CDex) implementation guide.

    The current published version of this implementation guide can be found at the following URL:

    • https://hl7.org/fhir/us/davinci-cdex/index.html

    40.0.1.1Operation Submit Attachment

    Smile CDR supports the $submit-attachment operation as defined in version 2.0.0 - STU2.0 US of the CDex implementation guide.

    • https://hl7.org/fhir/us/davinci-cdex/STU2/OperationDefinition-submit-attachment.html

    The $submit-attachment operation saves the attached documents and links them to the related Task's output without modifying any existing claim or checking the existence of a claim or patient. It is expected that Payer's application to process the information saved in the Task to associate submitted information to a claim or prior authorization. The operation supports both solicited and unsolicited attachments. That is, if a Task whose Identifier matches the TrackingId parameter exists in the system, then that Task is updated. If such a Task does not exist, then it is created by the submit-attachment operation.

    40.0.1.1.1Differences from the earlier implementation

    40.0.1.1.1.1Smile CDR 2023.11.R01

    With Smile CDR 2023.11.R01, significant changes were made to the submit-attachment implementation that was initially introduced in Smile CDR 2022.11.R01 and was based on the CDex implementation guide version 1.1.0. The main differences of the CDR 2023.11.R01 implementation from the CDR 2023.08.R01 implementation are as follows:

    • Earlier implementation was updating the related claim with a link to the submitted attachment. With the current implementation, the links to the saved attachments are added to the Task output. Existence of a claim matching the submit-attachment request is not validated and no changes made to any claim as part of the operation.
    • Unsolicited attachments are now supported.
    • TrackingId input parameter type was a string, but now is an Identifier.
    • At least one of the OrganizationId or ProviderId fields must now be present. Previously they were both required.
    • Final parameter is now supported. The Task status is updated to Completed when Final is true, or absent. If Final exists and false, the Task status remains in IN PROGRESS.
    • Validation is added to require ServiceDate when AttachTo value is claim.
    • Validation is removed that checked a Patient matching the MemberId parameter exists in the system.

    40.0.1.1.1.2Smile CDR 2024.11.R01

    With Smile CDR 2024.11.R01, changes were made to the submit-attachment implementation in order to conform to CDex Task Attachment Request Profile 2.0.0. The main differences of the CDR 2024.11.R01 implementation from the CDR 2024.08.R01 implementation are as follows:

    • For solicited attachment flow, the validation on incoming requests against the existing Task now checks that:
      • OrganizationID field is matching to Task.contained.PractitionerRole.organization.identifier or ProviderID field is matching to Task.contained.PractitionerRole.practitioner.identifier.
      • MemberID field is matching to Task.contained.Patient.identifier.
    • For unsolicited attachment flow, when new Task is generated by the $submit-attachment operation, updated generation of Task resource:
      • Added contained Patient and PractitionerRole resources.
      • MemberId from the request is mapped to Task.contained.Patient.identifier.
      • OrganizationID from the request is mapped to Task.contained.PractitionerRole.organization.identifier.
      • ProviderID from the request is mapped to Task.contained.PractitionerRole.practitioner.identifier.
      • Task.for now has a reference to contained Patient resource.
      • Task.owner now has a reference to contained PractitionerRole resource.
      • Task.contained.Patient.name and Task.contained.Patient.birthDate are mapped from an existing Patient resource that was retrieved from the repository by MemberId parameter.
  • Additional Features
  • 40.0 Da Vinci Clinical Data Exchange (CDex)
  • 40.1 Da Vinci Health Record Exchange (HRex)
    • 40.1    Da Vinci Health Record Exchange (HRex)