Hospital EHR integration
AGIMAN captures the encounter in the room, drafts the chart note in the clinician's style, and suggests ICD and CPT codes. After the clinician reviews and signs, the approved note and codes export to your MEDHOST chart over the access path your hospital approves.
The connection
What MEDHOST is
MEDHOST is a healthcare IT vendor that has built EHR, clinical, and financial systems for over 35 years, including its YourCare line of EHR, patient engagement, and care coordination products. Its customers are mostly community, rural, and surgical hospitals, often smaller facilities that need an integrated EHR without a large in-house IT team. MEDHOST hosts its FHIR API on AWS so member hospitals do not have to stand up and run their own FHIR server.
Who runs it
Community, rural, and surgical hospitals on MEDHOST
The access path
AGIMAN registers with the MEDHOST Developer Network and authenticates over OAuth 2.0 and SMART on FHIR against your hospital's FHIR R4 v4.0.1 endpoint, with HL7v2 interfaces used where your build still moves results and orders that way. AGIMAN maps the reviewed note and the ICD and CPT codes to the MEDHOST resources and fields your instance exposes, including any MEDHOST FHIR extensions in your build. The first export path is scoped to one department and tested against your own MEDHOST instance before it is turned on, so the fields, code sets, and document types are confirmed against your data before go-live. AGIMAN is not a certified MEDHOST partner and MEDHOST does not endorse it. This is standards-based access to the endpoint your hospital approves.
The MEDHOST export path is scoped to one department and tested against your own MEDHOST instance before go-live, and AGIMAN is not a certified MEDHOST partner.
The workflow
Capture
AGIMINION captures the visit audio in the exam or procedure room and sends it to the AGIMAN appliance on the hospital network. Audio and transcript stay on the appliance, with no internet connection needed to transcribe.
Draft
AGIMAN drafts the chart note in the clinician's style and suggests ICD and CPT codes for the encounter. It also prepares referral letters, patient handouts, and intake and visit forms for review.
Review and sign
The clinician edits the draft, confirms or changes the suggested codes, and signs. Nothing leaves the appliance for MEDHOST until a human approves it.
Sync
AGIMAN sends the signed note and the approved ICD and CPT codes to your MEDHOST chart over the FHIR R4 endpoint, with HL7v2 used where your build moves documents and results that way. Each export is recorded in the review log.
After sign-off
The note the clinician signed is mapped to the MEDHOST document and encounter resources your instance exposes. The draft never reaches the chart before the clinician signs.
The ICD and CPT codes the clinician approved are attached to the MEDHOST encounter for billing and the financial workflow. The clinician confirms every code before it syncs.
Referral letters, patient handouts, and intake and visit forms are prepared as documents and mapped to the MEDHOST fields your build supports. A human confirms each one before it is sent or filed.
On your network
Questions
On the AGIMAN appliance on your hospital network. Room audio, transcripts, and drafts stay local, and AGIMAN does not need an internet connection to transcribe or draft. Only the note and codes the clinician approves are exported to MEDHOST, over the access path your hospital approves.
Through the MEDHOST Developer Network, using OAuth 2.0 and SMART on FHIR against your FHIR R4 v4.0.1 endpoint, with HL7v2 interfaces where your build uses them. Because MEDHOST hosts the FHIR API on AWS, your hospital does not have to run its own FHIR server for this to work.
No. The clinician reviews the drafted note, confirms or edits the ICD and CPT codes, and signs before anything is sent to MEDHOST. AGIMAN automates the drafting and the mapping, not the clinical judgment, and every export is recorded in the review log.
Get started
Buy the appliance and room devices, then scope the MEDHOST export path with us. We test it against your instance before it is turned on.
