Good links - the architecture overview explains a lot. I downloaded
the editor and was looking to load the openEHR archetypes but the
following link fails to find a tar.gz file of all ADLs:
I noticed that the Archetype Editor has the ability to create
references to UMLS and Snowmed content - is that part of OpenEHR or is
it licensed separately?
First, I think you must have a conceptual idea of “diagnostic-therapeutic cycle” (see http://www.mieur.nl/mihandbook/r_3_3/mmedia/f01_02l.gif )
And you think how to organize medical concepts into information model (openEHR’s information model. For basic understanding, refer to http://ontology.buffalo.edu/medo/HL7_2004.pdf) and how to use information model in real practical situation(openEHR’s archetype).
For your understanding, from information model’s viewpoint your example may be coded like this.
(it’s peudocode and not exactly match with openEHR. It’s just for your understanding )
<Composition (Admission Note)>
with admitted with
Received ml/kg of volume resuscitation last night.
Went to OR for placement, transferred to ICU for management after OR.
a) Send
b) for wound infection
But, in order to use this example in real situation, we need to define codes(terminology), ranges and other constraints for , , etc. This is the role of archetype.
I don’t know whether these are tips for you. But as Mikael Nystrom said, it is better that you start reading Architecture Overview and post any questions here
Simple diagrams help me a lot My background is computer science not medicine.
I am starting to get the picture, this is exciting stuff. In the past I have the best HIS systems organize clinical data into a hierarchy with little rhyme or reason, and custom to the client. Writing meaningful reports from flowsheet data was a disaster. This could really help a lot and gives me something to focus my implementation on rather than a custom domain model.
I noticed that the Archetype Editor has the ability to
create references to UMLS and Snowmed content - is that
part of OpenEHR or is it licensed separately?
openEHR is designed to be able to map to any terminology (and also possible
to use without any mappings at all).
Neither UMLS nor Snomed CT are included in openEHR and you need to have
separate licenses for them, but if you are based in the US I think it is a
minor problem. (Someone who knows details about the licenses in the US
better than me can maybe add some information. I am based in Sweden and are
only engaged in Snomed CT:s organization IHTSDO.)
(Snomed CT is an acronym for Systematized Nomenclature of Medicine-Clinical
Terms, so there is no w in the acronym.)
Greetings,
Mikael Nyström
Medical Informatics
Department of Biomedical Engineering
Linköping University
Sweden
I am going to respond to how such a record might exist as openEHR data. You have gone for a very narrative form which may mean that you are thinking dictation - very hard to go from narrative to formally structured data (ask Peter Elkin at the Mayo). I have clipped the openEHR-EHR- from the lead of archetype names.
Greg Caulton wrote:
<age, sex> - with <ESLD> admitted with [ADMISSION DIAGNOSIS as EVALUATION-problem-diagnosis]<dehydration>
The following would be noting findings in the record - we could use hyperlinks to those parts of the EHR and would not necessarily re-enter the data. It is an important feature of openEHR that a URL can be expressed to any data point in an EHR.
Received <n> ml/kg of volume resuscitation last night. Went to OR for
<CVL> placement, transferred to ICU for management after OR.
a) Send <bacterial infection> <if stooling>
a) - this is an INSTRUCTION-laboratory and the timing for action is if the person uses their bowels
b) <Re|start> <med> for wound infection
b) - this is an ACTION-medication and re-commence of a standing instruction.
c) Check weights
c) - this is an INSTRUCTION-observation to record the weight - timing ? daily
d) etc.
_____________________
How does OpenEHR come into play with this action -
Simple diagrams help me a lot My background is computer science
not medicine.
I am starting to get the picture, this is exciting stuff. In the past
I have the best HIS systems organize clinical data into a hierarchy
with little rhyme or reason, and custom to the client. Writing
meaningful reports from flowsheet data was a disaster. This could
really help a lot and gives me something to focus my implementation on
rather than a custom domain model.