Subject of care

Eric We have fetus and donor as subjects of care also - sorry for omitting that. Cheers, Sam -Original Message- From: Eric Browne [mailto:eric at montagesystems.com.au] Sent: Monday, 2 December 2002 8:48 AM To: Sam Heard Cc: Openehr-Technical Subject: Re: Subject of care Sam

Categorising EHR Content

-Original Message- From: Eric Browne [mailto:eric at montagesystems.com.au] Sent: Saturday, 7 December 2002 2:25 PM To: Thomas Beale Cc: Sam Heard; openehr-technical at openehr.org Subject: Re: Categorising EHR Content Tom Sam, Thanks for taking the time to explain the openEHR use

[Fwd: RE: Subject of care]

Message- From: Thomas Beale [mailto:thomas at deepthought.com.au] Sent: Thursday, 19 December 2002 1:43 AM To: Sam Heard Cc: openehr-technical at openehr.org Subject: Re: [Fwd: RE: Subject of care] I think that the only systematic approach is to make a new EHR for each genetically

[Fwd: RE: Subject of care]

Ed Thanks for that - I think this is the correct approach - recognising that there will be times when a fetal record may be required - such as with antenatal surgery etc. Any thoughts on the EHR SIG? Cheers, Sam -Original Message- From: owner-openehr-technical at openehr.org

[Fwd: RE: Subject of care]

Dear All Sorry, I have been out of touch over the Xmas - great surf on the east coast! This may be old ground? This conversation is sounding a little like a technical solution rather than a pragmatic solution. My response is that both solutions are required - a fetal record (rare) and fetal

Data Types

Tim I think this is true but from a date point of view we can only know the year if the month is unknown - if it is one or two then the person will have to guess and store it as a fuzzy date. I think this is the only sensible approach. We can record in text the time issues that have been

TBD_10

This was meant to be a data type for the physical location of something - an Xray film, specimen etc. I agree that this should be an archetype. Cheers, Sam -Original Message- From: owner-openehr-technical at openehr.org [mailto:owner-openehr-technical at openehr.org]On Behalf Of

Data Types

Tim This is definately a mistake - amny disorders have a date of onset that is fuzzy from a month point of view but is worthwhile - last Pap smear, last attendance at Ophthalmologist etc. The point about a fuzzy date is that it is helpful for human interpretation - a month that a spouse died will

The concept of contribution

method. Cheers Henry Li -Original Message- From: Denis Nosworthy [mailto:Denis.Nosworthy at swsahs.nsw.gov.au] mailto:[mailto:Denis.Nosworthy at swsahs.nsw.gov.au] Sent: Tuesday, 11 June 2002 8:37 To: 'Sam Heard

Patient notifications

, Sam Dr Sam Heard The Good Electronic Health Record Ocean Informatics, openEHR 105 Rapid Creek Rd Rapid Creek NT 0810 Ph: +61 417 838 808 sam.heard at bigpond.com www.gehr.org www.openEHR.org __ -Original

Archetype rules (invariants) in openEHR RM?

Tom I think work Unit or Work Group is important as long as it is linked to an organisation - a person might work on a ward, an outpatient department and in the cardiology team. As far as the referral is concerned - it could be to a work unit if that is available and has a system for dealing

Terminology services

