Overview

ABM Care Decision Support API
The goal for this first capability is to ingest data from Care Decision Support Service (CDSS), save this data in the ABM platform and make this data available to downstream application such as ABM CES.

The payload will contain the following:

• DecisionSupportNumber (string)
• OrganizationId (int)
• Score (int)
• ProcedureDescription (string)
• ProcedureCode (string)
• OrderDate (DateTime)
• indicationId (int)
• indicationDescription (string)

API request JSON:

{ "DecisionSupportNumber": "12345", "OrganizationId": 1111, "Score":8, "MemberId":"abc1234", "ProcedureCode": "74176", "ProcedureDescription": "CT, abdomend-pelvis, wo iv contrast", "OrderDate": "2025-01-15T14:30:00", "indicationId":123, "indicationDescription":" description of indication" }

Endpoint details

• Insert,update,get,delete Decision Support Record in dev01 enviornemnt use endpoint cds-dsrservice-dev01
• Insert,update,get,delete Decision Support Record in qa01 enviornemnt use endpoint cds-dsrservice-qa01
• Search Decision Support Record use in dev01 enviornment use endpoint cds-dsrservice-search-dev01
• Search Decision Support Record use in qa01 enviornment use endpoint cds-dsrservice-search-qa01
• To check the Decision Support API health check in dev01 environment use endpoint cds-dsrservice-healthcheck-dev01
• To check the Decision Support API health check in qa01 environment use endpoint cds-dsrservice-healthcheck-qa01

Dependency
Observability framework

Security
The ABM Care Decision Support API is secured using OAuth 2.0 facilitated by the Link API Gateway.

Retrieve your OAuth2 access token using your client id and secret. Then retrieve your access token. Refresh the token, token type, and expiration time. Your access token will expire after two hours.

Request:

curl -X POST https://sandbox-apigw.optum.com/apip/auth/sntl/v1/token

-H 'accept: application/json'

-H 'content-type: application/x-www-form-urlencoded'

-d 'grant_type=client_credentials&client_id=xxxxx&client_secret=[guid]'

Response: { "access_token":"abc123", "expires_in":7200, "refresh_expires_in":1800, "refresh_token":"def456", "token_type":"bearer", "not-before-policy":0, "session_state":"9c6eab3c-27ce-4fa2-29f1-ga020bd1z3c5", "scope":"email profile" }

Add the header to the request. Then take the access token from above. (Authorization: Bearer)

Support
Self-troubleshooting
When troubleshooting unexpected behavior from the API, validate the following:

• Are the input data and parameters following REST API and specification expectations?
• Is the input JSON in the correct format?
• Are you providing all the required input parameters?
• Is the REST client you are using configured correctly with security credentials?
• For functional questions about this API, use the "Want more information?" form below.

Technical support
For technical support, provide as much of the following information as possible:

• A sample request to demonstrate the behavior you are expecting
• A corresponding sample response to demonstrate the actual output from the API
• Any environmental factors you deem important (e.g., how intermittent is the problem, what browser is impacted, etc.)
• Providing this information will help the technical team triage and respond more quickly.

Please gather and send details to ABM engineering support at[email protected]

Change control / maintenance
ABM follows a compliance process where all features going into a release are linked to the release for auditing purposes. A change ticket is created and approved by appropriate individuals before releasing into production. The advance notice is sent to consumers of this API if there is any change with an upcoming release/deployment.