Set up MEDITECH filing

Faxart files approved faxes to MEDITECH as HL7 messages over SFTP. This guide connects the interface and explains the human-in-the-loop gate that protects the chart.

How filing works

An approved fax’s extracted fields become an HL7 message (an ORU result, or an MDM document) with the page embedded. The broker drops it on the interface engine’s SFTP endpoint, where it lands in MEDITECH’s imaging/DMS indexed by patient, document type, and date.

flowchart LR
  A[Approved fax<br/>+ confirmed patient] --> B[Build HL7<br/>ORU or MDM]
  B --> C[SFTP to<br/>interface engine]
  C --> D[MEDITECH<br/>imaging / DMS]

Prerequisites

• An interface engine that accepts HL7 over SFTP
• An SFTP account for Faxart, and the engine’s host key
• A private key for Faxart, provided as a mounted secret (never web-editable)
• Your informatics team’s field mapping, reconciled against the interface spec

Steps

1. Provide the SFTP private key to the broker as a mounted secret. The path is the one configuration value that stays out of the web UI on purpose.
2. In the web app’s MEDITECH settings, enter the host, user, remote path, host key, and processing ID. These are admin-set in the database, not the environment.
3. Use the connection test in the commissioning console to confirm the host key pins and the upload path is writable.
4. File a test document and confirm it appears in MEDITECH.

The safety property

A person confirms the patient before any HL7 is sent. The suggested MRN, name, and date of birth extracted from the document are candidates, never trusted on their own. Auto-mode can route a fax without a human, but it will never file one to a chart without a human confirming the patient. That line does not move.

See also

• Configuration reference for the MEDITECH keys
• Keeping PHI on-prem