Implementation Pilots
Prove the pipeline on your records.
There is no open, shared way of turning decades of clinical correspondence into structured, coded, source-traceable history. This is a working implementation of one, and it is ready to be validated in the real world. I am looking to partner with health organisations to deploy bounded, fixed-scope pilots that run the framework against their own legacy data.
The proposition
A bounded deployment inside your infrastructure.
An implementation pilot is designed to prove clinical value quickly without disrupting your existing systems of record. We define a targeted set of records (e.g., 500 historical discharge summaries), deploy the framework within your governed environment, and tune the extraction and SNOMED CT resolution to your specific clinical specialty.
What you bring
- A real deployment inside your own governed environment
- Real records — correspondence, discharge summaries, reports
- A defined clinical problem (e.g., registry abstraction, complex triage)
- One named technical or clinical informatics lead
- Your own clinical, privacy and regulatory governance
What you get
- A fully operational pipeline transforming text to structured data
- The full framework under PolyForm Internal Use 1.0.0
- Direct architectural integration and deployment support
- Custom terminology mapping for your local data
- A visual, auditable interface for your clinicians or data team
- A low-risk, measurable proof of concept to present to leadership
Pilot Focus Areas
Where we can drive immediate value.
These are the specific domains where the framework is ready to be tested and hardened in partnership with your clinical team.
How it starts
A conversation, then a scoped proposal.
Use the form to outline your organisation, your timeline, and the specific records you want to structure. Every field is listed here if you want to see it first.
I reply personally. We work out whether your use case and the framework are a fit, and discuss structuring the engagement as an internal evaluation or a scoped consulting pilot.
The framework is deployed inside your infrastructure, against your records, under your governance. No patient data ever leaves your environment.
We present the working visual interface and structured data output back to your clinical governance board to evaluate broader integration.
Being straight with you
What you would be deploying.
This is a working, functional implementation. The pilot phase is designed to de-risk your adoption.
The core framework and architecture are settled, but every hospital writes differently. The pilot process exists specifically to validate the extraction and terminology mapping against the idiosyncrasies of your local clinical records before you commit to a wider rollout.
The software licence (PolyForm Internal Use 1.0.0) is perpetual and irrevocable for the version you receive, meaning nothing you deploy internally can be taken away from you.
Want the detail first?
What the form asks, what the licence says, and what you need in place before you deploy.