Every document this project has produced, the method first. Nothing here requires a key, a form or an account. Each entry says who it is for. Page counts are read from the files themselves rather than typed, so they cannot drift out of date. What changed, and when.
This is the point of the site. Everything else here exists to show the method survives contact with a real record and a real device. Start with the plain-language walkthrough if you do not work in health IT.
Published capability statements say what a server supports. They do not say what it will give you. Those are different questions and only one can be answered by reading documentation.
Why the record of what a device did is unreconstructable, and the endpoint built to test whether anyone will fix it.
These are running now and answer without a key. They are generated by the deployed code, so they always describe what is actually running rather than what the documentation claims.
| Endpoint | What it tells you |
|---|---|
| /device | Device sandbox capability statement |
| /device/health | Device sandbox liveness |
| /cds-services | CDS Hooks service discovery |
| /cds-health | CDS Hooks liveness |
facts.json The vendor findings as structured data, which is the same file the datasheet and the evidence page both read from, so the three cannot disagree.
Daniel Pettus spent forty years in medical device and health IT leadership at Alaris, CareFusion and BD, contributed to IHE Patient Care Device interoperability standards, and is named on two United States patents. He writes Inside the Loop at insidetheloopdp.substack.com and is the author of The Technology Was Never the Problem, at pettusbook.com.
AI MedAgent is a research demonstration of a patent-pending method. Advisory only. Not a medical device. Not for clinical use. Synthetic data only.