A bone-health enrolment carrying the FRAX percentages as they were calculated elsewhere, DEXA results with the next scan due 24 months after the last, an append-only therapy log, and a liaison record on every fragility fracture.
How you actually use it
1Enrol on a FRAXOn Enrol on bone health, find the patient and type the FRAX major and hip percentages that justify it, then Enrol. Both sit on 0–100, a patient has one active enrolment, and enrolling dates the programme’s review milestones. FRAX on a row records a reassessment.
2Record DEXADetail opens the patient; T-score and site — spine, hip or forearm — then Record DEXA. The next scan is the scan date plus 24 months, computed on read; DEXA due appears once that date has passed, and on a patient who has never been scanned at all. A T-score outside −6 to +4 is refused as a positioning error, not a bone.
3Log fractures and liaise themLog fracture with the site. Each fracture shows not liaised until somebody presses Mark liaised, and the registry row counts the unliaised ones.
4Log therapyLog therapy with the drug and the dose. The row is appended with its author and never edited.
5Read the registry flagUntreated high risk is a T-score of −2.5 or below, or a fracture, with no therapy row; on therapy and watching are the other two states. The flag is computed on every load and never stored. Stop asks why the patient is leaving.
See it on screen
Live product01Bone Health — Bone strength screening and fracture preventionCaptured from the running demo clinic
1 of 1
Connected to
Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.
Same patient record as every other app — nothing is copied into a silo. Data class: Full PHI.
What it does not do
It does not calculate FRAX, and it gates no discharge. Every fragility fracture opens a liaison record, and that record can be liaised only once.
Every app page carries this section. A listing with only benefits is an advertisement.
Questions clinics ask
What data does OsteoGuard read and write?
OsteoGuard reads care plans, patient record and writes enrolments, DEXA results, fractures, therapy steps. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.
What does OsteoGuard deliberately not do?
It does not calculate FRAX, and it gates no discharge. Every fragility fracture opens a liaison record, and that record can be liaised only once.
What happens to our data if we uninstall OsteoGuard?
All clinical data stays in the record; operational history stays queryable.
Is OsteoGuard available today?
Yes — OsteoGuard is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.
Ask about OsteoGuard
Want to see OsteoGuard running on your own patients?
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.