generated: '2026-08-14'
method: searched
source: >-
  https://rhapsody.health/solutions/rhapsody/ ,
  https://rhapsody.health/solutions/rhapsody-axon/ ,
  https://rhapsody.health/solutions/guardian/ ,
  https://rhapsody.health/solutions/agent-ready-interoperability/ ,
  https://rhapsody.health/llms.txt ,
  https://rhapsody.health/trust-center/
note: >-
  Conformance asserted from Rhapsody's public solution and trust pages. Rhapsody
  is a healthcare interoperability platform whose defining value is standards
  breadth: it moves data across the healthcare exchange standards below from a
  single deployment. Machine-readable API specs are gated behind
  docs.rhapsody.health (AWS Cognito SSO), so operation-level RFC conformance
  (e.g. RFC 9457) cannot be verified from a public OpenAPI and is left null.
standards:
- id: hl7-v2
  conforms: true
  evidence: Core supported message standard across Rhapsody and Corepoint engines
- id: fhir
  conforms: true
  evidence: FHIR named as a first-class supported standard; FHIR APIs documented in the developer portal
- id: cda
  conforms: true
  evidence: Clinical Document Architecture listed among supported standards
- id: x12-edi
  conforms: true
  evidence: X12/EDI listed among supported standards
- id: dicom
  conforms: true
  evidence: DICOM imaging listed among supported standards (Image Director)
- id: ncpdp
  conforms: null
  evidence: not confirmed on public pages
- id: mcp
  conforms: true
  evidence: >-
    Model Context Protocol named as a supported protocol on the agent-ready
    interoperability page alongside FHIR/HL7/REST/CDA/X12/SQL/DICOM/AMQP, and
    surfaced through Rhapsody Axon. Platform capability only — Rhapsody publishes
    no reachable MCP endpoint or installable server (see mcp/rhapsody-mcp.yml).
- id: amqp
  conforms: true
  evidence: AMQP listed among the protocols supported from a single platform
- id: smart-on-fhir
  conforms: true
  evidence: >-
    Rhapsody Guardian product page states "Guardian supports OAuth 2.0, SMART on
    FHIR, and Basic Auth" for the healthcare APIs a customer exposes through the gateway
- id: oauth2
  conforms: true
  evidence: >-
    Developer documentation portal fronted by AWS Cognito OAuth2 (authorization
    code + PKCE); Rhapsody Guardian additionally offers OAuth 2.0 for
    customer-published APIs
- id: openid-connect
  conforms: true
  evidence: Cognito hosted UI issues openid/email/profile scopes (OIDC)
- id: hipaa
  conforms: true
  evidence: Supported via Business Associate Agreements (trust center)
- id: gdpr
  conforms: true
  evidence: Supported via DPA with Standard Contractual Clauses (trust center)
- id: onc-cures-act
  conforms: true
  evidence: Platform designed to support ONC/CMS interoperability requirements
- id: rfc9457-problem-details
  conforms: null
  evidence: API spec gated; cannot verify error envelope from a public OpenAPI