Re: Alive vs Dead

I agree with Thomas. The EHR is about subjective statements, by an author, at a point in time, in a certain context, about an aspect (state, event, process, …) of the Patient system (person and its environments). Gerard Freriks +31 620347088 gf...@luna.nl > On 5 jan. 2016,

Re: Alive vs Dead

I agree also with this, dead is a state, and about the event, f.e. the cause, or other circumstances can be described, if known, in a special for this case, archetype. ___ openEHR-clinical mailing list openEHR-clinical@lists.openehr.org http://lists.opene

Re: Alive vs Dead

I like that book of him almost most of all books I've ever read. If I was not so busy making a living I would now read it again. ;-) Every page is a new painting in words. But now back to business. Op 6 jan. 2016 00:43 schreef "Thomas Beale" : > > > Following your Kafka reference, we can think of

Re: Alive vs Dead

Wonderful discussion. I go with Eric - “Is deceased” or “Has died” ? [ Using both supports future recording of post-cryogenic or other types of resurrections ;-) ] Here in Brazil at our national database with 220 M we use the HL7 demographic approach. I agree this ADT death is different from

Re: Alive vs Dead

Following your Kafka reference, we can think of 'K' in the Castle, who probably wished he was dead On 05/01/2016 20:57, Bert Verhees wrote: I understand Thomas, just some arguments make me smile, like this one: "alive equals not-dead" I am glad I am just a programmer. ;-) ___

Re: Alive vs Dead

I understand Thomas, just some arguments make me smile, like this one: "alive equals not-dead" I am glad I am just a programmer. ;-) On 05-01-16 21:27, Thomas Beale wrote: Most of these are 'ontological' discussions, i.e. discussions about all the weird things that could possibly happen in re

Re: Alive vs Dead

Most of these are 'ontological' discussions, i.e. discussions about all the weird things that could possibly happen in reality. We need to remember that we are not generally trying to model all that complexity, but just the general structures for what needs to be written down at specific poin

Re: Alive vs Dead

Hi Tom > >- >hL7v2 messages indicate changes of state in things; and I think will >be mainly ADT oriented, i.e. correspond to the administrative change to the >openEHR demographic data >- FHIR's view is a query - meaning depends on what resource it is >coming from; it coul

Re: Alive vs Dead

‘Status’ (which needs some sort of archetype context) and the values are ‘Alive’ and ‘Deceased’ which cross the SNOMED CT hierarchies! We could just be very pragmatic and label the data element ‘Alive vs Dead?’ Curious problem – I thought there would be more on the internets J. Any wisdom you c

Re: Alive vs Dead

name ‘Status’ (which needs some sort of archetype context) and the values are ‘Alive’ and ‘Deceased’ which cross the SNOMED CT hierarchies! We could just be very pragmatic and label the data element ‘Alive vs Dead?’ Curious problem – I thought there would be more on the internets J.

RE: Alive vs Dead

om: openEHR-clinical [mailto:openehr-clinical-boun...@lists.openehr.org] On Behalf Of Heather Leslie Sent: Tuesday, January 5, 2016 6:16 PM To: For openEHR clinical discussions Subject: RE: Alive vs Dead Hi Heath, There are many things in the demographic archetypes that we seem to sometimes need i

Re: Alive vs Dead

common for the patient’s death status to be transmitted in a dedicated additional patient demographics segment ( other than HL7’s PD1 segment ), thus allowing for various forms of dead to be conveyed without breaching HL7 standards. In the above cases, the property of alive vs dead is very m

SV: Alive vs Dead

g] På vegne av Heath Frankel Sendt: 5. januar 2016 11:21 Til: For openEHR clinical discussions Emne: RE: Alive vs Dead Yep, they are certainly clinical and different to the original concepts you suggested (or at least the ones I interpreted that you were suggesting). I think Shinji's conce

RE: Alive vs Dead

From: Heather Leslie mailto:heather.les...@oceaninformatics.com>> Sent: Tuesday, January 5, 2016 6:55 PM Subject: RE: Alive vs Dead To: For openEHR clinical discussions mailto:openehr-clinical@lists.openehr.org>> Thanks Heath - death date, source of notification, location, certificat

