Build on openEHR
Open specifications, a shared library of clinical models and a market of conformant platforms, so you can spend your time building applications instead of reinventing data models.
How building with openEHR works
Most openEHR projects follow the same four steps. Each one has open tools and a community behind it.
Model your data
Reuse existing archetypes wherever you can, then combine them into templates for your use case.
Choose a platform
Store data in an open source or commercial openEHR clinical data repository.
Build applications
Use low-code form builders, the REST API, AQL queries and SDKs to deliver apps quickly.
Connect and scale
Exchange data with FHIR, IHE and terminologies such as SNOMED CT, and grow component by component.
Tools and products
A growing ecosystem of open source and commercial products, listed by what they help you do. See the full overview.
- Platforms
Clinical data repositories and full openEHR platforms.
- Modelling tools
Archetype and template editors, including the Archetype Designer.
- Applications
Ready-made clinical applications built on openEHR.
- Guidelines and CDS
Tools for computable guidelines and clinical decision support.
- Libraries
SDKs and code libraries in a range of languages.
- Knowledge management
Manage, review and publish clinical models at scale.
- Archetype Designer
Design archetypes and templates in your browser.
- Archetype Editor
The original desktop tool for editing archetypes.
- Deployments
See what others have built and learn from them.
Specifications and standards
The openEHR specifications are free to read and implement. Here’s where they live and how they change.
- Specifications site
Reference model, archetype formalism, REST API, AQL and more.
- Specifications program
The Specifications Editorial Committee and its work.
- Release strategy
How and when new versions of the specifications are released.
- Change process
How to raise and track a change request.
- Software program
The Software Program Board and community open source.
- SNOMED CT and openEHR
Using SNOMED CT with openEHR models.
- Logos and trademarks
How products can refer to openEHR.
Build with the community
You won’t be building alone. Ask questions, share code and learn from people who’ve done it before.
- Discourse forum
The best place to ask technical and modelling questions.
- GitHub (external)
Open source code, specifications and tooling.
- Developer ecosystem
A developer’s guide to the openEHR ecosystem.
- Training
Courses and recognised openEHR educators.
- Fellowship Program
Funded projects that grow openEHR skills and tools.
Work with suppliers and experts
Need a platform, an integrator or a trainer? openEHR’s partners and professional members build, implement and support openEHR around the world.
- Industry partners
Vendors, integrators and consultancies using openEHR.
- Professional members
Independent consultants, trainers and experts.
- Organisation partners
Health organisations that have adopted openEHR.
- Contact us
Not sure where to start? We’ll point you in the right direction.
From the blog
- Making archetype work easier
Martin Koch’s Archetype Companion helps you find and reuse archetypes.
- The science of clinical modeling using openEHR
Modelling fundamentals every builder should know.
- IHE and the openEHR Plugathon
Interoperability profiles meet openEHR models.
- From proof of concept to a reusable blueprint
An implementation guide for openEHR and FHIR in Switzerland.
Keep exploring
What is openEHR?
The open standard for lifelong, vendor-neutral health records, and who it’s for.
Join openEHR
Become a member or partner, take part in our programs and meet the global community.