Mobile-ID Digital TrustISO/IEC 27001:2022 · SIS351224I008Published certification scope
View evidence

AI / IMAGING

Health AI

Governed assistance for professionals; no claims of autonomous diagnosis, guaranteed outcomes or regulatory approval.

AI Capabilities

Clinical NLP · structured extraction · summarization · trend analysis · anomaly detection · prioritization · document understanding

Evidence required before publication

AI Governance

Owner · intended use · data boundary · validation · human oversight · change control

Evidence required before publication

AI Transparency

Model/version · known limits · confidence · provenance · review trail

Evidence required before publication
HUMAN DECISION BOUNDARY

AI assists; accountable professionals decide

Health AI is presented as a governed assistance layer. Inputs, model version, output, confidence/limitations and the human response must remain distinguishable so an AI suggestion never silently becomes a clinical decision.

01

Intended role

Use AI for supported summarization, prioritization or decision support only within the declared use case; diagnostic or autonomous treatment claims require separate verification.

02

Input context

Bind output to the source data, subject, encounter/time window and quality state used for inference; missing or stale inputs remain visible.

03

Output contract

Present recommendation/signal with model version, confidence or uncertainty representation when available, limitations and the action expected from the reviewer.

04

Human control

Authorized professionals can accept, reject, override or escalate. Their final decision and rationale remain separate from the model output.

INFERENCE JOURNEY

From source data to reviewable assistance

The operating flow keeps data quality, model identity and human action explicit.

Validate contextConfirm source, subject, freshness and required fields before inference.
Invoke versioned modelRun only an approved model/version in the configured environment.
Return bounded outputAttach version, timestamp and uncertainty/limitations to the result.
Human reviewPresent source context and AI output together; do not hide contradictory evidence.
Decide or escalateReviewer accepts, overrides, requests more data or escalates according to policy.
Record outcomeCorrelate model output, reviewer action and downstream handoff for audit/monitoring.
MODEL LIFECYCLE

Production AI is a controlled release

Model behavior can change even when the UI does not. Release, monitoring and rollback therefore belong in the product boundary.

01

Registry & version

Track model identity, version, intended use and environment. A model change is a controlled product change, not an invisible file replacement.

02

Evaluation

Keep test/evaluation evidence tied to the use case and population/context assessed; avoid generalizing beyond that evidence.

03

Monitoring

Observe operational quality, missing inputs, override patterns, drift signals and failure modes appropriate to the deployed use case.

04

Rollback & incident

Support disabling/rolling back a problematic version and preserve the correlation needed to investigate affected outputs.

AI USE CASES

AI by operational workspace

Each use case exposes intended use, input/output, human oversight, failure modes, model version and evidence.

AI by operational workspace
# Application Use case Control Status
1 Patient App Data summary · trends · compliance Human review · Override · Evidence Configuration dependent
2 Doctor Portal Patient 360 · decision support · outcomes-focused Human review · Override · Evidence Configuration dependent
3 Nurse Portal Priority alert · care gap · escalation Human review · Override · Evidence Configuration dependent
4 Laboratory Identification · QC anomaly · critical value Human review · Override · Evidence Configuration dependent
5 Pharmacy Medication reconciliation · duplication · safety Human review · Override · Evidence Configuration dependent
6 CareGiver Compliance · change notification · handover Human review · Override · Evidence Configuration dependent
7 TeleHealth Pre-visit summary · notes · follow-up Human review · Override · Evidence Configuration dependent
8 Kiosk Measurement quality · mismatch · retry Human review · Override · Evidence Configuration dependent
9 Admin Capabilities · SLA risk · Operational anomalies Human review · Override · Evidence Configuration dependent
Registry & VersionEvaluationBias/FairnessDriftIncidentRollback

AI starts with an operational decision

Each use case states the user, input, output and the point where a person must review the result before action.

AI starts with an operational decision
Application Use case Input Output Human review / failure Status
Patient Monitoring alert prioritization Observations, trends, configured thresholds Attention queue No autonomous diagnosis; insufficient data → no conclusion Configuration dependent
Doctor Pre-visit summarization Encounter, Observation, DiagnosticReport Reviewable summary Clinician validates and may discard/edit Planned
Nurse Worklist prioritization Task, care plan, alert Suggested order Nurse adjusts based on actual condition Planned
Kiosk Repeat-measurement signal Quality flag, device state, range Retry/escalation suggestion No diagnosis; device fault → stop/retry Configuration dependent
Pharmacy Risk-review assistance MedicationRequest, allergy, rule context Items for pharmacist review Pharmacist decides; missing data → clarification Planned
Laboratory Validation queue prioritization QC, result flags, reference context Priority queue Lab professional validates; critical values follow SOP Planned
Caregiver Task attention suggestion Task, adherence, alert Priority list Never expands delegated access Planned
TeleHealth Pre-consultation preparation Appointment, uploads, observations Pre-visit summary Clinician reviews; reconnect/low bandwidth is not delegated to AI Planned
Administration Operational anomaly signal Audit/event metrics Investigation signal Administrator verifies before action Planned
No accuracy claim: does not publish accuracy, clinical-benefit or regulatory-approval claims without supporting evidence.

Google Cloud Healthcare is not an AI model

Cloud Healthcare API can provide a FHIR/HL7v2/DICOM data plane and events for downstream analytics or AI. Human review and decision evidence remain part of Trusted Care workflows.

Explore the Google Cloud Healthcare architecture →
Screen detail

Search all Trusted Care
TRUSTED CARE

09 applications

Governed application access; no unverified login URL is invented.

Patient AppPatients & familiesRequest accessDoctor PortalDoctors & cliniciansRequest accessNurse & Care CoordinatorNurses & care coordinatorsRequest accessAdmin PortalOrganization administratorsRequest accessHealth KioskReception & service pointsRequest accessPharmacy PortalPharmacistsRequest accessLaboratory PortalLaboratory teamsRequest accessCareGiver AppCaregivers & familiesRequest accessTelehealthPatients & care teamsRequest access