-technical at lists.openehr.org
*Subject:* Re: openEHR / FHIR data types cross analysis
** **
Actually, Eiffel has nothing to do with it (I wrote my own date/time
libraries based on ISO 8601 semantics). What I am influenced by is what I
see in CKM and other repositories.
openEHR CKM
at lists.openehr.org [mailto:
openehr-technical-bounces at lists.openehr.org] *On Behalf Of *Thomas Beale
*Sent:* Monday, 19 March 2012 8:18 AM
*To:* openehr-technical at lists.openehr.org
*Subject:* Re: openEHR / FHIR data types cross analysis
** **
Actually, Eiffel has nothing to do with it (I wrote
I just wasn't thinking what I wrote this. In FHIR, a boolean data
type, primitive, is a
type that can be used in models an is exactly equivalent to DV_BOOLEAN.
but isn't the problem that it doesn't inherit from some DATA_VALUE parent
type (Any in HL7 data types)? How can it be one of the
-bounces at lists.openehr.org [mailto:openehr-
technical-bounces at lists.openehr.org] On Behalf Of Grahame Grieve
Sent: Sunday, 18 March 2012 11:50 PM
To: For openEHR technical discussions
Subject: Re: openEHR / FHIR data types cross analysis
I just wasn't thinking what I wrote this. In FHIR
FHIR has no such restriction - elements must have a type of one or more
of the defined types, either primitive or complex
ok, but how do w write a normal statically typed classes in Java or C# to
deal with that?
Many boolean elements are mandatory - they map straight onto the primitive
: Re: openEHR / FHIR data types cross analysis
I just wasn't thinking what I wrote this. In FHIR, a boolean data
type, primitive, is a type that can be used in models an is
exactly equivalent to DV_BOOLEAN.
but isn't the problem that it doesn't inherit from some DATA_VALUE
parent
Grieve
Sent: Monday, 19 March 2012 8:16 AM
To: For openEHR technical discussions
Subject: Re: openEHR / FHIR data types cross analysis
Hi Sam
Actually, this has come up in a couple of other places. The FHIR data
types are defined for use within the FHIR framework. There's two very
important
Sorry about the Eiffel slur J
Cheers, Sam
From: openehr-technical-boun...@lists.openehr.org
[mailto:openehr-technical-bounces at lists.openehr.org] On Behalf Of Thomas
Beale
Sent: Monday, 19 March 2012 8:18 AM
To: openehr-technical at lists.openehr.org
Subject: Re: openEHR / FHIR data types
Couple of quick reactions - you need to talk to clinical modellers to get a
better response (maybe post on clinical list)...
um, maybe. but most are representational questions, not questions of
meaning, I think.
* DV_BOOLEAN - maps a to a coded value with true/false. True and false are
On 17/03/2012 22:18, Grahame Grieve wrote:
Couple of quick reactions - you need to talk to clinical modellers to get a
better response (maybe post on clinical list)...
um, maybe. but most are representational questions, not questions of
meaning, I think.
* DV_BOOLEAN - maps a to a coded
On 18/03/2012 12:49, Grahame Grieve wrote:
I just wasn't thinking what I wrote this. In FHIR, a boolean data
type, primitive, is a
type that can be used in models an is exactly equivalent to DV_BOOLEAN.
but isn't the problem that it doesn't inherit from some DATA_VALUE parent
type (Any in HL7
On 11/03/2012 09:43, Thomas Beale wrote:
Well, this is the HL7 modelling mentality, trying to create a data
type or class with all possible attributes, some of which can be
removed in some subclass. This is bad modelling, we should not be
doing it. I'm talking about interfaces here,
HI
I have responded to the comments in the wiki.
Generally, the FHIR data types are not purely for computation; they contain
some features related to display.
Some further responses here:
* DV_BOOLEAN - maps a to a coded value with true/false. True and false are
defined codes. I'd be
Couple of quick reactions - you need to talk to clinical modellers to
get a better response (maybe post on clinical list)...
On 10/03/2012 19:34, Grahame Grieve wrote:
HI
I have responded to the comments in the wiki.
Generally, the FHIR data types are not purely for computation; they
-bounces at openehr.org] On Behalf Of Thomas Beale
Sent: Monday, 30 January 2012 4:27 AM
To: Openehr-Technical
Subject: openEHR / FHIR data types cross analysis
I have started a gap analysis of the openEHR and FHIR data types
http://www.openehr.org/wiki/display/stds/FHIR+-+openEHR+Data+Types
On 30/01/2012 20:56, Sam Heard wrote:
Thanks Tom for this useful work.
A couple of thoughts:
1)It might be worth explaining the need for DV_BOOLEAN -- and not just
use Boolean
The openEHR RM, like 13606, CDA and most other such models has a generic
structure part for building trees of
Again, FYI. If you would like help in doing the cross ref. with MLHIM
let me know. However, this might be a good project for Sergio???
--Tim
On Sun, Jan 29, 2012 at 10:26, Thomas Beale
thomas.beale at oceaninformatics.com wrote:
I have started a gap analysis of the openEHR and FHIR data
Apologies, this was not intended for the mailing list.
On Mon, Jan 30, 2012 at 19:39, Timothy Cook timothywayne.cook at gmail.com
wrote:
Again, FYI. ?If you would like help in doing the cross ref. with MLHIM
let me know. ?However, this might be a good project for Sergio???
--Tim
On Sun,
18 matches
Mail list logo
