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

This change request seeks to allow for more granularity for expressing the interaction codes associated with profiles in a capability statement.

    XMLWordPrintableJSON

Details

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

      We will add a tracker item to the CapabilityStatement2 IG to include this ability to identify different profiles for different RESTful interactions for a given resource

      Show
      We will add a tracker item to the CapabilityStatement2 IG to include this ability to identify different profiles for different RESTful interactions for a given resource
    • Corey Spears/Richard Ettema: 12-0-0
    • Enhancement
    • Non-substantive

    Description

      Summary: This change request seeks to allow for more granularity for expressing the interaction codes associated with profiles in a capability statement. Currently, you can only express the supported profiles and the interaction codes as a group. A more precise way is to add the capability to express individual interaction codes for a given profile.

      For each exchanged resource referenced in the capability statement, the current method allows to assign a list of interactions (Read, Write and other codes from Interaction Codes value set). However, once selected, the interaction codes are applied to all the supported profiles for a given resource type.

      Table 1 illustrates how the interaction codes are assigned to a particular resource type. In this case, the Read and Search operations are applied to all the supported profiles.

      Resource Type Supported profiles R S U C
      Patient Patient_obligation_1
      Patient _obligation_2
      Patient_obligation_3
       
      Y Y   Y

       Table 1: Existing capability statement for expressing Profile and Operations

      The change request aims to provide the possibility to render specific operations to individual profiles. An example of the expected representation is as follow:

      Resource Type Supported Profiles R S U C
      Patient Patient_obligation_1 Y      
      Patient_obligation_2 Y Y    
      Patient_obligation_3
       
      Y     Y

       Table 2: Requested capability statement for expressing Profile and Operations

      Table 2 above shows how certain interactions are associated to a given profile. For instance, the Patient_Obligation_1 supports only the Read interaction. Patient_Obligation_2 supports both the Read and Search interaction; and Patient_Obligation_3 supports the Read and Create interaction. This is in comparison to Table 1, where all the three profiles are shown to support the interactions Read, Search, and Create.

      Attachments

        Activity

          People

            Unassigned Unassigned
            rsnelick Robert Snelick
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: