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

Determining Server Note type use of $expand

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Core (FHIR)
    • 6.0.0-ballot [deprecated]
    • Cross-Group Projects
    • STU
    • Clinical Notes
    • 3.3.3
    • Hide

      1) RE: When support of $expand is indicated in the CapabilityStatement does that mean it can be used for this purpose only or also for other ValueSets?

      The purpose of the FHIR Value Set Expansion ($expand) operation defined in the FHIR R4 specification is for a client to determine two things about a server:

      The note and report types a server supports
      The note types and read/write formats a server supports.

      will clarify the documentation in the CapabilityStatement:

      If a server supports DocumentReference for creating, using, and sharing clinical notes, it SHOULD also support the `context` and `contextdirection` parameters of the $expand operation to enable clients to determine the supported note and report types, as well as the supported read/write formats for notes on the server.

      2)  RE The $expand operation is used to determine the note types and read/write formats supported by a server.I think this is not the way this operation is intended to work...This is also different from the behavior of the server. If the server wants to publish its behavior, it should do so using a server specific profile of the UScore profile and the $expand operation should use the canonical of this structure definition in the context field.

      > We agree this is an error.  The examples will be updated to include the canonical URLs for the profiles.

      Show
      1) RE: When support of $expand is indicated in the CapabilityStatement does that mean it can be used for this purpose only or also for other ValueSets? The purpose of the FHIR Value Set Expansion ($expand) operation defined in the FHIR R4 specification is for a client to determine two things about a server: The note and report types a server supports The note types and read/write formats a server supports. will clarify the documentation in the CapabilityStatement: If a server supports DocumentReference for creating, using, and sharing clinical notes, it SHOULD also support the `context` and `contextdirection` parameters of the $expand operation to enable clients to determine the supported note and report types, as well as the supported read/write formats for notes on the server. 2)  RE The $expand operation is used to determine the note types and read/write formats supported by a server . I think this is not the way this operation is intended to work...This is also different from the behavior of the server. If the server wants to publish its behavior, it should do so using a server specific profile of the UScore profile and the $expand operation should use the canonical of this structure definition in the context field. > We agree this is an error.  The examples will be updated to include the canonical URLs for the profiles.
    • Eric Haas/Jason Vogt: 12-0-0
    • Correction
    • Non-substantive

    Description

      In section 3,3,3 it is defined that a client can determine the note and report types supported by a server.

      This is specified through the ValueSet.$expand operation.

      When support of $expand is indicated in the CapabilityStatement does that mean it can be used for this purpose only or also for other ValueSets?

       

      The $expand operation is used to determine the note types and read/write formats supported by a server. I think this is not the way this operation is intended to work.

      So far as I understand the $expand use of the context fiedThe DiagnosticReport.category will provide the list of the ValueSet defined in the StructureDefinition referred to in the context field. In the case DiagnosticReport.category is entered, this will be StructureDefinition of the  base FHIR resource. When the categories of US core are required, this operation should point to the USCore profile.

      If this is the case, this means this operation cannot be used to determine the categories and contextDirection of the server. Only the information that is coded in the StructureDefinition.

       

      This is also different from the behavior of the server. If the server wants to publish its behavior, it should do so using a server specific profile of the UScore profile and the $expand operation should use the cannonical of this structure definition in the context field.

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            bvdh Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: