magentus fhir · approachable concept · not the official ig

Start with what you're building

The implementation guide lists every profile, package and dependency first. Useful once you know FHIR. A wall before you do. So start the other way: pick the job, and we'll walk only the resources it actually touches, in the order the work happens.

what are you trying to do

Book a theatre case

A booking isn't a row in a calendar. It's a promise: this patient, this surgeon, this team, this list, on this day, with consent given. FHIR can hold all of it. Here are the moves, each mapped to the profile that records it.

01
Request the case
The surgeon's office asks for a theatre slot. The move that starts everything, the thing to be done.
profile Bookings ServiceRequest
02
Hold a place on the list
The case joins a theatre list. The list is the shared commitment everyone reads from, the day's plan.
List theatre list
03
Schedule the when and where
A time and a location get fixed. The appointment the patient and the team see.
profile Bookings Appointment
04
Confirm the team and the needs
Anaesthetist, prosthesis. The detail that turns a slot into a real operating plan.
profile Bookings Anaesthetic Request profile Bookings Prosthesis
05
Capture consent
The patient agrees, on the record. The part of the promise that protects everyone, and the part a calendar row never holds.
profile Bookings Consent
06
Get it confirmed back
The other side accepts. Now the promise is mutual, and the booking is real.
profile Bookings Appointment Response
That's the booking, as a contract.
Profiles you'd never have found by scrolling a dependency table. Same FHIR, just met in the order the work happens.
None of this replaces the standard. Every chip links into the real Magentus Practice Management Implementation Guide, which stays exactly where it is, underneath, as the reference. This layer just gives you a door in.
concept prototype · inverts the ig to lead with jobs, not profiles