Runbook | Family 7, Runbooks

Hypercare Runbook: Day 1 to Day 30

RBK-GL-015v1.0.0ClientRunbookGL1234S10 Hypercare

Hypercare is not part of the fourteen-day clock and is not hidden. The clocks stop at cash and at the first live patient registration. Hypercare is a 30 to 45 day tail regardless of how fast the go-live was. It is stated on day zero, priced, and sold as a feature. Conflating it with the fourteen days is the quickest…

Permalink trust.pensievelabs.org/documents/RBK-GL-015

Classification

ClientClient credential required

The five axes

Kind: Runbook
Tier: Client credential required
Direction: Bilateral
Lifecycle: S10 Hypercare
State: Published templateTokens resolve live. An issued instance freezes its render, its token values and its hash.

Record

Doc ID: RBK-GL-015
Version: v1.0.0
Last modified: 31 July 2026
Review due: 31 July 2027
Owner: Customer Success
Family: 7. Runbooks
Language: en-IN
Retention: 8 years after the record closes

Execution

Signature: No signature
Stamp duty: No stamping required
Letterhead: standard

Applicability

Jurisdiction: Global (GL)
Applies to: 1234Dedicated, Shared, Customer Cloud, On-Premise
Lane: Enablement
Exit gate: Hypercare exit certificate signed
Critical path: Not on the critical path

Integrity

Length: 3,328 words
SHA-256: 7138D6E9293E7138d6e9293e4a7b7c2ffb50ff0eef3073712ef22c03d2fa7e434ae8bc427a3e

No-repetition rule

This document is the source of truth for: hypercare-taper-schedule, hypercare-exit-criteria, hypercare-handover-point

Those surfaces render this text from here. They do not keep their own copy, so they cannot drift from it.

Depends on

Artefacts this one references or cannot be issued without.

Referenced by

Artefacts that would be blocked if this one were missing or out of date.

Client credential required

This belongs to a specific hospital's workspace. Sign in with your workspace credential to read it.

Where you are

PublicCleared
EmailNot cleared
NDANot cleared
ClientRequired for this document

What this page did not send you

The body of RBK-GL-015 was not rendered and was not transmitted to your browser. Everything you can see here (the classification, the summary, the dependency graph, the integrity hash) is register metadata, and it is published deliberately. Knowing that a document exists is not the same as reading it, and hiding the title only makes you send an email.

Available to you right now, without clearing anything

Nothing else in this family is open at your current level. The public tier is the place to start: it holds the security whitepaper, the architecture overview, the standard DPA, the SLA and the sub-processor register.