How MedJourney connects to the systems around it
The same distinction as on the security page: what exists is listed separately from what is planned.
Available today
-
REST API with OpenAPI
The platform's own API covers applications, documents, offers, messaging and configuration. The OpenAPI description is generated from the running service, so it cannot drift from the code.
-
Patient messaging and referral
Patients can be routed into the platform's messaging module from external channels, keeping the conversation attached to the application rather than a personal phone.
-
Email
Verification codes and notifications are delivered over SMTP from the hospital's own sender identity, so the patient never sees a third-party brand.
-
Push notifications
Device registration and notification delivery for the patient app, with message previews disabled by default so health information does not appear on a lock screen.
On the roadmap
Not available today. If one of these is a prerequisite for your evaluation, tell us in the demo request and we will be direct about timing.
-
HL7 / FHIR
Standards-based clinical data exchange with hospital information systems.
-
HIS / EHR connectors
Direct connectors for patient records, appointments and billing in common hospital systems.
-
Single sign-on
Entra ID and SAML for staff accounts, so panel access follows your existing identity provider.
-
Payment systems
Collecting deposits or payments against an offer, inside the platform.
-
Call centre platforms
Linking inbound calls to the patient application record.
For your technical team
The API description is available in a development environment and can be shared during an evaluation. Integration work is scoped together rather than sold as a fixed package.