A health assessment, read as one record and one report.

The reading. The assessment produces the documents; Vitrubo reads them into one FHIR R4 health record for that person and returns one report. Lab panels arrive as values, so trends and ranges are computed. Imaging reports, the consultation note, questionnaires and prescriptions are read as context, so a marker is interpreted with the medication and the finding that bear on it. The report comes in two views, one for the clinician who signs it and one for the client who reads it.

Four steps. Parse: each document arrives as a lab PDF, a scanned report, a photo, an HL7 or FHIR feed or JSON, and numbers, units, ranges and flags are computed by deterministic code. Structure: every value is mapped to LOINC and its unit to UCUM, and the document becomes part of one FHIR R4 record for that person. Understand: values are read together, against the previous assessment and the notes on file, with named guidance cited claim by claim. Deliver: a clinician view, a client view, a PDF or JSON through the API.

On one scale. Every value from every year is normalised to one of 17,000+ LOINC codes and to UCUM units, so a marker measured at one laboratory in one year and at another the next reads as points on one line rather than two formats. The report then says which values moved, which came back to normal and which have never moved, and places each in one of four zones. This is the comparison an annual health check is sold on. Reference ranges are kept per laboratory, because the range that applies to a value is the one the lab that measured it published.

Because the assessment's value is in the comparison, and the comparison is the part most programmes leave to the client. A folder of departmental print-outs handed over at the end of the day is hard to read and harder to compare with last year's folder. When the programme returns one report that names what changed since the last health assessment, the consultation has more to say, the client has a reason to come back, and the executive health programme's value compounds rather than resetting each year.

The clinician view is the whole health record before the appointment: flagged results grouped into connected stories, each with its trend across assessments, the conditions and medications it connects to, the guidance it rests on one chip away, and the tests worth considering next. The physician reads it, agrees or disagrees, and signs. Vitrubo drafts; it does not decide. The hour with the client is spent on the conversation, not on reconciling the departmental reports.

No. Vitrubo is not a diagnostic device, does not select treatment and does not replace the physician who closes the assessment. It drafts a reading of the results that are there, organises the record and names tests worth considering; the clinician reads and signs. For a person reading their own assessment it is educational context to bring to the next appointment, not medical advice.

No. Vitrubo runs no clinic, no laboratory and no imaging, and sells no assessment of its own. The assessment is performed by the clinic, hospital or programme, and Vitrubo is licensed to them as the reading layer, delivered under their brand. Access is by invitation after an evaluation on your own anonymised folders; there is no self-serve signup and no published price list.

Any laboratory result reported as a value, in any panel: metabolic and lipid panels, blood count, inflammation, iron and vitamin status, thyroid and other hormones, kidney and liver markers, urine and allergy tests. Imaging reports, ECG and other cardiac reports, the consultation note, lifestyle and family history questionnaires, prescriptions and hospital records are read as context. A document read as context is not scored; it is known when the values are interpreted.

Containers run inside the hospital's perimeter or in a private cloud; the hospital owns the keys and Vitrubo has no access to the data. Lab results arrive from the LIS as HL7 or FHIR R4, documents from the EHR, and the drafted reading flows back as FHIR or JSON into the same EHR or into a role-based portal under the hospital's brand. Identity never enters the prompt: the models see values and an internal ID. A HIPAA business associate agreement for US deployments and GDPR Article 28 terms.

Yes, through a clinic, programme or health app that offers Vitrubo under its own brand. The person uploads the folder as PDFs or photos and reads the plain-language view: what stands out, why it is grouped that way, and what to discuss with a doctor. Earlier assessments uploaded alongside are read into the same history, so one assessment is read on its own and two or more are read as a line. Vitrudoc, the AI chat grounded only in that person's own record, can answer questions about the folder beside the report.

With a call, then sandbox access and API documentation. Your team runs its own anonymised folders, ideally two consecutive health assessments from the same clients, and your physician validates the drafts against their own reading. There is no commitment at that stage; production follows when you are ready, inside your perimeter or a private cloud, connected to the LIS and EHR or through the client portal.