About

Title: Senior FHIR Engineer (Azure) – In-Memory FHIR Converter & Sender Overview I’m an emergency physician and founder of a HIPAA-oriented documentation system running entirely on my own Microsoft Azure subscription. The system already: • Takes a physician’s dictation • Applies a large clinical rule set via an AI pipeline • Returns a completed ED-style note into a secure browser text box From there, the doctor can already copy/paste the full note into the EMR or generate discharge instructions. I do not store PHI or act as an EMR. Everything is processed in memory, rendered to the browser, and cleared when the session ends. I am not asking you to touch the AI pipeline — that part is done and working. ________________________________________ What I need Add a third button: “Send to EMR” with two backend pieces in Azure: 1. FHIR Converter (Azure Function) o Input: the completed note text (highly consistent, ED note with uniform ALL-CAPS headers: e.g., HISTORY, PHYSICAL EXAMINATION, LABS AND STUDIES, EKG, MEDICAL DECISION MAKING, IMPRESSION, DISPOSITION, etc.). o Task: parse by these headers and map sections into a valid FHIR Bundle (typical resources such as Patient, Encounter, Condition, Observation, Procedure, DocumentReference – final details to be agreed with you). o Must be stateless, in-memory only (no PHI written to disk, DB, queues, or logs). 2. FHIR Sender (Azure) o Input: the FHIR Bundle from the converter. o Task: POST/PUT the bundle to a configurable hospital FHIR endpoint (Epic, Cerner, Meditech, etc.) over HTTPS using standard FHIR REST. o Auth must be configurable per client (OAuth2, bearer token, etc.), with endpoint and credentials stored securely (e.g., Key Vault) and adjustable without code changes. Once this is built, no further coding should be needed per hospital: new hospital = set endpoint + credentials in config, and the “Send to EMR” button works. All of this must run inside my existing Azure subscription. No third-party FHIR gateways or external services. ________________________________________ What I’m looking for Only senior, hands-on people who have actually shipped this kind of thing: • Strong FHIR experience (ideally with Epic / Cerner / Meditech or other EHRs). • Solid Azure background (Azure Functions, API Management or similar, Key Vault, secure outbound REST). • Comfortable designing a clean, minimal FHIR Bundle for ED notes and handling errors/retries without persisting PHI. ________________________________________ Please include in your reply 1. Brief summary of your FHIR/EHR work (which EHRs, what you built). 2. Your Azure experience relevant to Functions / APIs / Key Vault. 3. One or two examples of FHIR integrations you’ve done. 4. A rough hour estimate to: o Build the converter o Build the sender o Wire to the “Send to EMR” button and do basic testing 5. Your hourly rate and earliest availability.