2015May core #890 - Need to be able to "lock" records

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Considered for Future Use
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • US Realm Task Force
    • REST (http)
    • 2.1.0 RESTful API
    • Hide

      resolution: Implementers have a framework for implementating this now, using tags and meta operations, or using a RBAC engine. We encourage implementers to experiment with the implications of this, including at the October connectathon in the EHR-FM stream, and then we will consider standardising this in a future version after experimentation.

      Show
      resolution: Implementers have a framework for implementating this now, using tags and meta operations, or using a RBAC engine. We encourage implementers to experiment with the implications of this, including at the October connectathon in the EHR-FM stream, and then we will consider standardising this in a future version after experimentation.
    • Grahame Grieve / John Moerhke: 7-0-0
    • Enhancement
    • Non-substantive

      Proposed Wording: "lock: this operation updates the "read-only" metadata for the resource. This allows for records to be marked as "read only" to avoid any subsequent updates.

      Comment:

      Medical Records experts at the VA have indicated that in some cases medical records need to "locked" - protected for changes - to avoid revisions in certain cases. There are other use cases when resources may need to be "read-only".

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: