Enterprise · Deployment
Try Records in public. Operate it inside the boundary your data policy requires.
The Records core stays the same. Operator, data policy, identity, networking, retention, and recovery change with the deployment contract.
Where Records sits
Records runs beside the FHIR server it observes and reads through the standard API. What changes with the deployment contract is who operates that observer, not the position it holds.
FHIR server
Your existing infrastructure and source resources.
Records
Observes the permitted scope. Read-only by default.
Conformance
Results against the selected requirements.
Validation
Findings tied to resources and fields.
Drift
Changes against an accepted baseline.
Deployment and evaluation options
Availability is stated separately from architecture so a future option cannot read like a current entitlement.
Available now
Public demo
Evaluate Records against curated public FHIR servers
- Operator
- MedVertical
- Data boundary
- Public and permitted non-production data only
Request access
Records Workspace
Evaluate one FHIR delivery with conformance checks, quality indicators, findings, and a repeat run
- Operator
- MedVertical
- Data boundary
- Development, test, synthetic, or de-identified data during staged access
Enterprise qualification
Customer-managed Enterprise
Run the shared Records core inside a controlled customer environment
- Operator
- Customer or contracted operator
- Data boundary
- Customer network, identity, terminology, retention, and recovery controls
Two production operating contracts
Public Demo is an evaluation surface. Production operation resolves to one of two governed contracts.
Hosted · staged access
MedVertical operates the workspace
Evaluation starts with a permitted non-production data class and one named workflow. Region, tenant controls, support, retention, and recovery are qualified separately before production use.
Customer-managed Enterprise
Records runs in the customer environment
The customer owns the network, identity boundary, terminology strategy, database recovery, and operating approvals under the contracted deployment runbook.
The operating surface does not change with the contract
Whoever operates Records works with the same connected servers, their environment assignment and their current connection state. The deployment contract decides who holds this surface and which data may reach it.
Start with the boundary, not the hosting label.
Tell us what data may be processed, who must operate Records, and which controls the review requires.