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

Clarify scope of operations

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Considered - Question answered
    • Icon: Highest Highest
    • SMART on FHIR (FHIR)
    • 2.0.0
    • FHIR Infrastructure
    • (NA)
    • Hide

      We don't currently have support for custom operations in our scope language; we could not identify a common core of functionality to standardize given challenges of needing to lock down custom operations based on invocation context and fixed parameters. In the meantime we encourage experimentation and will consider suggestions on how to standardize this functionality by enhancing the scope language in a future release.

      Show
      We don't currently have support for custom operations in our scope language; we could not identify a common core of functionality to standardize given challenges of needing to lock down custom operations based on invocation context and fixed parameters. In the meantime we encourage experimentation and will consider suggestions on how to standardize this functionality by enhancing the scope language in a future release.

    Description

      What scope does a defined Operation, e.g. Patient/$match, fall under? Is this dependent on the operation (e.g. $match is similar to a search, which Composition/$document is similar to a read)?

      Existing Wording:

      • c for create...
      • r for read...
      • u for update...
      • d for delete...
      • s for search…

      (Comment 19 - imported by: Ron G. Parker)

      Attachments

        Activity

          People

            Unassigned Unassigned
            Rongparker Ron G. Parker
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: