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

Update documentation to document what fields a client can and cannot update

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Subscription
    • Hide

      Based on the redesign of subscription, there are no longer any elements that can't freely be updated by the client (same restrictions as any other resource - e.g. messing around with .id or .meta).

      Show
      Based on the redesign of subscription, there are no longer any elements that can't freely be updated by the client (same restrictions as any other resource - e.g. messing around with .id or .meta).
    • Gino Canessa/Christiaan Knaap: 13-0-0

    Description

      In Subscription, there are some fields a client app can't update. Status already calls out some limitations, but there are other fields that need to likely call limitations out.

      For example, a client should never update the error or eventCount.

      Attachments

        Activity

          People

            ginocanessa Gino Canessa
            jenni_syed Jenni Syed (Inactive)
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: