# Baltique OS Core 2.2.0
## Clinical Experience, Identity, Smart Intake & Governed AI Release

Core 2.2.0 is a cumulative release for Baltique OS 2.1.0.1. It combines official dark/light themes, effective site-scoped data context, secure patient identity and encrypted structured address, document/photo/live-camera intake, governed pre-operative laboratory review, independent patient language, bilingual document governance and the Premium Patient Care Guide.

## Core scope

- official `Dark`, `Light` and `System` themes;
- role- and user-governed location visibility, including an authorized all-sites overview;
- PESEL validation and passport/foreign ID support;
- encrypted patient identifiers and blind duplicate indexes;
- encrypted residential address with structured country/postal/city routing fields;
- optional Facebook/Instagram profiles with separate evidence-based contact and marketing consent;
- manual, file/photo and live-camera patient intake;
- OCR as assistive evidence only; staff review is mandatory;
- independent Polish/English patient communication and document locale;
- clinician-reviewed pre-op laboratory intelligence and message drafts;
- two-stage Premium Patient Care Guide with explicit synthetic disclosure;
- role workspaces, technical-route protection, staff PWA and governed Web Push.

## Patient address model

The new patient workflow requires a residential address consisting of country, postal code, city, administrative area, street, building number, optional unit number and an optional second address line. The detailed payload is encrypted at rest. Approved documents can use `{{patient.address_formatted}}`.

## Clinical safety

The release does not automatically diagnose, issue anaesthesia clearance, change GO/HOLD/NO-GO, sign documents, send medical instructions, move OR stages or apply Digital Twin scenarios. Laboratory output and patient communication remain human-reviewed.

## Deployment

See `README_UPGRADE_2_2_0.md` and `docs/POST_DEPLOYMENT_ACCEPTANCE_2_2_0.md`.

## Validation boundary

The package is statically validated and archive-verified. It has not been executed against the live OVH database. Staging migration, restore proof, UAT, load testing, clinical governance and legal approval remain mandatory before clinical production use.