Dipak I would propose that such narratives be kept in a different transaction if you want to specify the language and referenced from the main record. This can be transparent for the user (BUT the language would of the referenced transaction would need to be stated as it differed from the current

No known allergies

that the empty entry allows a return string of type DV_TEXT (ie plain or coded) to state the situation - in this case it might be No Known allergies. Comments? Cheers, Sam Dr Sam Heard Ocean Informatics, openEHR Co-Chair, EHR-SIG, HL7 Chair EHR IT-14-2

Patient notifications

Dr Sam Heard The Good Electronic Health Record Ocean Informatics, openEHR 105 Rapid Creek Rd Rapid Creek NT 0810 Ph: +61 417 838 808 sam.heard at bigpond.com www.gehr.org www.openEHR.org __ - If you have any questions

Archetype ontology

not want this sort of EHR and it served no useful purpose. Cheers, Sam Dr Sam Heard The Good Electronic Health Record Ocean Informatics, openEHR 105 Rapid Creek Rd Rapid Creek NT 0810 Ph: +61 417 838 808 sam.heard at bigpond.com www.gehr.org www.openEHR.org

Archetype ontology

at the moment really do not match the reality and until we have working EHR systems and integration, these sorts of debate need to stay in the background. They do not really impinge greatly on the EHR requirements. But keep it up! Sam Heard -Original Message- From: owner-openehr

openEHR security

://www.chime.ucl.ac.uk/work-areas/ehrs/GEHR/Deliverables.htm#D8 Keep up the good work! Sam Dr Sam Heard Ocean Informatics, openEHR Co-Chair, EHR-SIG, HL7 Chair EHR IT-14-2, Standards Australia Hon. Senior Research Fellow, UCL, London 105 Rapid

GEHR philosophical background info

Paul I've been following these discussions with a lot of interest. So I guess it's time for me to put in my two bits. While I've seen a couple of references to ownership of the medical record, I havent seen anything definitive that defines it (e.g. patient, provider, legal custiodian of

Encoding concept-relationships in openehr archetypes.

Gerard I am using the term 'assumed' value in the archetype editor. This seems helpful as it means that it does not have to be recorded and it is normal practice. A single BP reading is assumed to be sitting - possibly lying - but not standing. Weight is assumed to be measured in light clothing

Distributed Records - An approach

Christopher It has been good to read this thread - but I have to wade in here. In designing openEHR I have had a few principles in mind. 1. The technical solution should impose no constraints on social behaviour. This means to me that if we want one EHR for each person that is patient held or

Ontology Standard for Archtypes

Matias I have developed an ontology of archetypes in Protege - it has been a large endeavour and I think is starting to get there. I am happy to send this to you to have a look at. I believe OWL and Protege are merging their approaches. Cheers, Sam -Original Message- From:

Introducing myself + question

Rafal We have seen this coming for some time and I would point out a few things that seem clear: 1. That queries can be based across a number of EHRs or within one - the oprimisation issues are somewhat different 2. That queries may return rows of data (like in current RDBS) or lumps of data for

Data Types RM

Grahame It is like being reviewed by a tornado - even my teeth feel clean! These comments relate to v1.7.1 Section 4.2 DV_BOOLEAN. are the values {true, false} case sensitive? Generally, is openehr case sensitive or not? no they're not. I'm not sure what it means to say is openEHR

Links

implementation issues for us to consider as yet. Cheers, Sam Dr Sam Heard Ocean Informatics, openEHR Co-Chair, EHR-SIG, HL7 Chair EHR IT-14-2, Standards Australia Hon. Senior Research Fellow, UCL, London 105 Rapid Creek Rd Rapid Creek NT 0810 Ph: +61 417 838

Genetic information and RM (data types and structures)

record - as there will need to be a lot of other information present to make healthcare work. What do you think? Cheers, Sam Heard Dr Sam Heard Ocean Informatics, openEHR Co-Chair, EHR-SIG, HL7 Chair EHR IT-14-2, Standards Australia Hon. Senior

Archetypes and Terminology

an archetype driven information model. Cheers, Sam Heard Dr Sam Heard Ocean Informatics, openEHR Co-Chair, EHR-SIG, HL7 Chair EHR IT-14-9-2, Standards Australia Hon. Senior Research Fellow, UCL, London 105 Rapid Creek Rd Rapid Creek NT 0810 Ph: +61 417 838

Pathology requirements TIMED MEASUREMENTS

' as the unit rather than time. This would mean that people did not have to enter spurious times in the data and name the event as Sample 1, which could be misleading. Comments? Cheers, Sam Dr Sam Heard Ocean Informatics, openEHR Co-Chair, EHR-SIG, HL7 Chair

Pathology requirements TEXTURAL RESULTS TO QUANTITIES

independent of the archetype. This will look a little clunky in the archetype itself and I will need to discuss the technical issues with Thomas. Cheers, Sam Dr Sam Heard Ocean Informatics, openEHR Co-Chair, EHR-SIG, HL7 Chair EHR IT-14-9-2, Standards Australia

Pathology requirements TIMED MEASUREMENTS

Message- From: owner-openehr-technical at openehr.org [mailto:owner-openehr-technical at openehr.org]On Behalf Of Bhupinder Singh Sent: Thursday, 23 October 2003 1:12 PM To: Sam Heard; Openehr-Technical Subject: Re: Pathology requirements TIMED MEASUREMENTS Further to what you have

FW: Re: Pathology requirements TEXTURAL RESULTS TO QUANTITIES

-Original Message- From: Sam Heard [mailto:sam.he...@bigpond.com] Sent: Friday, 24 October 2003 11:00 AM To: Tim Churches Subject: RE: Re: Pathology requirements TEXTURAL RESULTS TO QUANTITIES Tim As we seek to achieve automatic processing of some of the data in the EHR

Pathology requirements UNITS

as reference ranges. What do others think? I think Labs will probably push back on this one. Sam -Original Message- From: owner-openehr-technical at openehr.org [mailto:owner-openehr-technical at openehr.org]On Behalf Of Bhupinder Singh Sent: Thursday, 23 October 2003 1:30 PM To: Sam Heard

Pathology requirements CONTRIBUTION - 2 versions at once

Bhipinder Thank you. I think we have all of these issues covered. Sam -Original Message- From: owner-openehr-technical at openehr.org [mailto:owner-openehr-technical at openehr.org]On Behalf Of Bhupinder Singh Sent: Thursday, 23 October 2003 1:23 PM To: Sam Heard; Openehr-Technical

Pathology requirements TIMED MEASUREMENTS

: Thomas Beale [mailto:thomas at deepthought.com.au] Sent: Friday, 24 October 2003 5:58 PM To: Sam Heard; Openehr-Technical Subject: Re: Pathology requirements TIMED MEASUREMENTS 1. We recognise this is a sampling issue and there should be a label on each sample which is transfered

Pathology requirements TEXTURAL RESULTS TO QUANTITIES

Subject: Re: Pathology requirements TEXTURAL RESULTS TO QUANTITIES Tim Churches wrote: Sam Heard sam.heard at bigpond.com wrote: TEXTURAL RESULTS TO QUANTITIES ?TEXTUAL? This raises the general issue of how mixed categorical/ordinal/scalar quantities are handled eg (made up

Pathology requirements UNITS

Thomas It is more that units match Force/Length^2 for pressure and it is an expression that the property of pressure is the property of Force per property of area - this does allow a very wide range of units to be used if that is the requirement. I am starting to see that things do get

Pathology requirements TIMED MEASUREMENTS

Bhupinder The only values we are not wanting to show are those that are wrong - and have been changed in a later version. The idea behind this is to store the information in an openEHR system inside the Pathology service and then send an extract - rather than develop a lot of messages. Cheers,

Pathology requirements CONTRIBUTION - 2 versions at once

. (Did I understand your scenario correctly?) Regards, -Chris At 07:26 PM 10/24/2003 +1000, Thomas Beale wrote: Sam Heard sam.heard at bigpond.com, wrote: CONTRIBUTION - 2 versions at once There is a particular problem with results that are deemed

Modelling Episodes in openEHR

Bill and all This is a very important consideration and one that we need to get right for lots of reasons. Tom has been proposing an aggregation approach - allowing us to find all data that relates to something - a disease, care at an institution etc. It is clear that there are aspects of

History paths

Rong This is an important consideration - especially if we are to get the event right. We have recently been moving away from offset to a datetime stamp for the items in the history - as this is easier and more realistic for summary data over a long period. With this change - you want to

Issues with Latest Spec

for sensitivities to penicillinor looking for sensitivies of E. Coli. I hope this is helpful, Sam Heard Matias Klein President, CTO Ethidium Health Systems 3993 Huntingdon Pike - Suite 108 Huntingdon Valley, PA 19006-1927 USA Office: (215)938-8630 Fax: (866)583-8018 http

Issues with Latest Spec

for sensitivities to penicillinor looking for sensitivies of E. Coli. I hope this is helpful, Sam Heard Matias Klein President, CTO Ethidium Health Systems 3993 Huntingdon Pike - Suite 108 Huntingdon Valley, PA 19006-1927 USA Office: (215)938-8630 Fax: (866)583-8018 http

Propositions?

Matius Thank you for your email. You are correct in your assertion. I have felt that this is not summary data and as an Entry should go in an archetype called questionnaire. Archetype can then have a question and an answer. Such data is usually derived from the EHR in the long run - I call it

Propositions?

Gerard The alternative suggestion is to allow the patient to add information to the EHR problem list - ie enter diabetes mellitus as a problem. It is true that the Entry will be known to have come from them. The composition will also come from them and unless the world changes a little - will

Propositions?

Jim Patients often report that they have diabetes and clinicians usually believe them. Infact it would be negligent not to without good reason. So we are used to doing that. Entering the problem in their problem list is something that increases the scope of the information. We have added

Basic EHR functionality

Tim The openEHR and before it GEHR work on legality made it clear to me that a document has no legal status until it is saved in some voluntary manner - just as a correction in a written document has no status as fact (if you contemporaneously correct the document). Sam On Sat, 2004-03-06

[Fwd: Fwd: XML.org Daily Newslink. Friday, 12 November 2004]

Original Message Subject: Fwd: XML.org Daily Newslink. Friday, 12 November 2004 Date: Sat, 13 Nov 2004 12:20:36 +0100 From: Gerard Freriks gf...@luna.nl To: Angelo ROSSI MORI angelo at itbm.rm.cnr.it, Sam Heard sam.heard at bigpond.com, Klein Gunnar gunnar.klein at sis.se

Archetype vs. ontology

Philippe Thank you for this...very informative and I am starting to see how we are converging with your work. I believe that the 'structured terminology' - fils guide down from the archetype nodes - is an important part - SNOMED are trying to address it generically (ie without archetypes) -

Episodes in openEHR

Tim These links are very helpful...particularly to show that the idea of episode is about one consultant - rather than admission. The Australian data dictionary is about an admitted patient episode. It is clear that many types of groupings will be required. The Folders solution may be one -

Archetype constraints and interfacing instruments/DSS to an OpenEHR system.

Damon This is important to consider I believe that DSS groups will be a major player in determining the final archetypes that are agreed at a high level. It seems to me that in the same way, archetypes will have great impact on the development of future EHR-compatible instrument interface

openEHR and Odyssee

Philippe, I agree - your work has been an inspiration to us to keep going with the approach we have chosen. There is no doubt that we need an ontological underpinning in our work - and its relation to the ontological underpinning of terminology should be clear. For a start we are populating

Medication Regimens

Matias Thanks for the email - and sorry to be so slow getting back to you. Our current work in this area relates to instructions as a generic class in the reference model. The links between individual instructions can modelled in a number of ways: 1. The start condition for one instruction

Flavour of null

will want to use this for all sorts of reasons, one clear example is when an electrolyte sample has haemolysed - and they cannot give a potassium reading (they do not want to omit it!) So I want to propose that the flavour of null is set to DV_TEXT. Cheers Sam Heard - If you have any questions about

The Uncertainty Decision was: Dr R LONJON Confidence indicator !

Arild and Tim This is clearly an issue. In the CIP project the group wanted to be able to say that a diagnosis was a working diagnosis. We have archetyped a number of concepts that I think will enable the clinician to express these levels of uncertainty without resorting to confidence ratings

Age, gender and more

the new type is to participate violate any of the definitions that applied to the old type? If so, then all instances of usage of the old type must be reexamined and brought back into line. This is known as the 'frame problem'. Good luck. Quoting Sam Heard sam.heard at bigpond.com: Tom

Time in interval in interval measurements

Dear all I have been thinking about the date/time measurement with regard to interval measurements in the HISTORY class (used in OBSERVATION) Consider a maximum temperature measured over a 12 hour period - or an average. At the moment the date/time will be the beginning of the 12 hr period.

Cyclic events

Phillippe We are working hard on INSTRUCTION at the moment and have a document coming out soon. The model is basically to have an instruction and a new class of ENTRY which records execution or actions. Thus the execution of an instruction can be tracked and any variation recorded (to the

Age - a summary

Ergin, and all ERGIN: Thanks - there is no problem working from date of birth forward to age group - it is when you are working back and times are fuzzy. In family history when the DOB is not known it is even more of an issue. The issue of FUZZY ages (and other quantities) I believe we need a

Age

Philippe I would suggest that the duration of the event is not included - rather modelled in instructions themselves as there are many different ideas of event duration. The time to give a dose of intravenous agent may be very specific and I believe needs to be modelled explicitly - not as

openEHR in the news in Australia

Tim Ocean Informatics is working in two key activities. 1. Tom is working on the finalisation of the V1 specification and the development of the open source Java kernel at CHIME(UCL) in London, working with a group in Sweden. The DSTC RecordPoint product (J2EE on SQL database as I understand

Demographics service

Karsten You will see from the attestation class that it is possible to add an image with a digital signature - allowing compositions to be pixelmaps for legal purposes if required. Cheers, Sam Heard The EHR is rather a unique document and a layered approach is necessary as old data must never

archetypes and class constraints

will use the actual classes specified. I am sure Tom will have something to say on the matter! Cheers, Sam Heard - If you have any questions about using this list, please send a message to d.lloyd at openehr.org

Demographics service

Dear All The openEHR design team have, over many years, decided to separate the demographic information from the EHR data. Advantages are, amongst others: 1. Security - you need access to both sets of data to know about an individual 2. Normalisation - you can find people even though they have

ADL to XML Schema

David W. Forslund Good to see you sniffing around! The key issue for us in ADL is that Eiffel is not UNICODE compliant. There will be a number of Java parsers soon, and I hope a JAVA archetype editor. I am interested in what you can do with Schematron as well as another implementation

ADL to XML Schema

description to a schematron description. Hopefully, this is semantically possible. Dave On Tue, March 8, 2005 5:58 pm, Sam Heard said: David W. Forslund Good to see you sniffing around! The key issue for us in ADL is that Eiffel is not UNICODE compliant. There will be a number of Java

DV_MULTIMEDIA

a cyclical definition. The danger is fixing to a particular technology - but I think in this case it is worth it. Thoughts? Sam Heard - If you have any questions about using this list, please send a message to d.lloyd at openehr.org

Ang. Archetypes new tool versions

Sorry Torsten The notification was sent to an old email..we have renewed it so I hope that goes well very soon. Sam - If you have any questions about using this list, please send a message to d.lloyd at openehr.org

The semantics of archetype Specialization

Hi Andrew The principles of specialisation have been described in our development environment and there is a placeholder for the documentation in the archetype system document. Our initial thoughts are at: http://www.deepthought.com.au/it/archetypes/output/specialisation.html The rules that

The semantics of archetype Specialization

Andrew The lab result is a good example of further constraining and it is really additional constraints. It is just that the at0013 (any data type) is labelled and turned into a quantity with units. It looks like extention but is it further constraint in this instance. However, we do extend

The semantics of archetype Specialization

Andrew We are not able to implement specialisation as I would like - true O-O would be better - so the child has all the features of the parent at the outset - though the editor knows a little about what is going on. Try renaming - you have to specialise the concept (shadowing in O-O), but

Question about Ocean's Archetype Editor

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20051115/ba78c98c/attachment.html

Archetypes, paths and the reference model - issues for the Editor

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20051117/99e8e947/attachment.html

parsing error

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20051012/e6e93d46/attachment.html

Templates - should we record which are used?

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20051020/dc94bc9d/attachment.html

Templates - should we record which are used?

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20051021/43bd828c/attachment.html

openEHR XML-schema Questions - Include or Import?

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20051021/9a530b40/attachment.html

openEHR XML-schema Questions - Now in four sections

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20051021/a2b7da1d/attachment.html

openEHR XML-schema Questions - Now in four sections

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20051024/d7a30877/attachment.html

DV_QUANTITY_RATIO - remove from specification

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20061210/991d7f80/attachment.html -- next part -- ___ openEHR-technical mailing list

DV_QUANTITY_RATIO - remove from specification

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20061211/b594f834/attachment.html -- next part -- ___ openEHR-technical mailing list

Constraint references

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20061218/384b0599/attachment.html -- next part -- ___ openEHR-technical mailing list

Suggestions re Term binding in Archetype Editor

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20061218/707c2271/attachment.html -- next part -- ___ openEHR-technical mailing list

Suggestions re Term binding in Archetype Editor

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20061218/548fab4a/attachment.html -- next part -- ___ openEHR-technical mailing list

Suggestions re Term binding in Archetype Editor

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20061219/b572aa58/attachment.html -- next part -- ___ openEHR-technical mailing list

XML Schema candidate

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060217/525f3886/attachment.html

openEHR Terminology

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060217/ca03d054/attachment.html

Suggestion about the Multi-axial Archetype Indentifier

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060218/3a339af0/attachment.html

Pathology numeric values not supported in DV_Quantity

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060301/bd767cfc/attachment.html

difficulties starting an implementation

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060118/cdefb747/attachment.html

Proposed slightly radical change to CODE_PHRASE in Text package in openEHR

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060124/5febd8a0/attachment.html

More questions!!!

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060705/d295f949/attachment.html

what is the use of the reference model?

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060707/3c0f9def/attachment.html

Pathology numeric values not supported in DV_Quantity

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060301/14f81e20/attachment.html

Version and commit

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060308/853cbce0/attachment.html

Pathology numeric values not supported in DV_Quantity

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060322/62f4b2c9/attachment.html

New alpha of release 1.0 archetype editor

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060504/0fedbfb9/attachment.html

Authorisation

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060504/99e01d8e/attachment.html

[Fwd: Modelling Medication Administration Control]

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060510/87c5c233/attachment.html

Lifestyle: substance_use archetype

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060510/28b25a87/attachment.html

Lifestyle: substance_use archetype

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060510/39b56008/attachment.html

Lifestyle: substance_use archetype

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060511/4847d27b/attachment.html

  1   2   3   >