Patient History Viewer · Feature documentation
The whole picture, before you say hello.
MediAttune.AI reads a practice's own Office Ally records through the SMART on FHIR® API and lays out each patient's active problems, medications, allergies, and recent results in one place — so the physician walks in already caught up. Provider-authorized, read-only, and never written to disk.
- FHIR® R4
- US Core 3.1.1
- OAuth 2.0 · Authorization Code + PKCE
- Read-only access
What it is
MediAttune.AI is an iOS clinical-documentation app built for independent and small-group physician practices — the solo doctors and small teams who carry their own after-hours charting. The Patient History Viewer is the part of the app that connects to Office Ally.
When a physician opens a patient, the viewer gathers that patient's recent clinical record from the practice's Office Ally account and presents it as a single, readable summary the physician can scan before and during the visit. It is a window onto the chart — a reading surface, not a place where new records are created.
01How the integration works
Four properties define every request the app makes to Office Ally.
The physician authorizes it
The physician signs in with their own Office Ally credentials and approves a consent screen. The app never sees or stores those credentials — it receives a scoped access token through the standard OAuth 2.0 Authorization Code flow with PKCE.
Read-only, always
The app requests read scopes only. It does not create, update, or delete anything through the FHIR API. Documentation a physician produces elsewhere in the app is entered and signed through Office Ally's own interface, under the physician's review.
Scoped to the practice's patients
Access is limited to the authorizing physician's own practice records, following the minimum-necessary principle — the app asks only for the resource types the history view actually displays.
Standards-based
The integration uses FHIR® R4 with US Core 3.1.1 profiles against Office Ally's SMART on FHIR® server, so the data model follows the published specification rather than anything proprietary.
02What it reads
The Patient History Viewer requests the clinical resources a physician needs to get oriented — all read-only:
- Patient
- Condition
- MedicationRequest
- AllergyIntolerance
- Observation
- DiagnosticReport
- Procedure
Additional resource types (such as Immunization, CarePlan, or clinical notes via DocumentReference) may be requested only where the history view surfaces them. Office Ally's API provides read access only; there is no write path, by design.
03How patient data is protected
- Held in memory, not on disk. Patient data retrieved from Office Ally lives in device memory for the active session only. It is never written to the device's storage.
- Never sold. Never shared for anyone else's purposes. Patient information is not sold, and is not disclosed to any third party for that party's own use.
- AI processing under agreement. Documentation features are AI-assisted; any patient data processed by our AI provider is handled by that provider as a subprocessor under a Business Associate Agreement, solely to deliver the service.
- Agreement before access. A Business Associate Agreement is executed with the practice before any feature that touches patient data is enabled.