Re: Alive vs Dead

the archetype of death >>> that contains clinically relevant data! >>> >>> * for querying - if the patient is not recorded as being known as >>> dead or deceased, then we assume either the patient is still alive or that >>> their status is unkn

RE: Alive vs Dead

uding contributing clinical factors. There is crossover between demographics and clinical. H From: openEHR-clinical [mailto:openehr-clinical-boun...@lists.openehr.org] On Behalf Of Heath Frankel Sent: Tuesday, 5 January 2016 7:04 PM To: For openEHR clinical discussions Subject: RE: Alive vs

Re: Alive vs Dead

dead. > > > > To add to the confusion, the requirements I am modelling uses the name > ‘Status’ (which needs some sort of archetype context) and the values are > ‘Alive’ and ‘Deceased’ which cross the SNOMED CT hierarchies! > > > > We could just be very pragmatic a

Re: Alive vs Dead

rchetype of death that >> contains clinically relevant data! >> >> * for querying - if the patient is not recorded as being known as >> dead or deceased, then we assume either the patient is still alive or that >> their status is unknown. >> >> I suspect t

RE: Alive vs Dead

-boun...@lists.openehr.org] On Behalf Of Ian McNicoll Sent: Tuesday, 5 January 2016 6:56 PM To: For openEHR clinical discussions Subject: Re: Alive vs Dead Hi Heather, I have been using an 'Anonymised person' archetype for this purpose, including a 'Vital status' element w

Re: Alive vs Dead

g known as > dead or deceased, then we assume either the patient is still alive or that > their status is unknown. > > I suspect that the reality is that many current systems do have an alive vs > dead status of some sort - would anyone like to confirm or deny? GNUmed models

RE: Alive vs Dead

means to do this. Regards Heath _ From: Heather Leslie mailto:heather.les...@oceaninformatics.com>> Sent: Tuesday, January 5, 2016 6:17 pm Subject: RE: Alive vs Dead To: For openEHR clinical discussions mailto:openehr-clinical@lists.openehr.org>> Hi

Re: Alive vs Dead

‘Living status’ was proposed on a forum, but seems a bit weird if they are > dead. > > > > To add to the confusion, the requirements I am modelling uses the name > ‘Status’ (which needs some sort of archetype context) and the values are > ‘Alive’ and ‘Deceased’ which cross the

RE: Alive vs Dead

Thanks Grahame, Knew someone would be able to provide a HL7 POV H From: openEHR-clinical [mailto:openehr-clinical-boun...@lists.openehr.org] On Behalf Of Grahame Grieve Sent: Tuesday, 5 January 2016 6:29 PM To: For openEHR clinical discussions Subject: Re: Alive vs Dead FHIR - either

RE: Alive vs Dead

-boun...@lists.openehr.org] On Behalf Of Heath Frankel Sent: Tuesday, 5 January 2016 6:37 PM To: For openEHR clinical discussions Subject: RE: Alive vs Dead Heather, The fact that a person is deceased is already represented in demographic archetypes. Regards Heath On Mon, Jan 4, 2016 at 11:20 PM

RE: Alive vs Dead

reality is that many current systems do have an alive vs dead status of some sort - would anyone like to confirm or deny? Cheers Heather From: openEHR-clinical [mailto:openehr-clinical-boun...@lists.openehr.org] On Behalf Of Heather Leslie Sent: Tuesday, 5 January 2016 5:44 PM To: For

Re: Alive vs Dead

- if the patient is not recorded as being known > as dead or deceased, then we assume either the patient is still alive or > that their status is unknown. > > > > I suspect that the reality is that many current systems do have an alive > vs dead status of some sort – would any

RE: Alive vs Dead

alive or that their status is unknown. I suspect that the reality is that many current systems do have an alive vs dead status of some sort - would anyone like to confirm or deny? Cheers Heather From: openEHR-clinical [mailto:openehr-clinical-boun...@lists.openehr.org] On Behalf Of Heather

Alive vs Dead

elling uses the name 'Status' (which needs some sort of archetype context) and the values are 'Alive' and 'Deceased' which cross the SNOMED CT hierarchies! We could just be very pragmatic and label the data element 'Alive vs Dead?' Curious problem - I though