A deployment that respects your clinical model.
How Peacefull lands inside the technical and clinical operations you already run. SSO, role gating, governance committee, data posture. Written for the people on your team who have to integrate it, not sell it.
Three conversations, covered.
Your clinicians, your scope.
Role-gated access for clinician, supervisor, admin, and compliance. MFA mandatory. Patient assignment mirrors your practice management system. SSO via SAML or OIDC; user lifecycle via SCIM.
Your governance.
A clinical governance committee (CGC) reviews every model update before it reaches patients. You seat the committee. We publish the meeting minutes. Quarterly alignment sessions with our clinical lead.
Your data posture.
BAA at no additional cost. Zero advertising partners. Row-level security on every query. 42 CFR Part 2 handling for substance-use populations. Custom data residency on request.
Clinicians govern the model.
Every model release passes a 7-gate lifecycle. This queue shows what's waiting for your signature and what's moving.
Lower the Sunday-night escalation threshold to 0.68.
Companion currently escalates at ISS 0.70 across all time-of-day windows. Post-deployment monitoring of 847 supervised cases shows false-negatives cluster between 9pm–1am Sunday. This change drops the Sunday-night window to 0.68. No change to other windows.
Identity & access, in your source of truth.
SSO mirrors your IdP. Role policy mirrors your practice hierarchy. SCIM keeps user lifecycle aligned with your HR system. Everything about identity is read from where you already run it — Peacefull does not become another shadow directory.
Your clinicians, your scope.
SSO mirrors your IdP, role gates mirror your practice hierarchy, lifecycle events come in via SCIM. You keep the source of truth.
Every event, streamable.
A tamper-evident log of every PHI access, every model decision, every escalation, every admin change. Stream to your SIEM (Splunk, Datadog) or your compliance data lake (S3, BigQuery). Chain-verified via SHA-256 with hourly Merkle root rotation.
Every access, every decision, streamable.
A tamper-evident event log of every PHI access, every safety decision, every escalation. Stream to your SIEM, your compliance data lake, or your S3 bucket. Retention mirrors your policy.
BETA-1. Honest about it.
We have no published patient-outcome evidence yet, and we decline to invent any. What we do have is a deployable safety architecture, a pre-registered research program, and a public model card that changes with the product — so your clinical leadership and procurement teams can evaluate us on what is real.
Six-layer safety evaluation.
Document adherence, instruction adherence, named failure modes, tone and modality fidelity, independent clinical review, and bias & equity — every layer gates every release. Details in the model card.
Deterministic escalation.
Crisis hand-off runs on rule-based signals, audit-logged line by line — not on model judgment. 988, 741741, and clinician contact are surfaced as one-tap actions, not paragraph mentions.
Research program, pre-registered.
OBS-90, hybrid effectiveness-implementation, and a micro-randomized trial of decision points — analysis plans deposited in advance, null results committed to publication. See the research program.
FDA PCCP structure.
We follow the structure of an FDA Predetermined Change Control Plan — not because we are under authorization today, but because we intend to pursue it. Every model, prompt, and knowledge-base change is versioned and gated.
The commercial side — unlocks, contracts, sign-off.
White-labeling, multi-site, audit-log export API, and the contract template you actually run — in the companion procurement page.