Deployment Profiles
SCRIMED deployment readiness turns enterprise infrastructure constraints into proof-ready pilot profiles.
These profiles help buyers evaluate managed cloud, private cloud, hospital-controlled, sovereign, and edge/on-prem paths before live data, clinical execution, or production connectors are approved.
Proof boundary
Deployment profiles are attached to protected pilot proof packets as readiness evidence and production gate context.
SCRIMED deployment profiles are synthetic pilot and enterprise evaluation readiness fixtures. They are not cloud certifications, HIPAA certifications, SOC 2 reports, sovereign-cloud approvals, medical-device authorizations, or production clinical execution approvals.
01npm unavailable in the local shell is handled through direct Node entrypoints for lint, typecheck, integrity, and build.
02Local Turbopack is blocked by macOS SWC code-signature validation, so production verification uses Next's Webpack fallback while Vercel builds continue to report READY.
03No-secret public production readiness is handled by scripts/public-production-smoke.mjs.
04Authenticated mutation smoke remains gated by the out-of-band SCRIMED_BEARER_TOKEN secret and cannot be safely resolved in source code.
Profiles
Each deployment path defines buyer fit, revenue use, controls, metrics, gates, and blocked claims.
protected-pilot-ready
Managed Cloud Pilot Profile
US providers, payers, and healthcare operators evaluating SCRIMED on managed cloud infrastructure.. Fastest commercial path for governed synthetic evaluations and protected enterprise pilots when buyers do not require on-prem or sovereign isolation.
Default paid assessment, synthetic pilot, and protected pilot deployment profile.
- Environment: Vercel application runtime with Supabase Auth/Postgres and Upstash rate limiting.
- Cost model: Platform license plus protected pilot fee, workflow modules, implementation services, and usage bands after validation.
- Data posture: US managed cloud posture for current protected-pilot workspace; regional expansion requires customer review.
- Blocked claims: HIPAA certified, SOC 2 certified, production clinical system, autonomous diagnosis
external-approval-required
Private Cloud Readiness Profile
Health systems and payers requiring customer-controlled cloud tenancy or private network posture.. Enterprise buyers can evaluate how AgentOS, Atlas, TrustOS, and protected workspaces would move into controlled infrastructure after a synthetic proof phase.
Premium implementation and annual platform license expansion for larger enterprise accounts.
- Environment: Customer cloud or private-cloud architecture review with SCRIMED runtime components mapped before deployment.
- Cost model: Annual platform license plus private-cloud implementation, security review, connector scope, and support tier.
- Data posture: Customer-defined residency and backup posture; no cross-border assumption.
- Blocked claims: customer environment approved, private cloud certified, EHR production connected
external-approval-required
Hospital-Controlled Runtime Profile
Hospitals that require clinical-adjacent workflows to run inside hospital-controlled infrastructure.. SCRIMED can be positioned as an intelligence sidecar that respects the hospital record of truth and does not mutate clinical systems without approval.
High-value enterprise operating license for multi-department workflow ownership.
- Environment: Hospital-controlled runtime with local policy, identity, audit, and clinical-review ownership.
- Cost model: Enterprise license plus department workflow modules, integration services, and clinical governance support.
- Data posture: Hospital-controlled data boundary; live PHI cannot leave approved environment.
- Blocked claims: clinical decision support authorized, EHR writeback enabled, patient treatment automation
external-approval-required
Sovereign Cloud And Public Sector Profile
Governments, ministries of health, national programs, and public-sector healthcare agencies.. SCRIMED can support public-sector evaluation as a synthetic, jurisdiction-aware healthcare intelligence fabric before any live data movement.
Strategic platform partnership and multi-year public-sector transformation program.
- Environment: Government or sovereign-cloud profile with jurisdiction-specific residency, procurement, and incident ownership.
- Cost model: Multi-year strategic agreement with jurisdictional customization, regional support, and governance reporting.
- Data posture: Jurisdiction-defined; cross-border transfer denied until reviewed and approved.
- Blocked claims: sovereign compliant, government approved, public health reporting authorized
external-approval-required
Edge And On-Prem Evaluation Profile
Hospitals, imaging groups, labs, and device-heavy environments evaluating edge or on-prem constraints.. SCRIMED should be ready for medical-device and facility-adjacent intelligence without controlling devices, making diagnoses, or operating equipment.
Premium device, imaging, lab, and facility integration module after synthetic proof.
- Environment: Edge or on-prem runtime planning for imaging, device, lab, and facility-signal workflows using synthetic fixtures first.
- Cost model: Platform module plus device/integration implementation, support, monitoring, and safety review.
- Data posture: Local-first where customer requires; external transfer denied until approved.
- Blocked claims: device control, diagnostic imaging interpretation, medical-device cleared, real-time clinical automation
Metrics
Deployment readiness is measured as pilot evidence, not as unsupported production certification.
Cost per synthetic work order
Measured during pilot
- Agent Workspace work-order outcome metrics and proof packets.
- Directional pilot metric; not a guaranteed production price.
Review latency
Buyer-approved workflow target
- Work-order event timeline and reviewer checkpoints.
- Human review remains required for clinical-adjacent outputs.
Evidence completeness
Trust Card, source attribution, reviewer status, and blocked actions attached
- Pilot proof packet and TrustOS decision ledger.
- Evidence completeness is not clinical correctness certification.
Deployment portability
Architecture map approved before build
- Deployment profile packet and customer security checklist.
- Architecture readiness is not deployment approval.
Connector readiness
Synthetic fixture pass before live connector work
- Integration fixture validation and conformance evaluations.
- Synthetic conformance does not imply EHR vendor certification.
No-writeback assurance
All synthetic workflows blocked from EHR mutation
- Denied execution audit and connector contracts.
- No-writeback proof is a pilot control, not vendor certification.
Reviewer coverage
Every clinical-adjacent recommendation has reviewer status
- TrustOS reviewer events and proof packets.
- Reviewer coverage does not make output medical advice.
Sovereign readiness
Jurisdiction, residency, retention, and incident owner mapped
- Public Sector Sovereign Retention Pack and deployment profile.
- Mapping is not government approval.
Public-sector proof completeness
Governance gates, blocked claims, and procurement route visible
- Activation governance and enterprise readiness packets.
- Proof packet is not legal or procurement authorization.
Device fixture coverage
Monitor, lab, DICOM, and facility scenarios mapped before live data
- Synthetic fixture contracts and integration validation.
- Fixture coverage does not authorize device control.
Edge safety posture
All device-control and diagnostic actions blocked
- Runtime safety readiness and denied execution audit.
- Safety posture is a development gate, not medical-device clearance.