Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-44867

Clarify CDex interactions in Figure 3.1 - Request For Additional Information Workflow

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Da Vinci PAS (FHIR)
    • 2.0.1
    • Financial Mgmt
    • Request for Additional Information
    • Hide

      Include the more generic diagram (first one in the description) to show how the $submit-attachment call is used.

      Provide text that indicates that although CDex defines a set of operations, it may be implemented in a separate module.  The Task is used to represent the information that is needed to make the CDex calls.  If the CDex calls are not in a separate module, then the Task may just be conceptual and not actually created.

      We also want to indicate that, in PAS, the Task is created by the Provider but that the remaining workflow remains the same.

      Show
      Include the more generic diagram (first one in the description) to show how the $submit-attachment call is used. Provide text that indicates that although CDex defines a set of operations, it may be implemented in a separate module.  The Task is used to represent the information that is needed to make the CDex calls.  If the CDex calls are not in a separate module, then the Task may just be conceptual and not actually created. We also want to indicate that, in PAS, the Task is created by the Provider but that the remaining workflow remains the same.
    • Clarification
    • Non-substantive

    Description

      Clarify in the diagram that launching DTR using Task and submitting attachments using $submit-attachment are FHIR transactions defined in CDex rather a distinct actor as implied by the diagram. Whether they are performed within a system or passed to the separate 3rd party applications is an implementation specific architectural detail not covered in CDex.  

      Also the same holds true for DTR.  I propose show 2 sets of sequence diagrams to illustrate this.  The first is a high level diagram that abstract the the interaction to black box function for getting documents as additional information.  No Task is needed in this case.

       

      The second diagram is a simplified diagram that aligns more closely with CDex and DTR  and shows when PAS Response Bundle is asking for a Questionnaire to be filled out and the options if the DTR is a provider system function or a separate SMART App.

      Attachments

        Activity

          People

            Unassigned Unassigned
            ehaas Eric Haas
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: