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

Define profiles on Parameters to add constraints for OperationDefinition

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Quality Measures (FHIR)
    • 4.0.0-ballot [deprecated]
    • Clinical Quality Information
    • Measure Packaging [deprecated]
    • Measure Repository Service
    • 10.2.1.5.3
    • Hide

      Agree with recommendation but will defer adding a profile of Parameter to a future publication based on priorities of other additional features that need to be added for the STU 4 publication cycle.

      Consider the profile of a Parameter resource for future versions.

      For this version, add the following to http://hl7.org/fhir/us/cqfmeasures/2023Jan/measure-repository-service.html#package

      For the $package operation, when combinations of "in" parameters specify more than one measure to package, the operation SHOULD return an OperationOutcome error. These combinations include the following:

      The "id" input (in) parameter and Measure/

      {id}

      /$package have different values for the id,_

      More than one of "id", "url" or "identifier" input parameters are specified

      If Measure/{id}/$package is used to specify the measure, then url and identifier "in" parameters must not be present in the Parameters resource or as a URL parameter

      Implementations are not required to support mixing of "in" parameters in the URL and inside a POSTed Parameters resource; it is acceptable to return an OperationOutcome if mixing is not supported. Implementation MAY support such mixing of input parameters.

      These constraints are applicable even if if some or all of the in parameters are specified in the URL

       

      Show
      Agree with recommendation but will defer adding a profile of Parameter to a future publication based on priorities of other additional features that need to be added for the STU 4 publication cycle. Consider the profile of a Parameter resource for future versions. For this version, add the following to  http://hl7.org/fhir/us/cqfmeasures/2023Jan/measure-repository-service.html#package For the $package operation, when combinations of "in" parameters specify more than one measure to package, the operation SHOULD return an OperationOutcome error. These combinations include the following: The "id" input (in) parameter and Measure/ {id} /$package have different values for the id,_ More than one of "id", "url" or "identifier" input parameters are specified If Measure/{id} /$package is used to specify the measure, then url and identifier "in" parameters must not be present in the Parameters resource or as a URL parameter Implementations are not required to support mixing of "in" parameters in the URL and inside a POSTed Parameters resource; it is acceptable to return an OperationOutcome if mixing is not supported. Implementation MAY support such mixing of input parameters. These constraints are applicable even if if some or all of the in parameters are specified in the URL  
    • Juliet Rubini/Anne Smith: 22-0-0
    • Clarification
    • Non-substantive

    Description

      See https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/Validation.20of.20messages.20and.20operations/near/317257602 for background

      Add a profile of the Parameters resource which can be referenced from OperationDefinition.inputProfile for the Measure $package operation. Include invariants in the profile that exactly one Measure can be specified. Conditions which specify more than one measure to package shall return an OperationOutcome error. These conditions in include the following:

      "id" in parameter and Measure/{id}/$package have different values for the id,

      More than one of "id", "url" or "identifier" input parameters are specified

      If Measure/{id}/$package is used to specify the measure, then url and identifier "in" parameters must not be present in the Parameters resource or as a URL parameter

      Implementations are not required to support mixing of in parameters in the URL and inside a POSTed Parameters resource; it is acceptable to return an OperationOutcome if mixing is not supported. Implementation MAY support such mixing of input parameters.

      The Parameters profile constraints are applicable even if if some or all of the in parameters are specified in the URL

      Also add text in  http://hl7.org/fhir/us/cqfmeasures/2023Jan/measure-repository-service.html#package to explain how the Parameters profile is applied to the operation.

       

      Attachments

        Activity

          People

            abdullah.rafiqi Abdullah Rafiqi
            mitrep9g Paul Denning
            Paul Denning
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: