<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/481edc8400a441ce8c6b5b68366004b2&quot; frameborder=&quot;0&quot; width=&quot;1048&quot; height=&quot;786&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>786</height><width>1048</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>786</thumbnail_height><thumbnail_width>1048</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/481edc8400a441ce8c6b5b68366004b2-57e6ebe733774c01.gif</thumbnail_url><duration>237.809</duration><title>EasyPA FHIR to HL7 Mapping in Minutes</title><description>This Loom walks through how EasyPA converts FHIR to HL7 v2 without hiring an HL7 expert. We use a stateless multi tenant AWS setup with sub second latency, and the hard part is mapping to each downstream system’s exact shape. I show how you paste one sample message that your system already accepts, then one click calls AWS Bedrock Nova Pro to draft a mapping template that preserves segment order and MSH encoding, tokenizes patient and order identifiers, keeps constants literal, and leaves to do tokens only when needed. You review and approve the template, then conversions run via API response or webhook delivery.</description></oembed>