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

Basing the implementation guide on Communication increases implementation costs

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • Patient Corrections (FHIR)
    • 1.0.0-ballot
    • Patient Empowerment
    • STU
    • Actors and Use Cases
    • Hide

      Work on publishing the guide as is.
      Add a 'Known Issues' section:

      • Some implementers believe that a more streamlined approach without communication should be considered for the next release.

      Make this an explicit request for comments.

      Also note for the committee to track this feedback.

      Show
      Work on publishing the guide as is. Add a 'Known Issues' section: Some implementers believe that a more streamlined approach without communication should be considered for the next release. Make this an explicit request for comments. Also note for the committee to track this feedback.
    • Grahame Grieve / Vassil Peytchev : 11-0-3
    • Clarification
    • Non-substantive

    Description

      The use cases and the scope of the implementation guide are well defined, and will benefit form a straight-forward implementation guide. All the use cases can be satisfied with only a Task resource that maintains the state of the request, contains the conversation in the Task.note element, and provides the capability to attach inputs for and outputs of the correction process.

      With such an approach, later iterations of the implementation guide can gradually add more sophistication to the patient correction process, including the use of Communication resources within the context of general patient-provider communications.

      The current implementation guide requires the use of communications without any regard for general patient-provider communications, and that will prevent implementations, as implementers would be reluctant to start managing Communication resources for a very specific (from the patient-provider communications viewpoint) use case without any guidance how to implement it in a general fashion.

      Attachments

        Activity

          People

            david.pyke David Pyke
            vassil Vassil Peytchev
            Vassil Peytchev
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: