Skip to main content

Supported CareRecords

Overview​

The General Purpose R4 FHIR API is supported across multiple Netsmart CareRecord systems. Each CareRecord provides FHIR R4 capabilities through a standardized API interface, enabling healthcare organizations to access and exchange clinical data using industry-standard protocols.

Before implementing with any CareRecord, always retrieve the CapabilityStatement to validate current API capabilities:

GET {base-url}/metadata

Supported CareRecord Systems​

Netsmart has multiple CareRecords that support the General Purpose R4 API:

myAvatar​

Comprehensive behavioral health EHR supporting the full spectrum of care delivery.

myEvolv​

Integrated platform for behavioral health and human services organizations.

myUnity​

Home care and hospice management solution with clinical documentation capabilities.

TheraOffice​

Practice management and EHR solution for rehabilitation therapy providers.

GEHRIMED​

Post-acute care EHR solution for skilled nursing and long-term care facilities.

Implementation Considerations​

CapabilityStatement Validation​

Each CareRecord may support different:

  • Resource types and operations
  • Search parameters
  • Supported profiles
  • Authentication requirements

Always validate capabilities before implementation by retrieving the CapabilityStatement from the target environment.

Environment-Specific Differences​

Capabilities may vary between:

  • Production and preview environments
  • Different CareRecord versions
  • Tenant-specific configurations

Integration Patterns​

Common Workflows​

  1. Capability Discovery

    • Retrieve CapabilityStatement
    • Validate supported resources
    • Check authentication requirements

  2. Resource Access

    • Use supported search parameters
    • Follow supported profiles
    • Handle CareRecord-specific extensions

  3. Data Exchange

    • Respect supported formats
    • Use appropriate include/revinclude parameters
    • Handle pagination consistently

Error Handling​

For comprehensive error handling information, see Common Errors.

Support​

For technical support with CareRecord integration: