01 / JOURNEY
A first visit, with fewer unknowns
Give a new patient a considered place to share registration details and an emergency contact before they arrive.
Explore first-visit intakeTrial access requiredA patient-first Connect journey
Patient intake APIs. Every answer has a next step.
Explore two patient intake workflows for Australian practices: first-visit registration with an emergency contact, and referral letter upload into patient correspondence. See which MediRecords API operations are live, simulated or need authorised action.
Demo available · Conditional live calls
Safe by designGrounded in Connect APIs
THE INTAKE JOURNEY EXAMPLE FLOW
Patient answersDetails shared on their terms
01Reviewed with contextStaff verification before action
Connected, step by stepDocumented operations, honest status
03Not just a form.
A workflow you can understand.
Each step has a reason
One platform story. Two useful paths.
Two patient intake
API workflows.
Different patients arrive with different needs. Connect helps teams see what was shared, what needs review and which integration step is supported.
02 / JOURNEY
Referral letter upload
Collect patient details and a referral letter. In authorised live mode, the file is sent to MediRecords Correspondence In after the patient write succeeds. Simulated runs retain metadata only, not the file, and do not deliver it.
Explore referral letter uploadTrial access requiredFrom answer to action
Make the handoffs visible.
A form is only the beginning. A useful integration story makes ownership, identity checks and API boundaries clear along the way.
Follow the API journeyTrial access required- 01PATIENT
Patient shares what matters
Collect the information needed for this visit—not a catch-all profile.
- 02PRACTICE
Practice reviews and verifies
Keep staff identity checks and decisions out of the patient-facing form.
- 03INTEGRATION
Connect traces each operation
See what is documented, what is simulated and what requires authorised action.
Clear about capability
Trust starts with precise language.
The demo distinguishes API documentation from current behaviour. Explore the form scenarios, then inspect the sequence behind them.
A
Live calls need authorisation
The demo distinguishes configured, authorised API writes from simulated outcomes. A simulated success does not mean a patient record or document was written to MediRecords.
LIVE OR SIMULATEDB
First visit stays focused
The first-visit journey covers registration and an emergency contact. It does not collect clinical history or consent choices; referral letter upload is the other public journey.
REGISTRATION + CONTACTC
A letter, not a native referral record
The uploaded letter is filed in Correspondence In only when live delivery is confirmed. This does not create a Patients > Referrals record, verify the referring doctor or signed letter, or confirm Medicare eligibility. Typed sender details remain unverified notes.
CORRESPONDENCE INNo hidden trigger. This story does not promise booking-triggered SMS, automatic intake invitations or guaranteed record updates. Each integration step is shown on its own merits.
Ready to see it in context?
Follow the journey, not just the form.
Open the intake experience or step through the operations that connect patient answers to practice workflows.