Metriport raises $26 million to give clinicians insight at the point of care

Send, not just receive.

Send and receive referrals to other providers, and send electronic case reports to public health agencies.

Join the teams already reaching every connected network, and sending runs on the same one.

Sollis Health customer story EasyHealth customer story Color customer story Brightside Health customer story

Two directions, one connection.

Send and receive referrals

Refer out to other providers and receive inbound referrals, with the patient context travelling alongside. No separate referral network to join.

File electronic case reports

Reportable conditions go to public health agencies from the consolidated record. One path, not one per jurisdiction.

Both directions, one list

Inbound and outbound sit in the same message list, on the same connection and the same patient identity as retrieval. Receiving is not a second integration either.

Know when it lands

The send returns straight away and the delivery is reported after it, so nothing sits in an unknown state. Take it on the webhook you already run, or ask for it.

Benefits

Sending is not a second integration.

The same directory, the same record, the same webhook.

No referral network to sign up for.

The destinations are the network directory Metriport already reaches, filtered to the organizations that can receive a message. You search it by name, NPI or address, the ones that support messaging come back flagged, and the delivery method (Direct Message or XCDR) is picked for you.

The referral carries the record, not a summary of it.

Attachments are document IDs out of the consolidated record, so what travels with a referral is the source material itself rather than a re-typed face sheet.

Inbound lands in the record, not in an inbox.

Messages sent to you arrive on the webhook you already run, with a presigned URL for the content. Where the patient matches, the message carries into Consolidated Data; where it does not, it waits in the message list rather than disappearing.

How it works

Send on the rails you query.

1. Find the destination - List Network Entries with supportsMessaging set to true returns the organizations that can receive a message. The destination is an OID or a Direct address, and Metriport picks the delivery method.

2. Send the message - A subject plus a body or attachments, about a specific patient. Documents go up first through Upload Document; the endpoint returns a processing status immediately.

3. Hear back on your webhook - message.status reports delivery or failure. Inbound messages arrive as message.received with a presigned URL for the content, and a matched patient carries them in Consolidated Data.

FAQs

1. How does this relate to the rest of Metriport? Retrieval and messaging run over the same network connections and the same patient identity. If Metriport is already reconciling a patient's record for you, sending a referral or a case report about that patient does not require a new integration.

2. Is messaging available today? Messaging capabilities are rolled out with individual customers. Talk to us about your referral or public health reporting requirements and we will walk through what is available for your setup.