One consequence is that you must omit anything in the situation hierarchy of SNOMED CT, but that is almost certainly a "good thing"
Michael Sent from my iPhone On 18/10/2012, at 2:27 PM, "Renato Iannella" <renato.ianne...@nehta.gov.au<mailto:renato.ianne...@nehta.gov.au>> wrote: On 17 Oct 2012, at 08:11, peter.hend...@kp.org<mailto:peter.hend...@kp.org> wrote: We limit the SNOMED codes to the "what" part of the model, and we use the OO for the "who when where" etc. Hi Peter, does this then limit your ability to detect (computationally) dependencies that go thru the OO model? For example, Person has Allergy substance X and is prescribed Medicine Y (with active ingredient substance X) Cheers Dr Renato Iannella Lead Architect, Information & Policy Services nehta - National E-Health Transition Authority Phone: +61 7 3023 8578 Mobile: +61 4 1313 2206
