VisionVision · not available today. Satin never runs on banking or payment pages.

Where OwnUX is going

Critical information first, for every role and shift. Each person sees what matters, in the order they work.

Vision: the OwnUX SDK is in development and doesn’t support records like these yet. Screens on this page are illustrative.

ward.hospital.example/patients/0048-2291Illustrative
AM

A. Mehra · 67

MRN 0048-2291 · Ward 4B · Bed 12

Pinned
Penicillin allergy High fall risk

Medication due

Paracetamol 1 g oral14:00
Enoxaparin 40 mg SC18:00

Vitals

BP142/88
HR96
SpO₂94%
Temp38.1 °C

Nursing tasks

Observations15:40
Repositionevery 2 h

Today

Physiotherapy15:30
Transport to X-ray16:00
3 more sections, collapsed by preference
Live from the hospital’s record system Standard view

One record. Four ways of reading it. Data, permissions and rules are shared. Order, density and words follow Interface DNA.

Nurses. Medication due, observations and tasks first, in the density that suits a busy shift.

Doctors. New results, trends and the plan first, in compact views with clinical terms.

Front-desk staff. Admissions, schedules and contacts first, with plain labels. Clinical sections stay behind your permissions.

Patients. Results, appointments and medicines in plain words and larger text, once your hospital releases them.

Pinned by you

Hide what you don’t need. Never what matters. Preferences arrange the record. Your safety rules decide what stays.

Clinicians can collapse sections, change density and reorder their view. You decide which are fixed: the patient identity band, allergies and alerts appear for every role, in the same place.

  • Pinned sections can’t be hidden or moved by any preference.
  • Permissions stay in your system. OwnUX can’t grant extra access.
  • Your standard view is always one action away.
How native fallback works

Arrange your view

Illustrative

Sections

Density

Your record

Patient identity
Allergies and alerts
Vitals
Medication
Results
Notes
Tasks
Schedule

For patients

Results patients can understand. In plain words and larger text, when you choose to release them.

Patients see their clinicians’ results in the words and size they asked for. Your clinicians write and approve the plain wording. What patients see, and when, is your decision.

  • Clinical or plain wording, chosen by the patient.
  • Text size and contrast from their Interface DNA.
  • Release rules and consent screens stay locked, and yours.
What Interface DNA holds
10:245G

Ward 4B · Bed 12

Your stay

Latest blood test

CRP 48 mg/L (ref < 5) ↑. WBC 13.1 ×10⁹/L (ref 4.0–11.0) ↑. Consistent with infection. Repeat in 48 h.

Next

Ward round review · 24 Oct, 10:30

Medicines

Paracetamol 1 g PO QDS PRN

Message care team

The patient’s Interface DNA

Illustrative

Words

Text sizeStandard

Clinicians approve the plain wording. The hospital decides what is released, and when.

Made for software where mistakes matter. The same safety model runs under every OwnUX screen.

Verified, never assumed. Every change goes through your own API and is read back before OwnUX says it’s done.

Your view, one action away. Every OwnUX screen starts with a switch back to your own interface.

No AI acting alone. Screens come from deterministic templates and your approved components. OwnUX never writes code into a page.

Locked surfaces. List consent, sign-off, billing and security screens as locked, and OwnUX never re-renders them.

Your data stays with you. Patient data stays between your backend and frontend, as today. Satin never receives your users’ content.

Measured, not assumed. Roll out to some staff, keep a holdout group, and compare against those without OwnUX.

Questions, answered.

In developmentThe OwnUX SDK is in development. Today’s alpha runs in our Reference App, works with React and covers tasks. Records like the ones on this page need capabilities beyond the alpha.

No. OwnUX changes how information is arranged and worded for each person. It never decides what is clinically important. Your rules and your clinicians do.

Put critical information first. For every role, on every shift.