FHIR Bundle with Claim (request) or ClaimResponse (response) - max 50KB
0 characters (max 51,200 for 50KB limit)
EvaluationNew request converter under controlled live evaluation. Use synthetic / de-identified data only.
Both methods use the same Redix conversion engine (FHIR → RMap → X12 278, in one step). Choose how your FHIR reaches the Redix contract.
During evaluation, conversion runs the reviewed demo samples; other uploads can be inspected with Review FHIR adaptation but are not converted until validation completeness is finalized.
This runs on the Redix AnyToAny Engine — trusted by state agencies and health plans since 1996. Tell us about your project and we'll follow up within one business day.
Thank you! We'll be in touch within one business day.
About CMS Prior Authorization (Da Vinci PAS)
Explore the HL7 Da Vinci PAS Implementation Guide with synthetic data. Convert X12 278 Request and Response transactions to FHIR R4. A legacy developer path (FHIR → RMap two-step) is also available. The reverse FHIR to X12 278 direction is in development.
The ePA Ecosystem: CRD + DTR + PAS
CRD, DTR and PAS are three HL7 Da Vinci implementation guides designed to work together for electronic prior authorization:
Coverage Requirements Discovery (CRD) — Embedded in the EHR workflow, CRD queries the payer in real-time at the point of order entry to determine whether prior authorization is required and what documentation is needed.
Documentation Templates and Rules (DTR) — When CRD indicates documentation is required, DTR launches a SMART-on-FHIR app that presents payer-specific questionnaires, auto-populating answers from the patient record to reduce manual data entry.
Prior Authorization Support (PAS) — Once documentation is complete, PAS submits the prior authorization request electronically via FHIR, replacing fax and portal-based workflows with real-time or near-real-time decisions.
Together, these three guides are designed to reduce manual prior authorization work by bringing requirement checks, documentation and submission into the provider’s workflow. Explore the Prior Authorization Workflow and API Sandbox →