Add RESTful for locking and unlocking patient records

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Normative
    • REST (http)
    • Hide

      We think we could do this using tags - if additional support beyond tags, this is a function that could be added to a future version of the specification. Prior to introducing such a concept, we would like to see it being used in a connectathon.

      After connectathon, a new task can be submitted requesting specific changes based on the learnings from the connectathon.

      Show
      We think we could do this using tags - if additional support beyond tags, this is a function that could be added to a future version of the specification. Prior to introducing such a concept, we would like to see it being used in a connectathon. After connectathon, a new task can be submitted requesting specific changes based on the learnings from the connectathon.
    • Grahame Grieve/Ewout Kramer: 10-0-0
    • Enhancement

      VA Medical Records Management requires the capability to lock records for patient under specific situations (e.g. litiagation). This means that all the resources associated with the patient must be locked to prevent updates for the duration.

      http://hl7.org/fhir/2018May/http.html#rejecting-updates

      Add an additional reason to "3.1.0.10.1 Rejecting Updates ":

      – HTTP status 405 "Method not allowed" because the resource is "locked"

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            greg_staudenmaier, Ioana Singureanu
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: