Available now
Public demo
Evaluate Records against curated public FHIR servers
- Operator
- MedVertical
- Data boundary
- Public and permitted non-production data only
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.
Deployment and evaluation options
Availability is stated separately from architecture so a future option cannot read like a current entitlement.
Request access
Records Workspace
Evaluate a hosted Records workspace with your permitted server and validation scope
- 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
| Option | Purpose | Operator | Data boundary | Availability | Next action |
|---|---|---|---|---|---|
| Public demo | Evaluate Records against curated public FHIR servers | MedVertical | Public and permitted non-production data only | Available now | Explore public servers |
| Records Workspace | Evaluate a hosted Records workspace with your permitted server and validation scope | MedVertical | Development, test, synthetic, or de-identified data during staged access | Request access | Request hosted access |
| Customer-managed Enterprise | Run the shared Records core inside a controlled customer environment | Customer or contracted operator | Customer network, identity, terminology, retention, and recovery controls | Enterprise qualification | Review the deployment boundary |
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.
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.