3 min read

Meditech Integration

MEDITECH is planned, not supported. A Rehab administrator can record a MEDITECH hospital record import connection (read-only, FHIR R4). It would work only if the hospital grants SMART Backend Services access; where it offers only SMART app launch, which ArkCloud does not have, the connection is shown as unsupported. Nothing has been tested against MEDITECH. There is also no working HL7 v2 interface that a MEDITECH site could send to. This page says what that means and how a MEDITECH site can exchange data with ArkCloud today.

Not built

A MEDITECH-specific connector of any kind (Expanse, MAGIC, Client/Server or 6.x), and any test against a MEDITECH system

SMART app launch (provider or patient authorised), which is often the only access a MEDITECH hospital offers: a connection that needs it is recorded as unsupported

HL7 v2 feeds from MEDITECH: there is no MLLP listener or inbound HL7 interface (the HL7 API only parses, validates and generates messages for an administrator)

NPR report extracts, DPM access or direct database connections

Automatic demographic, insurance or charge synchronisation

Posting payments or account updates back to MEDITECH

What it would take

This is a list of engineering gaps, not a delivery commitment. A MEDITECH exchange would need at least:

SMART provider launch (authorization code and refresh), where the hospital does not grant Backend Services.
MEDITECH Greenfield registration, and the hospital activating ArkCloud's client and agreeing to release records.
For HL7 v2: an MLLP listener, message routing into patient and charge records, and acknowledgement handling.
Field mapping and tests against a MEDITECH test environment.

Exchanging data today

Outside records (Rehab)

Staff upload records a MEDITECH hospital sent them - a FHIR R4 bundle, a C-CDA document or a PDF - and a clinician reviews what is proposed for the chart.

Outside records

Claims and remittance

Claims go out and 999, 277CA and 835 files come back through your clearinghouse's SFTP mailbox, independent of any EHR.

Clearinghouse

File and CSV imports

An administrator can create Amazon S3, SFTP or manual-upload connections under Settings → Integrations → Connections for extracts produced from MEDITECH. Connections can be set up and tested, but file pipelines are not available: inbound files are not imported into ArkCloud and exports are not generated or delivered.

Custom integrations

Implementation work

For anything else, contact support. Any MEDITECH-specific work would be scoped as a project; there is nothing to switch on.

Contact support

HL7 v2 messaging EMR Integration Epic Integration Cerner Integration