Da Vinci Clinical Data Exchange (CDex)
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:
Smile CDR supports the $submit-attachment operation as defined in version 2.0.0 - STU2.0 US of the CDex implementation guide.
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.
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:
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:
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.$submit-attachment operation, updated generation of Task resource:
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.