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

Tooling issues around multi-level Operations

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • FHIR Infrastructure
    • (NA)
    • Hide

      Will add OperationDefinition.parameter.scope 0..* code with valueset consisting of system/type/instance and a definition that says "if present, indicates that the parameter only applies when the operation is being invoked at the specified level".  

      Add a meaning if missing "The allowed use of the parameter in a given level is presumed to be allowed unless the textual description of the operation expresses otherwise."

      Will go through existing operations and set the code as appropriate once this is supported by the publication tooling.

      Show
      Will add OperationDefinition.parameter.scope 0..* code with valueset consisting of system/type/instance and a definition that says "if present, indicates that the parameter only applies when the operation is being invoked at the specified level".   Add a meaning if missing "The allowed use of the parameter in a given level is presumed to be allowed unless the textual description of the operation expresses otherwise." Will go through existing operations and set the code as appropriate once this is supported by the publication tooling.
    • Josh Mandel/Gino Canessa: 26-0-2
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      When defining an operation at both the Resource and Instance levels, it is neither possible to separate the definitions, nor it is possible to flag parameters as specific to one level.

       

      It should either be possible to separate the definitions so that different input parameters can be specified, or parameters should be able to be flagged as used in only one or the other (e.g., Use: in-resource/in-instance).

       

      For example, several operations are defined at both levels with the Resource operation taking in a list of ids, which is not valid at the instance level.  Right now, the parameter is defined on the operation at both, with a text note explaining that it isn't valid at instance level.

      Attachments

        Activity

          People

            GrahameGrieve Grahame Grieve
            ginocanessa Gino Canessa
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: