terminology
openEHR reference model terminology, and artefacts for binding or using standard terminologies.
Note
This repository is now archived and read-only.
The original content is migrated to https://github.com/openEHR/specifications-TERM/tree/master/computable/XML.
Reporting issues or requesting new terms
Any issues, change requests or problem reports, including requests for new terms should be posted via the openEHR Specifications JIRA Tracker
latest
-
repository blocked for editing - content is now imported at https://github.com/openEHR/specifications-TERM/tree/master/computable/XML
-
added Spanish (es) translations See https://openehr.atlassian.net/browse/SPECPR-401, https://openehr.atlassian.net/browse/SPECTERM-12
RELEASE-2.3.0
-
added missing instruction transition term, and pt, jp translations See https://openehr.atlassian.net/browse/SPECPR-276
-
corrected inconsistent term rubric of concept 532 See https://openehr.atlassian.net/browse/SPECPR-51
-
added 'episodic' term to composition caetgory See https://openehr.atlassian.net/browse/SPECPR-335
RELEASE-2.2.0
-
removed 'no' language which does not formally exist. See https://openehr.atlassian.net/browse/SPECPR-247
RELEASE-2.1.0
-
Corrects truncated rubrics in 'care-settings' and 'relationship' groups. See https://openehr.atlassian.net/browse/SPECPR-244
RELEASE-2.0.0
This release establishes a more solid baseline for terminology list governance.
Some of the outstanding terminology SPECPRs have been fixed here, other fixes will be applied in later commits.
The the Git Tag mechanism will be used to formally label Releases e.g. RELEASE-2.0.0, using the semver.org mechanism adopted by the clinical models.
This branch will be RELEASE-2.0.0, reflecting the breaking changes in the file format and content.
19 Feb 2017
Changes from RELEASE-1.0.0
-
Added Japanese translation.
17 June 2016-06