Custom objects and app data

Ask about this pageView as MarkdownInstall tools

Portal version: 0.1.0
Updated: 2026-08-28
Source menu item: Custom objects
Availability: Planned

This page defines the intended medOS equivalent. Do not build against it as a live API or operational promise.

The designed app data plane separates registered entity extensions, generic app records, and app-owned MedBase tables.

What you can use now

• Until the governed registry is built, use existing FHIR resources and canonical medOS entities.
• Do not create a parallel patient, encounter, queue, or clinical-result owner.

Current limits

• The app data profile/record/table registration and evidence gate are designed but not operational.

Next step

Use the nearest documented FHIR, webhook, configuration, or hospital-review path today, and treat this page as roadmap guidance only.

Canonical references

• FHIR R4 integration
• Public API
• Security and compliance
• Developer portal status and coverage