## add-service-request

In the Direct API submission method, the RMS Source submits the referral payload directly to the RMS target via backend API mechanisms. The payload being sent matches that being sent in the sof-enh-add-service-request method, except that it uses the event code add-service-request.

Unlike the SoF / SoF-Enhanced submission methods, the RMS target does not present any UI to the user. It is up to the RMS source to generate all of the UI components. As a result, this method has limited functionality and cannot handle sophisticated eReferral business logic. It is best suited for simple referral workflows.

### Trigger Events

This event is triggered when:

* A user chooses to use their RMS Source system to submit a referral directly to the RMS Target.

### Summary of Supported Operations

This operation supports an HTTP POST of a MesssageHeader bundle from the RMS Source to the RMS Target's endpoint, with:

`"MessageHeader.eventCoding" : "add-service-request"`

The target endpoint is: `"MessageHeader.eventCoding" : "add-service-request"`

### Expected Behaviour

The RMS Source SHALL send a message with the relevant message event code, and all of the relevant resources.

The RMS Source SHALL send a message with `eventCoding.code=add-service-request`, which contains any eReferral information from the requesting system. The receiving system SHALL respond with a Bundle containing its full version of the referral resources. 

In the case of an error, the endpoint MAY optionally provide an OperationOutcome resource.

### Relevant Resource Profiles

Same as [sof-enh-add-service-request](https://simplifier.net/guide/eReferralOntario/MessagesSubmitReferral#eventsof-enh-add-service-request)

### Examples
* [sof-enh-add-service-request](https://simplifier.net/guide/eReferralOntario/exampleadd-service-request) - This is the reference payload, all RMS Targets should be able to process this payload successfully.