Notice of Admission

An admission notification informs the payer that an enrollee has been admitted to a facility (acute cafe hospital, skilled nursing facility, acute rehabilitation facility). These facilities are responsible for admission notification for inpatient services even if the coverage approval is on file. Notification of each inpatient admission must be received very quickly (typically within 24 to 72 hours after admission (see Advance and Admission Notification requirements)). The Notice of Admission (NoA) API:

• Enables more payers to support automation through 278N or portal-based notification
• Provides real-time status updates/alerts that assist users to quickly address issues so you do not have to rely on reports and/or HL7 response messages for information
• Creates a seamless experience and holistic view of Authorization workflow

The following endpoints are supported:

• Get authentication/bearer token

Generates an authentication token using your client_id and client_secret. For information, see Onboarding with Prior Authorization API.

https://sandbox-apigw.optum.com/apip/auth/v2/token

• Check API health

Our /healthcheck endpoint verifies that the operating status of the requested API is optimal. It is a ping for the API entry points to ensure the entry points are accessible and it is the first thing you can do if the API request is not working.

https://sandbox-apigw.optum.com/rcm/prior-authorization/v1/healthcheck

• A standard X12 EDI 278 transaction request

Formats the 278 transaction in JSON format for an noa request. Accepts JSON with a single string 'x12' property that has a 278 EDI string and produces a JSON response with a single 'x12' property that has a 215 EDI string.

https://sandbox-apigw.optum.com/rcm/prior-authorization/v1/noa/x12

• A JSON noa request to the payer or clearinghouse

Accepts an EDI JSON object model request and produces a JSON object model response.

https://sandbox-apigw.optum.com/rcm/prior-authorization/v1/noa

• JSON-to-EDI API Contents