Thanks Seung, 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 am sure I will post many more questions. thanks! Greg Boston, MA http://www.patientos.org On 10/18/07, Seung Jong Yu <ggojang at gmail.com> wrote: > > Dear Greg Caulton > > 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)> > <Section (Present illness)> > <Entry> > <age, sex> with <ESLD> admitted with <dehydration> > <Entry> > Received <n> ml/kg of volume resuscitation last night. > <Entry> > Went to OR for <CVL> placement, transferred to ICU for > management after OR. > > <Section (Microbiological Observation)> > <Entry> > a) Send <bacterial infection> <if stooling> > > <Section (Medication)> > <Entry> > b) <Re|start> <med> for wound infection > > But, in order to use this example in real situation, we need to define > codes(terminology), ranges and other constraints for <age>, <sex>, 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 > > Best regards > > Seung Jong Yu MD, MS > > ggojang at gmail.com > > Research Doctor > Medical Information Center Lab. > Seoul National University Hospital > 28 Yongon-dong, Chongno-gu > Seoul 110-799, Korea > +82-2-2072-1978 > > > > 2007/10/19, Greg Caulton <caultonpos at gmail.com>: > > > > Hi, > > > > As someone who is an OpenEHR novice can you give me any tips - there > > is so much information on the website it is difficult to know where to > > start. > > > > While I have yet to understand the full potential of the framework, I > > would like to start with something simple. > > > > Suppose a surgeon signs onto my system and wishes to create a new > > progress note. On paper he may have written (swapping out the <>) > > > > ____________________ > > <age, sex> with <ESLD> admitted with <dehydration> > > > > 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> > > b) <Re|start> <med> for wound infection > > c) Check weights > > d) etc. > > _____________________ > > > > How does OpenEHR come into play with this action - > > > > Should provide lookups or force sentence structure? > > Should it be used to define and store the content into discrete data? > > What data source or service would my code interact with? > > > > I guess I have many questions, and I apologize in advance if I miss > > some concepts. > > > > thanks! > > > > Greg > > > > Boston, MA > > http://www.patientos.org > > _______________________________________________ > > openEHR-technical mailing list > > openEHR-technical at openehr.org > > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > > > > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20071018/13b54226/attachment.html>
