Skip to main content

Process Message Operation

OPERATION: POST [base]/$process-message

The Process Message operation enables the submission of FHIR messages to various Netsmart solutions.

The Messaging using FHIR Resources article to learn more about FHIR Messaging.

Workflow

This API uses the synchronous message exchange pattern for each message.

Authorization

This operation will require the application obtain authorization using one of the following custom scopes based on SMART.

  • v1: [patient|user|system]/Messaging.[write|*]
  • v2: To be determined. (future)

Parameters

UseNameCardinalityTypeDocumentation
INcontent1..1BundleThe request message to process.
INasync0..1booleanIf true the message is process using asynchronous messaging pattern.
None of our supported message types currently support the asynchronous message pattern.
INcontent0..1urlA URL to submit response messages to, if asynchronous messaging is being used, and if the MessageHeader.source.endpoint is not the appropriate place to submit responses.
This is not currently supported by any of our existing message types.
OUTreturn0..1BundleThe response message returned directly as a resource.

Supported Message Events

Netsmart-defined Message Events

All Netsmart-defined messaging events use the following system: http://ntst.com/fhir/message-events.

NameTypeDescriptionSupported CareRecord(s)
and/or other Solutions
Submit Service Requestsubmit-service-requestEnables the submission of referrals ("Service Requests") to Referral Manager.Referral Manager
Update Service Requestupdate-service-requestEnables the update of previously referrals ("Service Requests") to Referral Manager.Referral Manager

Examples

curl -X POST 'https://fhir.netsmartcloud.com/v4/$process-message' \
-H "Authorization: {Bearer Token}" \
-H "Accept: application/fhir+json" \
-H "Content-Type: application/x-form-urlencoded" \
-d @payload.json