#EHDS Readiness Statement

STM-EU-001 v1.0.0, Last Modified On 01 August 2026, Tier: Public

A hospital buying an operating system in 01 August 2026 is buying a system that will still be running when EHR-system conformity becomes a legal obligation. This statement says what Pensieve Labs has built, what it has not, and the date by which it will declare. It claims no conformity that does not yet exist, because none does: the obligations have not yet attached to anybody.

---

#Applicability

Conformity under the EHDS Regulation attaches to the EHR system as placed on the market, not to the hosting arrangement. The analysis is the same in all four deployment models. Where a hospital self-develops or deeply modifies, Section 10 applies.

---

#1. Why this is the most important European document Pensieve Labs publishes

Edsol Edtech Pvt. Ltd. holds no certifications. In every other regulatory conversation that is a handicap to be compensated for. Under the EHDS Regulation it is not a handicap at all, because nobody holds a third-party certificate: the regime is built on the manufacturer's own declaration.

That makes EHDS the one European regime in which an uncertified vendor starts level with an incumbent, and the barrier is engineering and documentation, both of which Pensieve Labs controls, on a calendar Pensieve Labs can see. The payoff is disproportionate: one EU declaration of conformity makes the Platform sellable as an EHR system across the internal market.

A vendor that publishes a dated 2029 roadmap in 01 August 2026 is also making a claim it cannot retract: that it intends to exist in 2029 and expects to be measured against this page.

---

#2. What the Regulation does

Regulation (EU) 2025/327 establishing the European Health Data Space entered into force on 26 March 2025. It is a Regulation, so it applies directly in every Member State without transposition, and it extends to the EEA States on incorporation into the EEA Agreement.

Its Chapter III creates, for the first time, a conformity regime for EHR systems placed on the internal market. The obligations on a manufacturer are:

Item 5 is the structural fact. For the ordinary EHR system there is no notified body, no third-party audit and no certification fee. Conformity is declared by the manufacturer on the strength of the technical documentation file and the testing.

This is not a loophole and Pensieve Labs does not present it as one. A false declaration exposes the manufacturer to market surveillance, corrective action, withdrawal and penalties. The point is only that the gate is competence, not procurement of a certificate, which is the gate an engineering-led company can pass.

---

#3. The dates, resolved

Secondary commentary on EHDS has been unreliable. The dates below are from Article 105 of the Regulation and Pensieve Labs states them precisely because a wrong date in a tender response is a credibility loss that is hard to recover.

Two corrections Pensieve Labs makes when it hears them:

1. "EHR systems had to be certified from January 2026." This is circulating in secondary sources and is wrong. No Chapter III obligation applied in 2026.
2. "EHDS requires a notified body." For the ordinary EHR system it does not. Conformity is self-declared.

The specifications Pensieve Labs must actually build to do not exist yet. They arrive as Commission implementing acts after the general application date. Building the shape now and the specifics after adoption is the only rational sequence; over-building against a guess is waste.

---

#4. Pensieve Labs's position today, stated without overreach

As at 01 August 2026:

• Edsol Edtech Pvt. Ltd. holds no EU declaration of conformity for an EHR system.
• It has not registered any system in the EU database.
• It affixes no conformity marking and no CE marking of any kind.
• It has not tested in a European testing environment, because the environment and the specifications it would test against are not yet in place.
• No obligation to do any of these things has yet crystallised, for Pensieve Labs or for any other manufacturer.

Anything else stated in a sales conversation is wrong and should be reported to info@pensievelabs.org under POL-GL-059.

---

#5. Readiness by component

Status codes: Built (in production). Designed (architecture settled, implementation scheduled). Shaped: the requirement is understood and the substrate is being built so it can be met without re-architecture. Not started.

---

#6. The logging component: the decision that cannot be deferred

Of everything in Section 5, item 4 is the one with a closing window.

The Regulation requires machine-readable logging of access to electronic health data. Retrofitting a complete, tamper-evident, exportable access log into a hospital operating system that is already live in production hospitals is a major programme: every read path must be instrumented, every historical gap must be explained, and the hospitals themselves must be migrated. Building it into the substrate before the first European deployment is a sprint.

Pensieve Labs therefore builds the logging capability now, ahead of and independently of any European deal, on the following design commitments:

DIS-GL-013 is the operative disclosure and the source of truth for how logging works. This statement adds only the EHDS-specific commitments.

---

#7. Roadmap, with dates

Dates are Pensieve Labs's own planning targets, not regulatory deadlines. They are published so that they can be checked against.

Named owner: the role recorded at Roadmap ehds owner. This is a role with a standing agenda item, not a task on a list. Where the token is unresolved the obligation is unassigned, and a hospital is entitled to say so.

---

#8. What Pensieve Labs commits to contractually

MSA-EU-001 clause 6 makes the following binding, and this statement is incorporated into it:

1. maintain the technical documentation file and make its index available on request;
2. design and operate access logging so that it can satisfy the European logging component without a re-architecture, and make it exportable to the hospital in machine-readable form;
3. inform the hospital within 60 days of the adoption of a relevant implementing act, of the effect on the Platform and on the hospital's own obligations;
4. keep this statement current and dated at https://trust.pensievelabs.org; and
5. where the Order Form records that the deployment processes Priority Category 1 or Priority Category 2 data, complete conformity for that category before the applicable date at no additional charge, or give not less than twelve months' notice and the right to terminate the affected services without penalty and with exit assistance.

Commitment 5 is the one that matters commercially. It converts an uncertain 2029 obligation into a dated contractual right the hospital can put in its own risk register.

---

#9. What this statement does not claim

---

#10. Scope questions a hospital should ask

10.1 Is the Platform an "EHR system"? On its intended purpose, a system by which health data is recorded, stored and shared for the provision of health care: yes, in substance, and Pensieve Labs plans on that basis rather than looking for a definitional escape. A vendor that argues its hospital system is not an EHR system in order to avoid Chapter III is storing up a market-surveillance problem.

10.2 Which priority category is in scope for my deployment? Whichever the Order Form records. A deployment that does not process patient summary, ePrescription or eDispensation data has no 2029 exposure; one that adds them later triggers a Change Order and the commitment in Section 8.5.

10.3 What happens if the hospital modifies the system substantially? A person who makes a substantial modification to an EHR system placed on the market may assume the manufacturer's obligations for it. Where a hospital builds substantially inside the Platform, the boundary in DIS-EU-028 Section 9 applies by analogy and the Parties record the allocation in a Change Order.

10.4 What about wellness applications? The Regulation carries a separate, lighter regime for wellness applications claiming interoperability with an EHR system. Pensieve Labs publishes no wellness application and makes no interoperability claim of that kind.

---

#11. Interaction with other European regimes

---

#12. Limitations

12.1 The Regulation is new and its implementing acts are not adopted. Everything in Section 5 items 3, 4, 7, 8 and 9 is planned against a specification that does not yet exist. Estimates will move.

12.2 EEA incorporation. Application in EEA States that are not Member States follows incorporation into the EEA Agreement, which has its own timetable. Pensieve Labs does not state a date for it and the Norway delta pack records the position.

12.3 No competent authority has reviewed this statement. It is Pensieve Labs's own reasoned position.

12.4 Cost. The engineering and documentation effort for the interoperability and logging components plus the technical file is material but not certification-scale, and there is no notified-body fee in the ordinary case. [The current internal estimate is held in the Trust Center roadmap and is not published, because publishing a cost estimate invites it to be read as a price.]

---

#13. Related documents

---

#14. Signature

---

#15. Change history