Re: design description of lab archetypes

2017-12-04 Thread GF
Hi, In my SIAMM thinking: - I use the ENTRY to model using a fixed pattern the process of documentation of anything (the context of documentation) and that what is documented - What can be documented is done using a panel (compound statement) as CLUSTER - The compound statement CLUSTER documents

RE: design description of lab archetypes

2017-12-03 Thread Koray Atalag
-boun...@lists.openehr.org] On Behalf Of Heather Leslie Sent: Saturday, 15 July 2017 4:11 p.m. To: For openEHR clinical discussions Subject: [FORGED] RE: design description of lab archetypes Hi Thomas, Yes, the analyte is a newborn, developed in response to review feedback. Ian has been leading

Re: design description of lab archetypes

2017-07-18 Thread Thomas Beale
On 17/07/2017 17:00, Karsten Hilbert wrote: Maybe I am barking up the wrong tree - is panel only meant to reference the "probe" or "sample" ? Typically, "panel" is a tool for (lazy ;-) doctors, providing relief from the need to really think about which answers are needed, and hence which

Re: design description of lab archetypes

2017-07-17 Thread Karsten Hilbert
On Mon, Jul 17, 2017 at 10:31:41AM -0300, Thomas Beale wrote: > On 15/07/2017 15:36, Karsten Hilbert wrote: > > > > Receiving systems may decide (or not) to group single-analyte > > results one way or another (typically the way they were > > ordered ...) but that is an implementation detail. A

Re: design description of lab archetypes

2017-07-17 Thread Thomas Beale
Hi Colin, this is already taken care of in standard openEHR , Observation class. - thomas On 17/07/2017 12:15, Colin Sutton wrote: > Can I suggest that 'Sample date' (aka

Re: design description of lab archetypes

2017-07-17 Thread Colin Sutton
Can I suggest that 'Sample date' (aka 'Collection date') and 'Analysis date' should be explicit in 'etc' and 'other details' respectively? -- Colin On 13 Jul 2017, at 2:43 pm, Thomas Beale > wrote: Heather, thanks that's a page I was

Re: design description of lab archetypes

2017-07-17 Thread Thomas Beale
On 15/07/2017 15:36, Karsten Hilbert wrote: Receiving systems may decide (or not) to group single-analyte results one way or another (typically the way they were ordered ...) but that is an implementation detail. A result may carry with it a reference to the order to facilitate such grouping.

Re: design description of lab archetypes

2017-07-15 Thread Karsten Hilbert
On Thu, Jul 13, 2017 at 09:42:13AM -0300, Thomas Beale wrote: > I think we need more explanation about the basic intended structure. There > are at least the following scenarios to cope with for the 'simple tabular' > types like biochemistry. > > 1. The doc orders (taking thyroid as an example)

RE: design description of lab archetypes

2017-07-14 Thread Heather Leslie
the archetype – http://www.openehr.org/ckm/#showArchetype_1013.1.2191. Regards Heather From: openEHR-clinical [mailto:openehr-clinical-boun...@lists.openehr.org] On Behalf Of Thomas Beale Sent: Thursday, 13 July 2017 10:42 PM To: openehr-clinical@lists.openehr.org Subject: Re: design description of lab

Re: design description of lab archetypes

2017-07-14 Thread Thomas Beale
On 13/07/2017 19:02, GF wrote: Hi, Panels have a specific name Stan tells me that LOINC can code most/all standard panels. And can have an associated result describing the panel as a whole. Plus context data pertaining to the panel and all its items. E.g. /Haematology panel: normal./ Both

Re: design description of lab archetypes

2017-07-13 Thread GF
Hi, Panels have a specific name And can have an associated result describing the panel as a whole. Plus context data pertaining to the panel and all its items. E.g. Haematology panel: normal. Both the Panelresult and the results of the individual items can to be queried. Remarks: - The

Re: design description of lab archetypes

2017-07-13 Thread Thomas Beale
Going a bit further in my analysis, it seems to me that the archetypes needed are not exactly what are in CKM right now... I would expect: * *COMPOSITION*: *Lab report* o order meta-data o etc o *OBSERVATION: Lab Test [*]* *// may be LOINC coded here, or via archetype

Re: design description of lab archetypes

2017-07-13 Thread Thomas Beale
Heather, thanks that's a page I was looking for. I assume the laboratory analyte archetype is newer than this? It is not mentioned. I think we need more explanation about the basic intended structure. There are at least the following scenarios to cope with for the 'simple tabular' types

RE: design description of lab archetypes

2017-07-13 Thread Heather Leslie
Hi Thomas, This might help you: https://openehr.atlassian.net/wiki/spaces/healthmod/pages/91139266/Implementing+Laboratory+Tests+in+openEHR Heather From: openEHR-clinical [mailto:openehr-clinical-boun...@lists.openehr.org] On Behalf Of Thomas Beale Sent: Thursday, 13 July 2017 1:22 AM To: For