Skip to main content

Common Errors

This page documents common errors and troubleshooting guidance for the US Core v1 Patient Access API.

Authentication Errors​

401 Unauthorized​

  • Cause: Missing or invalid authentication token
  • Solution: Ensure valid OAuth 2.0 token is included in Authorization header
  • Example: Missing Authorization header or empty Bearer token

403 Forbidden​

  • Cause: Valid token but insufficient permissions
  • Solution: Verify token has appropriate scopes for the requested resource

Resource Errors​

404 Not Found​

  • Cause: Requested resource does not exist or is not accessible
  • Solution: Verify resource ID and ensure resource exists in the system

400 Bad Request​

  • Cause: Invalid request parameters or malformed request
  • Solution: Check request syntax and parameter values

Server Errors​

500 Internal Server Error​

  • Cause: Unexpected server error
  • Solution: Contact Netsmart support for assistance

501 Not Implemented​

  • Cause: Requested operation is not supported
  • Solution: Verify the operation is supported for the target resource

Troubleshooting​

Common Issues​

  1. Token Expiration: Tokens have limited lifespans - refresh as needed
  2. Invalid Resource IDs: Ensure resource IDs are valid and accessible
  3. Unsupported Operations: Check resource documentation for supported operations
  4. Network Connectivity: Verify network access to API endpoints

Getting Help​

For additional support, contact Netsmart support with:

  • Request details (method, URL, headers)
  • Error response received
  • Expected behavior