# Design patterns

**Portal version:** 0.1.0  
**Updated:** 2026-08-28  
**Source menu item:** Design patterns  
**Availability:** Documented and testable

> The source contract and local workflow exist. Access still depends on the target hospital deployment and its policy gates.

Use status color only for meaningful state, show clinical provenance, preserve host context, and make every denied/unavailable condition visible.

## What you can use now

- Prefer one clear primary task, compact responsive layout, accessible controls, and reversible actions.
- Never mimic a signed medOS decision or hide whether data came from the partner.

## Current limits

- Partner UI does not inherit unrestricted medOS styling or components.

## Next step

Start with the [medOS Developer overview](/developers/platform/overview) and confirm the target hospital’s enabled contracts before production work.

## Canonical references

- [FHIR R4 integration](/integrations/fhir)
- [Public API](/backend/public-api)
- [Security and compliance](/architecture/security-and-compliance)
- [Developer portal status and coverage](/developers/platform/changelog)