FHIR Questionnaire API for Health Cloud

Limitations in POST Questionnaire Response and Discovery Framework

The current implementation of the POST operation for Questionnaire Responses consuming the Discovery Framework has these limitations:

Unsupported Data Types

These data types are not currently supported in QuestionnaireResponse resource:

• valueCoding
• valueQuantity
• valueReference

Lack of Association with OmniProcess

The Discovery Framework ignores Questionnaire Responses that are not linked to an OmniProcess. Although such submissions return a 201 Created status, the corresponding data is not created or persisted in the org. No validation error or warning is surfaced.

Missing Type Validation

The Discovery Framework does not currently validate whether the data types of questions in the Questionnaire match the types of their corresponding answers in the QuestionnaireResponse. This can result in inconsistencies or unintended behavior if mismatched types are submitted.

Application-Level Limitaion

Supported Namespace for OmniScripts

The application currently supports OmniScripts only under the omnistudio namespace. Other namespaces are not supported by salesforce managed application at this time.

If this application is managed by customer and If you're using a different namespace, or working in an org that does not require the OmniStudio managed package, you must configure the sf.IPBasepath property. This can be set either in the application's properties section or as an additional property during deployment via the MuleSoft Direct deployment screen.

Example value: /services/apexrest/omnistudio/v1/integrationprocedure
This property defines the base path for calling Integration Procedures and must reflect the correct namespace or routing configuration for your Salesforce org.