Does WebPT have an API?+
WebPT does not publish public REST API documentation that we could find. Its integrations page describes standard HL7 interfaces for patient registration, billing, outbound documentation and inbound documents, plus custom integrations on request.
How do you integrate with WebPT?+
Through WebPT's standard HL7 interfaces. The clinic requests the integration, WebPT assigns a point of contact, the message specification is agreed, and the other system sends or receives the HL7 messages. We build and test that other side.
Which HL7 messages does WebPT use?+
WebPT's page lists HL7 ADT for inbound patient registration, ADT, BAR and DFT for outbound billing, and MDM or ORU for outbound documentation with the PDF embedded in Base64. Inbound documents land in the WebPT eDoc section.
Can we send referrals and prescriptions into WebPT?+
Yes. WebPT's inbound documentation integration stores documents such as prescriptions in the eDoc section of the patient's chart. We build the sending side and the patient matching so each document lands in the right chart.
Can WebPT send completed notes to our hospital EHR?+
Yes. WebPT's outbound documentation integration sends HL7 MDM or ORU messages when a document is completed, with the PDF embedded. Your EHR or interface engine has to decode the PDF and file it to the right patient and encounter.
Can WebPT send charges to our billing system?+
Yes. WebPT's outbound billing integration sends HL7 ADT, BAR and DFT messages that create claims in a billing system. The receiving system needs mapping for codes, units, modifiers and diagnoses.
Is there an unofficial WebPT API?+
Some companies sell access that automates the WebPT web application. We start with WebPT's own interfaces and use login-based automation only where WebPT's terms and the clinic's written authorization allow it.
Who maintains a WebPT interface after go-live?+
WebPT maintains and monitors its side. We maintain the channels, mapping and alerts on your side, with a shared runbook for failures.
Do we need an interface engine?+
Usually yes. HL7 interfaces are easiest to run through an engine such as Mirth Connect, which handles acknowledgments, retries and error queues. If your product has its own HL7 listener, we build there instead.
How long does a WebPT integration take?+
Our initial planning estimate is 6 to 10 weeks for one interface type, depending mostly on WebPT's integration schedule and how ready the other system is.
How much does a WebPT integration cost?+
Cost depends on the interface types, the receiving or sending system, patient matching, document handling and support level. After a scoping call we send a scoped proposal with the access dependencies listed.
