# New openEHR Developer Guide
**URL:** https://discourse.openehr.org/t/new-openehr-developer-guide/17211
**Category:** News
**Created:** [20 August 2026 10:00 UTC](https://discourse.openehr.org/t/new-openehr-developer-guide/17211 "2026-08-20T10:00:39Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@marcusbaw](https://discourse.openehr.org/u/marcusbaw)
#### Post date: [20 August 2026 10:00 UTC](https://discourse.openehr.org/t/new-openehr-developer-guide/17211/1 "2026-08-20T10:00:40Z")
The Software Program Board has published the [openEHR Developer Guide](https://developer.openehr.org/).
The first section is the [openEHR Tooling Guide](https://developer.openehr.org/tooling/), a practical survey of archetype and template authoring tools, clinical data repositories, knowledge management, SDKs, AQL tooling, and legacy software.
The guide is maintained as a Zensical site in the public [openEHR/developer.openehr.org](https://github.com/openEHR/developer.openehr.org) repository. Implementation and conformance guidance will be added over time.
Please reply here with corrections or additions, or open a pull request in the repository.
---
### Author:  [@dmccaf](https://discourse.openehr.org/u/dmccaf)
#### Post date: [20 August 2026 13:57 UTC](https://discourse.openehr.org/t/new-openehr-developer-guide/17211/2 "2026-08-20T13:57:30Z")
Wow @marcusbaw - you work quickly. Kudos!
Minor thing. I get a certificate warning when accessing [https://developer.openehr.org/](https://developer.openehr.org/)
---
### Author:  [@Pete\_Bouvier](https://discourse.openehr.org/u/Pete_Bouvier)
#### Post date: [20 August 2026 14:08 UTC](https://discourse.openehr.org/t/new-openehr-developer-guide/17211/3 "2026-08-20T14:08:02Z")
Sounds great. Well done SPB. I can’t see the cert warning myself.
I’ll find a spot on the website to push people your way. We actually need a page on the website to break down how the various tools, products, apps CDRs etc interact…
---
### Author:  [@Seref](https://discourse.openehr.org/u/Seref)
#### Post date: [20 August 2026 14:17 UTC](https://discourse.openehr.org/t/new-openehr-developer-guide/17211/4 "2026-08-20T14:17:59Z")
Great news and thanks for the work! I’m keen to read it but MS Edge is scared:
---
### Author:  [@marcusbaw](https://discourse.openehr.org/u/marcusbaw)
#### Post date: [20 August 2026 14:26 UTC](https://discourse.openehr.org/t/new-openehr-developer-guide/17211/5 "2026-08-20T14:26:07Z")
@dmccaf thanks - I had all the content already done months ago, was just waiting till we knew where it was to be published. I also have a lot of ‘[house-style](https://github.com/pacharanero/house-style)’ that helps agents do what I always want doing, every time I start a new project, this helps.
The LetsEncrypt seems to be taking a while to make its way around the Internet.
Everything is correctly configured at GitHub Pages AFAICT:
@Seref I would refrain from sending the site your passwords, messages, or credit card details then 😜
---
### Author:  [@Seref](https://discourse.openehr.org/u/Seref)
#### Post date: [21 August 2026 20:17 UTC](https://discourse.openehr.org/t/new-openehr-developer-guide/17211/6 "2026-08-21T20:17:19Z")
> [@marcusbaw](#):
>
> sending the site your passwords, messages, or credit card details then
---
### Author:  [@johngrant4est](https://discourse.openehr.org/u/johngrant4est)
#### Post date: [21 August 2026 21:44 UTC](https://discourse.openehr.org/t/new-openehr-developer-guide/17211/7 "2026-08-21T21:44:20Z")
Looks okay from here - as you say, probably propagation delay