Search all 478 artefacts by title, document ID or content.
Disclosure | Family 3, Security, Privacy & Trust Disclosures
Applies to DM-1, DM-2, DM-3 and DM-4 identically. The same application code and the same standards support ship in all four models.
This document is the source of truth for: standards-conformance-position, terminology-version-register, export-format-definitions, dicom-hl7-position, rfp-interoperability-answer, marketing:/product/interoperability
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.
Applies to DM-1, DM-2, DM-3 and DM-4 identically. The same application code and the same standards
support ship in all four models.
To state which standards Pensieve implements, at which version, where it conforms and where it
does not, and which licences the terminologies require. A hospital's IT head uses this to answer two
questions: can our other systems talk to it? and if we leave, can we take our data somewhere useful?
The second question is answered operationally in DIS-GL-023; the formats are defined here.
A standard named without a version and a conformance statement is a marketing claim. Every row below
carries both, or carries [TO BE SUPPLIED].
| Standard | Version | Where it is used | Conformance status |
|---|---|---|---|
| HL7 FHIR | R4 | The primary clinical data representation: patient, encounter, condition, observation, medication request and administration, diagnostic report, document reference, allergy, procedure, coverage and claim resources. Used for record export, for the national digital health integrations, and for hospital-to-hospital exchange | Implemented. A resource-by-resource FHIR Capability Statement is published at https://trust.pensievelabs.org ([TO BE SUPPLIED]) |
| HL7 v2 | v2.x, negotiated per interface | The working standard for laboratory analysers, middleware and many existing hospital systems in Pensieve Labs's markets. ADT, ORM, ORU and MDM message types |
Implemented per interface. An interface specification is issued per integration, because HL7 v2 conformance is always a bilateral negotiation, never a certificate |
| ASTM | As the device requires | Older laboratory analysers that predate HL7 support | Implemented per device |
| DICOM | PS3.0 | Imaging: storage, query/retrieve, worklist, and non-diagnostic display. No image analysis: DIS-GL-028 Section 7.1 |
Implemented. A DICOM Conformance Statement naming supported SOP classes, transfer syntaxes and roles is published: [TO BE SUPPLIED] |
| PDF/A-2 | Not applicable | Archived documents and generated reports | Implemented |
| JPEG | Not applicable | Scanned documents | Implemented |
On HL7 v2 and DICOM interfaces, stated honestly. Neither is a plug-and-play standard in practice. Every
analyser, middleware product and imaging archive implements a dialect, and every integration requires a
negotiated interface specification, a test plan and a period of message-level debugging with the other
vendor. Pensieve Labs budgets for this in the onboarding plan rather than discovering it. The
integration boundary (who owns which side, and what happens when the other vendor is slow) is
DIS-GL-024.
| System | Version / release | Use in Pensieve |
Licence position |
|---|---|---|---|
| SNOMED CT | International Release [TO BE SUPPLIED], plus the India Extension where applicable |
The primary clinical encoding system: problems, procedures, findings, substances, nursing and dental content, and the codes used when communicating clinical information to other record systems | An Affiliate Licence is required. India is a Member country of SNOMED International, so the Affiliate Licence is free in India and is issued through the National Release Centre operated by C-DAC Pune (NRCeS). Licence status: [TO BE SUPPLIED]. Free does not mean unlicensed: using SNOMED CT content in a commercial product without an Affiliate Licence is an intellectual property violation, and a hospital or an assessor can and should ask to see the licence |
| LOINC | [TO BE SUPPLIED] |
Laboratory tests, measurements and observations; result and report processing with laboratory and imaging systems | Free under the Regenstrief LOINC licence, with registration. Registration status: [TO BE SUPPLIED] |
| ICD-10 | [TO BE SUPPLIED] |
Diagnosis classification, statistical reporting, and the classification named in the Indian EHR standards | Free from the World Health Organization |
| ICD-11 | Not applicable | Mapping layer only. Pensieve implements ICD-10 as the mandated classification with an ICD-11 mapping layer, because the Indian EHR standards name ICD-10 and the national transition path is not settled. [UNVERIFIED: India's ICD-11 transition timetable and whether a revised EHR standards edition has been issued could not be confirmed] |
Free from the WHO |
| ICD-O, ICF, ICHI | Not applicable | Where a hospital's service line requires them | Free from the WHO |
| Hospital-local code systems: tariffs, packages, formulary, service catalogue | Hospital's own | Configured per hospital | Hospital's |
The versions above are maintained in a dated version register published on the Trust Center and
reviewed quarterly. A terminology release that has moved on without the register moving is a defect, and
the register's date makes it visible. Register status: [TO BE SUPPLIED].
Why this matters to a hospital more than it sounds. A record coded against a superseded SNOMED CT release still exports correctly, but a receiving system on a newer release may reject or misinterpret a retired concept. The register is what lets a receiving system's implementer plan for that.
| Market | Standard | Position |
|---|---|---|
| India | EHR Standards for India 2016, notified by the Ministry of Health and Family Welfare and maintained by NRCeS | Pensieve implements the named terminology, exchange, imaging and security standards. There is no conformance certification scheme for these standards: no body issues a certified mark. Evidence is therefore a clause-by-clause Conformance Statement, self-attested and signed. Status: [TO BE SUPPLIED] |
| India | ABDM FHIR implementation guide | Implemented for the integrations the hospital enables, on the hospital's own credentials. Edsol Edtech Pvt. Ltd. holds no ABDM milestone certification and does not seek it (DIS-GL-024 Section 3) |
| India | National health claims exchange profiles | Implemented on the hospital's own participant credentials. Pensieve Labs does not onboard in its own name (DIS-GL-024 Section 4) |
| Australia | My Health Record | Not implemented. DIS-GL-008 Section 5.2 states why, and it is a support-model constraint rather than a technical one |
| Denmark, Norway | European Health Data Space electronic health record system requirements | The regime is a manufacturer's declaration of conformity with technical documentation, on the Regulation's statutory timetable. Pensieve Labs intends to meet it on that timetable and does not claim conformity today. DIS-GL-028 Section 3.3 |
| UAE | Health information exchange participation and its implementation guide, which is FHIR-based | Not implemented. Three separate exchanges, one claims platform and a vendor-level assessment Edsol Edtech Pvt. Ltd. does not hold. The full position, including the two-gate structure and the onboarding stages, is DIS-AE-029 |
Defined here; the process, timelines and fees are in DIS-GL-023.
| Data | Format | Notes |
|---|---|---|
| Clinical records | HL7 FHIR R4 resource bundles | The primary clinical export. Coded content carries the code system and version it was coded against |
| Everything, structurally | CSV and JSONL table extracts | For teams without a FHIR consumer, which in Pensieve Labs's markets is most of them. This is the format that is actually used |
| Images | DICOM, original form | With study and series metadata |
| Documents and reports | Original files, plus PDF/A-2 for generated documents | With a manifest mapping each file to patient, encounter and document type |
| Audit trail | JSONL | Access, amendments with prior values, disclosures, administrative changes |
| Master and configuration data | CSV / JSONL | Tariffs, formulary, service catalogue, users, roles, forms and templates with versions and effective dates |
| Data dictionary | Markdown and CSV | Every file, every column, every code system, every identifier. An export without one is not portability |
What Pensieve connects to, on whose credentials, and who is responsible when it breaks, is
DIS-GL-024. It is not restated here. Two points that belong to this document:
Pensieve calls external systems as the hospital, on the hospital's own authority, using
credentials the hospital supplies. See DIS-GL-025.Pensieve Labs issues an interface
specification per integration for exactly this reason.6.1 No certification of standards conformance exists or is held. There is no certified mark for the
Indian EHR standards, Pensieve Labs holds no ABDM milestone certification, and no third party has
verified the conformance claims in this document. Evidence is self-attested conformance statements plus the
falsifiable artefacts (the FHIR capability statement and the DICOM conformance statement), which any
integrator can test against.
6.2 Several status fields are [TO BE SUPPLIED]. The SNOMED CT Affiliate Licence, the LOINC
registration, the published capability and conformance statements and the version register are named with
their status unsupplied rather than asserted. The SNOMED CT licence in particular is free, slow and
blocking (the worst combination to discover during a deal) and its status should be confirmed before a
hospital relies on SNOMED CT coding.
6.3 HL7 v2 and DICOM conformance is per-interface. Section 1. Pensieve Labs does not claim that any HL7 v2
or DICOM interface works without a negotiated specification and a test cycle, because none does.
6.4 Legacy device protocols may predate transport security. Where an analyser or imaging node cannot
offer TLS, the connection is confined to the hospital's own network segment and recorded in the deployment
record (DIS-GL-011 Section 7.2).
6.5 Pensieve does not interpret coded data clinically. It stores, exchanges and displays it.
Any inference from a code is the clinician's (DIS-GL-028).
6.6 ICD-11 is a mapping layer, not a native classification. Section 2.
6.7 My Health Record and the European declaration of conformity are not implemented today. Section 3.
| Question | Document |
|---|---|
What Pensieve integrates with, on whose authority, and who fixes what |
DIS-GL-024 Integration Boundary Statement |
| How the hospital's credentials for those systems are held | DIS-GL-025 |
| Export process, timelines, fees and the Certificate of Deletion | DIS-GL-023 Data Deletion & Return Disclosure |
Why Pensieve does not interpret clinical data |
DIS-GL-028 Clinical Safety Boundary Statement |
| The audit trail that accompanies exchanged records | DIS-GL-013 |
| Data residency for exchanged data | DIS-GL-008 |
| Version | Date | Author | Summary |
|---|---|---|---|
| 1.0.0 | 31 July 2026 |
Pensieve Labs Engineering |
First published edition. Standards named with versions and conformance status. SNOMED CT licensing position published as a gating item. Export formats defined. Unsupplied statuses marked rather than asserted. |