Light up X12, but don’t let it burn.
summary
CMS requires payer FHIR APIs for prior authorization while HIPAA still mandates X12, so organizations must implement robust X12→FHIR mapping that handles envelopes, loops, implicit two‑char code systems and attachments. Expect to build an X12 parser/generator, a normalization layer for code systems, and either a DSL mapping engine for inheritance and site overrides or reusable scripts. Redox reports handling 38 billion messages in scope and running live mappings with frequent, small corrections as edge cases emerge.
AI-written summary · about
chapters (9)
- 0:00Introductions
- 1:28Understanding X12
- 5:33Why translate to FHIR?
- 6:57X12 structure and mapping
- 14:59Modeling FHIR claims
- 18:56Tools for translation
- 27:40Summary and takeaways
- 30:23Developer experience
- 33:27Q&A session
