Menu
▾
▴
#28 Add openEHR specifications
openEHR is a virtual community working on interoperability and computability in e-health. Its main focus is electronic patient records (EHRs) and systems.
The openEHR Foundation has published a set of specifications defining a health information reference model, a language for building 'clinical models', or archetypes, which are separate from the software, and a query language. The architecture is designed to make use of external health terminologies, such as SNOMED CT, LOINC and ICDx. Components and systems conforming to openEHR are 'open' in terms of data (they obey the published openEHR XML Schemas), models (they are driven by archetypes, written in the published ADL formalism) and APIs. They share the key openEHR innovation of adaptability, due to the archetypes being external to the software, and significant parts of the software being machine-derived from the archetypes.
The essential outcome is systems and tools for computing with health information at a semantic level, thus enabling true analytic functions like decision support, and research querying.
Hi,
Thank you very much for your query. It would be very useful if you could give us a couple of examples (URLs) of the type of information you wish to access through identifiers.org URIs?
Thanks in advance,
cheers
Nick
Hi Nick, happy new year :)
Here are some examples (this is from Release 1.0.3)
| EHR IM | The information model of the openEHR EHR. |
| Demographic IM | The openEHR demographics information model. |
| Common IM | Information model containing common concepts, including the archetype-enabling LOCATABLE class, party references, audits and attestations, change control, and authored resources. |
| Data Structures IM | Information model of data structures, incuding a powerful model of time-series data. |
| Data Types IM | Information model of data types, including quantities, date/times, plain and coded text, time specification, multimedia and URIs. |
| Support IM | Support model defining identifiers, assumed types, and terminology interface specification used in the rest of the IMs. |
| Integration IM | Information model for representing legacy data is a free-form Entry type for implementing integration solutions. |
| EHR Extract IM | The information model of the EHR Extract, which is a serilialisation of content from an EHR. |
We need to identify and manage different versions of each specification so having unique identifiers would help tackle this.
So, for example for the first above (EHR IM) release 1.0.1 s here: http://www.openehr.org/releases/1.0.1/architecture/rm/ehr_im.pdf
And release 1.0.2 is at: http://openehr.org/releases/1.0.2/architecture/rm/ehr_im.pdf
So if can have a base URI like http://identifiers.org/openehr-specs - we can then assign further partitions based on Release numbers and whether these are related to Reference Model (RM), Archetype Model (AM) or other family of specs such as Archetype Query Language (AQL) and Guideline Definition Language (GDL). It looks we will need to come up with a consistent URI organisation as current web page URLs are not entirely consistent (e.g. 1.0.3. release is at: http://www.openehr.org/releases/RM/Release-1.0.3/ehr.html)
Many thanks in advance
Cheers,
-koray
To: [identifiers-org:new-collection] 28@new-collection.identifiers-org.p.re.sf.net
Sent: Wednesday, 6 January 2016 3:15 AM
Subject: [identifiers-org:new-collection] #28 Add openEHR specifications
Hi,
Thank you very much for your query. It would be very useful if you could give us a couple of examples (URLs) of the type of information you wish to access through identifiers.org URIs? Thanks in advance,cheersNick [new-collection:#28] Add openEHR specificationsStatus: open
Created: Wed Dec 23, 2015 02:16 AM UTC by Anonymous
Last Updated: Wed Dec 23, 2015 02:16 AM UTC
Owner: nobodyopenEHR is a virtual community working on interoperability and computability in e-health. Its main focus is electronic patient records (EHRs) and systems.The openEHR Foundation has published a set of specifications defining a health information reference model, a language for building 'clinical models', or archetypes, which are separate from the software, and a query language. The architecture is designed to make use of external health terminologies, such as SNOMED CT, LOINC and ICDx. Components and systems conforming to openEHR are 'open' in terms of data (they obey the published openEHR XML Schemas), models (they are driven by archetypes, written in the published ADL formalism) and APIs. They share the key openEHR innovation of adaptability, due to the archetypes being external to the software, and significant parts of the software being machine-derived from the archetypes.The essential outcome is systems and tools for computing with health information at a semantic level, thus enabling true analytic functions like decision support, and research querying.Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/identifiers-org/new-collection/28/To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Related
Request new collection: #28