Search all 478 artefacts by title, document ID or content.
Disclosure | Family 3, Security, Privacy & Trust Disclosures
Foundation is content, not a build variant. The same baseline instantiates into all four deployment models.
This document is the source of truth for: foundation-coverage-boundary, foundation-exclusions
Those surfaces render this text from here. They do not keep their own copy, so they cannot drift from it.
Artefacts this one references or cannot be issued without.
Artefacts that would be blocked if this one were missing or out of date.
IN-100 Coverage StatementDIS-GL-035 v1.0.0 | Last Modified On 01 August 2026 | Tier: Public | Foundation release Foundation release tag
| DM-1 | DM-2 | DM-3 | DM-4 |
|---|---|---|---|
| Yes | Yes | Yes | (same content; longer instantiation, see Section 6) |
Foundation is content, not a build variant. The same baseline instantiates into all four deployment models.
Pensieve Foundation IN-100 is a maintained, versioned, pre-built tenant baseline for a
50 to 200 bed Indian multi-specialty private hospital. It exists so that an implementation is adoption of a
working configuration, not construction of one.
This statement says what that baseline covers, and, at greater length, what it does not. The second half is the reason the first half is believable. A hospital that discovers an exclusion in week two of an implementation stops trusting everything else it was told; a hospital that read the exclusion before signing plans around it.
Read Section 3 before Section 2.
Status. Foundation
IN-100is released and versioned asFoundation release tag, datedFoundation release date. Where a release has not yet shipped a block below, the block is markedNOT YET RELEASEDinREG-IN-600and this statement carries that state. Nothing on this page describes a capability that has not shipped in the named release.
The same Platform every customer runs, pre-loaded with Indian hospital content: a facility and ward skeleton, a structured service catalogue with empty rate cells, a pharmacy item seed, a laboratory test seed with reference ranges, an imaging catalogue, a pre-built role and permission set, statutory print formats, a standard report pack, a payer pack, and the deployment blueprint. It is not a cut-down edition, a trial, or a template that must be "developed". It is the content layer, versioned and released on a fixed cadence, and every tenant receives updates without a per-tenant migration.
The block-by-block contents and the adoption procedure are in RBK-GL-007 Section 2. The object-level inventory,
with version and release state per object, is REG-IN-600. Neither is restated here.
| # | Block | Covered by Foundation | The hospital still supplies |
|---|---|---|---|
| 1 | Organisation & facility skeleton | Ward and bed-class taxonomy, theatre and critical-care structures, standard department list | Which of them they actually have, and local names |
| 2 | Tariff skeleton | Service catalogue structure and a class-multiplier framework, rate cells empty | The headline rates and the multiplier ladder: a decision, not data |
| 3 | Pharmacy item seed | Commonly stocked Indian formulations with molecule, pack, schedule flag, tax classification and reorder default | Items they stock that are not in the seed |
| 4 | Laboratory test seed | Routine tests with sample type, method, turnaround and reference ranges by age and sex, plus standard profiles | Ranges that differ from their own analyser inserts; outsourced tests and the partner laboratory |
| 5 | Radiology & imaging catalogue | Modality taxonomy, procedure lists, report templates for common studies | Which modalities exist, and the device identities |
| 6 | Roles, permissions and screens | Pre-built roles with a permission matrix and a landing screen each | The mapping of staff names onto roles |
| 7 | Statutory print formats | The statutory invoice, register, voucher, summary and consent formats an Indian hospital is inspected on | Letterhead, logo, address, tax identifiers and licence numbers, merged from scans |
| 8 | Report pack | Operational, financial, clinical-administrative and accreditation-evidence reports | Nothing before go-live |
| 9 | Payer pack | Scheme package masters, reference rates, pre-authorisation and claim layouts, cashless workflow | Which payers they are empanelled with, and their agreed rates |
| 10 | Deployment blueprint | Infrastructure-as-code, backup schedule, nightly customer-held export | Nothing in DM-1/DM-2. See WPR-GL-004 for DM-3/DM-4 |
Six things always require hospital input and nothing else should: tariff rate cells, unmatched pharmacy items, differing laboratory reference ranges, the clinician list with registration numbers and payout terms, empanelled payers and their rates, and the print-format identity merge.
This is the section that matters. Each exclusion below is a statement of fact about the released baseline, not a roadmap commitment.
| # | Not covered | Why | What happens instead |
|---|---|---|---|
| E1 | Rate values in the tariff | Rates are a commercial decision belonging to the hospital's owner and billing head. No vendor may supply them | Adjudicated in a scheduled owner session and recorded in FRM-GL-020 |
| E2 | Speciality-specific clinical content beyond general multi-specialty: oncology protocol regimens, IVF cycle management, transplant workflows, dialysis scheduling packs, psychiatric assessment instruments | The baseline is scoped to a 50 to 200 bed general multi-specialty hospital | Scoped separately. Never assumed to be wave 1 |
| E3 | Single-speciality hospital baselines: standalone eye, dental, maternity, orthopaedic or cardiac-only facilities | Their catalogues and workflows differ structurally, not marginally | Assessed at qualification. Foundation-fit is scored in FRM-GL-001 |
| E4 | Payroll, human-resources administration and statutory labour returns | Adjacent domain, separately regulated, and not on the go-live critical path | Out of wave 1 by default |
| E5 | Financial accounting, ledgers and statutory tax return preparation | Pensieve produces the operational and outward tax registers; it is not the books of account |
Exported to the hospital's accounting system |
| E6 | Blood bank component preparation and cross-match laboratory workflow beyond the issue register | Specialised and separately licensed | Scoped separately |
| E7 | Biomedical equipment maintenance management | Adjacent domain | Scoped separately |
| E8 | Non-Indian statutory print formats, registers and tax structures | IN-100 is the India baseline |
Other markets take their own baseline. See WPR-GL-004 |
Foundation ships the catalogue and the interface capability, not a live connection. Every live connection depends on a third party and on credentials the hospital holds.
| # | Not covered by the baseline | What is required |
|---|---|---|
| E9 | Laboratory analyser interfaces | Per-device commissioning. Make, model and protocol captured in FRM-GL-111; run under RBK-GL-009 |
| E10 | PACS / DICOM connections | Per-modality commissioning. FRM-GL-112 |
| E11 | Payment gateway, SMS, WhatsApp and e-mail delivery | The hospital's own credentials under the BYOK/BYOC model. DIS-GL-025, FRM-GL-119 |
| E12 | ABDM, NHCX, insurer and administrator portals | The hospital's own credentials and its own registrations. Pensieve Labs is not the regulated participant (DIS-GL-024, DIS-GL-026) |
| E13 | Biometric attendance, queue displays, CCTV and other estate systems | Assessed per site. FRM-GL-113 |
None of these is a gap in Foundation. They are boundaries stated in DIS-GL-024 and priced in the
Statement of Work.
| # | Not covered | Position |
|---|---|---|
| E14 | Diagnosis, treatment recommendation, dosing decisions or triage decisions | Pensieve is not a medical device and is not offered as one. DIS-GL-028 is binding and this baseline does not contain content that would contradict it |
| E15 | Legal or regulatory advice on the hospital's own licensing, accreditation or tax obligations | The formats are supplied; the obligations remain the hospital's |
| Rule | Statement |
|---|---|
| Pinning | Every tenant is instantiated from a named Foundation release tag, recorded on the deal. "Latest" makes a tenant unreproducible and the deviation ratio unmeasurable |
| Cadence | Foundation is released on a fixed cadence. This statement is re-issued with each release |
| Update path | Tenants receive Foundation updates without a per-tenant migration. A tenant carrying FORK deviations is the exception and knows it (REG-GL-214 Section 4) |
| Object inventory | REG-IN-600 holds every Foundation object with its release state. This statement holds the boundary |
Nothing is refused verbally and nothing is agreed on site.
REG-GL-214) in the requester's own
words, at the moment it is made.ADD-GL-015) with a
price, or it is declined in writing and the decline is acknowledged.Deviation volume is measured. Open deviations above roughly one quarter of configured objects means the hospital is commissioning a build rather than adopting a platform. That is a legitimate thing to want; it is priced and scheduled as one, openly, rather than discovered at go-live.
Foundation instantiates into a new tenant in under one hour. Nothing in this statement changes.
Foundation release tag only. An older or newer release has its own
statement.Pensieve Labs supplies the seed;
the hospital owns the clinical and fiscal correctness of what it operates on.DIS-GL-030, SLA-GL-001 and WPR-GL-001.NOT YET RELEASED in REG-IN-600, it is not covered, whatever this summary
implies.| Doc | What it holds |
|---|---|
REG-IN-600 |
The object-level Foundation inventory and release state |
RBK-GL-007 Section 2 |
Block-by-block contents and the adoption procedure |
REG-GL-214 |
The container for every request outside coverage |
DIS-GL-036 |
Minimum viable go-live configuration: the infrastructure counterpart of this statement |
DIS-GL-024, DIS-GL-026 |
Integration boundary and the ABDM/NHCX responsibility matrix |
DIS-GL-028 |
Clinical Safety Boundary Statement, binding on all Foundation content |
WPR-GL-004 |
Deployment models |
ADD-GL-015 |
Change Order, for requests outside the Statement of Work |
| Version | Date | Author | Summary |
|---|---|---|---|
| 1.0.0 | 01 August 2026 |
Platform | First issue, for Foundation release Foundation release tag. |