
A breakdown of what the Toolkit does and how each capability fits into a typical openEHR project workflow.
Upload and manage openEHR archetypes and operational templates in one place. Artifacts are versioned using semantic versioning so you can track changes over time. Share them across teams via the REST API.
Generate clinical document instances from any operational template, with randomly populated data. Output is available in both XML and JSON. Useful for testing openEHR servers, validating data pipelines, and demonstrating template structures.
See the full archetype tree behind any operational template. Understand which archetypes are included, at which paths, and with which constraints. Useful for data mapping and integration planning.
Upload a template and run validation to check for structural errors or constraint violations before deploying it to your openEHR CDR. Errors are displayed with enough context to identify the source.
Generate a basic HTML form from any operational template. The form reflects the data points defined in the template. Useful for showing clinicians what the data model looks like before building a full UI.
Access all stored artifacts and generated resources programmatically. The REST API lets you integrate the Toolkit into CI/CD pipelines, automated test suites, or other tooling.
Let us know how we can help you.