Connecting any FHIR R4 system
How 2care connects to an EHR through its HL7 FHIR R4 interface, what you need, the setup steps, and what is read and written during a call.
3 min read
How it connects
2care connects to any HL7 FHIR R4 endpoint. FHIR R4 is the standards route for systems beyond the named list, so if your EHR offers it, 2care can work inside it.
The connection uses server-to-server authorisation with short-lived tokens, approved by your practice or your EHR's administrator. Availability and patient records are read live, and the booking is written back during the call.
- FHIR R4. A shared healthcare data standard many EHRs publish, so outside systems can read and write records in a common format.
- Endpoint. The address of your EHR's FHIR interface, which your EHR provider or administrator can give you.
- Server-to-server authorisation. A connection approved once by your practice, with no staff login shared with 2care.
- BAA. The Business Associate Agreement your practice signs with 2care before any patient data moves.
Before you start
| Item | Who provides it |
|---|---|
| A signed BAA with 2care | Signed before any patient data moves |
| Confirmation that your EHR offers a FHIR R4 interface | Your EHR provider or practice administrator |
| Approval to register 2care as a server-to-server connection | Your practice administrator |
| Your provider list and the locations each one works at | Your practice manager |
| Your visit types and booking rules | Your practice manager |
Setup
- Sign the BAA. No patient data is read until it is in place.
- Confirm your FHIR R4 interface. Your onboarding specialist checks the details with your EHR provider or administrator.
- Register and approve the connection. 2care is registered as a server-to-server connection and your administrator approves it.
- Confirm providers, locations and visit types. Each is matched to what your EHR already holds. See visit types and provider templates.
- Agree booking rules and escalation contacts. These decide what the agent offers and who receives urgent calls.
- Run a test round trip. A test appointment is booked, opened in your EHR, then cancelled, with your team watching.
- Switch the line over. Your number forwards to 2care at the hours you choose. See forwarding your number.
On a booking call
| Step in the call | What the caller hears | What happens in your EHR |
|---|---|---|
| Identity | A check of their name and date of birth | The caller is matched to an existing patient record |
| Availability | The open times for the provider they asked for | Open slots read live for that provider, visit type and location |
| Choice | The time they chose, read back | The slot is held and your booking rules are applied |
| Booking | Confirmation of the appointment | The appointment is written to your EHR |
| Confirmation | A text with the date, time and location | The booking is confirmed once your EHR accepts it |
If the slot was taken in the meantime, your EHR refuses the write and the agent offers the next open time instead.
What 2care reads
- Open slots by provider, visit type and location
- Patient records, to recognise a returning caller and avoid a duplicate
- Coverage on file and the care team for each patient
- Provider and location details for your practice
What 2care writes
- New, moved and cancelled appointments
- New patient registrations and updates to contact details
What 2care never touches
- Clinical notes, results and medications
- Anything outside the access your practice approved
Questions
Our EHR is not in the list of setup guides. Can we still connect?
Yes. 2care has 95+ integrations, and FHIR R4 is the route for most of the rest. If your system offers neither, tell us what you use and we will plan the connection with you.
How long does setup take?
Most practices are live in about 5 business days once the connection is approved.
Related
Was this page helpful?