The openEHRSpecifications Editorial Committee (SEC)
<https://www.openehr.org/programs/specification/editorialcommittee>is
proud to announce*Release 1.0.4 of the Reference Model (RM)
<https://specifications.openehr.org/releases/RM/Release-1.0.4/>*component
of openEHR.
This release implements25 Change Requests
<https://openehr.atlassian.net/projects/SPECRM/versions/11074/tab/release-report-all-issues> (CRs),
including:
* support Markdown in DV_TEXT / DvText;
* allow context data for 'persistent' (longitudinal) Compositions;
* move most material from Support IM to BASE component, including
identifiers and other base types;
* add recommendations on preferred use of Guids as EHR id;
* documentation improvements.
These changes address28 Problem Reports
<https://openehr.atlassian.net/projects/SPECPR/versions/10861/tab/release-report-all-issues>(PRs),
most of which are requests for documentation clarification, attesting to
the stability of the openEHR RM as a model for the patient EHR.
TheITS component repositories
<https://specifications.openehr.org/releases/ITS/latest/index>(XSD,
JSON, BMM) will be released with changes from RM Release 1.0.4 in the
next week or so.
We are now working hard onBASE Release-1.1.0
<https://openehr.atlassian.net/projects/SPECBASE/versions/11760/tab/release-report-all-issues>,RM
Release-1.1.0
<https://openehr.atlassian.net/projects/SPECRM/versions/12516/tab/release-report-all-issues>,
and also further releases ofGDL (Guideline Definition Language)
<https://specifications.openehr.org/releases/CDS/latest/index>,Task
Planning
<https://specifications.openehr.org/releases/PROC/latest/index>and the
openEHRConformance specification
<https://specifications.openehr.org/releases/CNF/latest/openehr_platform_conformance.html>.
Today, the majority of all the specifications work in openEHR is driven
by requirements and experience from production implementation and
deployments, and we expect this to continue with growing adoption around
the world.
We would like to acknowledge all those who reported problems or worked
on this release, and we would like to encourage the community to
continue to provide feedback, enabling us to evolve the specifications
to meet changing needs and correct errors.
_______________________________________________
openEHR-announce mailing list
openEHR-announce@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-announce_lists.openehr.org
