Comments for Health Intersections Pty Ltd http://www.healthintersections.com.au Consulting Company for Grahame Grieve Mon, 14 May 2012 00:37:37 +0000 hourly 1 http://wordpress.org/?v=3.3.2 Comment on Updated list of FHIR Sessions at Vancouver WGM by Grahame Grieve http://www.healthintersections.com.au/?p=913#comment-2521 Grahame Grieve Mon, 14 May 2012 00:37:37 +0000 http://www.healthintersections.com.au/?p=913#comment-2521 Advice of more sessions: * MnM Q1 will include FHIR SAIF IG * RIMBAA Mon. Q2 will include CIMI & FHIR compare/contrast * Tuesday Q3: PA FHIR next steps Advice of more sessions:

* MnM Q1 will include FHIR SAIF IG
* RIMBAA Mon. Q2 will include CIMI & FHIR compare/contrast
* Tuesday Q3: PA FHIR next steps

]]> Comment on Updated list of FHIR Sessions at Vancouver WGM by Grahame Grieve http://www.healthintersections.com.au/?p=913#comment-2520 Grahame Grieve Sun, 13 May 2012 21:48:27 +0000 http://www.healthintersections.com.au/?p=913#comment-2520 wow, a change already - and also methodology and SAIF implementation guide will be discussed MnM Mon Q1 wow, a change already – and also methodology and SAIF implementation guide will be discussed MnM Mon Q1

]]> Comment on HL7 Progress Report by Grahame Grieve http://www.healthintersections.com.au/?p=899#comment-2498 Grahame Grieve Mon, 07 May 2012 14:02:41 +0000 http://www.healthintersections.com.au/?p=899#comment-2498 Hi Andrew I think that while it's rich, and *can* be templated, in practice there is no accepted methodology for that. And given how hard it seems to be for everyone to get v2 right (something you frequently comment on), that's a step too far. But I agree about v3 constraints. Hi Andrew

I think that while it’s rich, and *can* be templated, in practice there is no accepted methodology for that. And given how hard it seems to be for everyone to get v2 right (something you frequently comment on), that’s a step too far.

But I agree about v3 constraints.

]]> Comment on HL7 Progress Report by Andrew McIntyre http://www.healthintersections.com.au/?p=899#comment-2497 Andrew McIntyre Mon, 07 May 2012 13:24:33 +0000 http://www.healthintersections.com.au/?p=899#comment-2497 "Clinical information is delegated to a tree of name-value pairs with no good way to control them" Isn't that what the semantic web actually is? That tree is semantically rich and can be templated. That actually gives you good administration support that V2 has and extendable semantics much like OWL, with backward compatability with display orientated consumers. Thats not a bad place to be in my book. The issue is constraints, V2 and V3 place them in different places, but in the end the V2 solution actually works better in software and avoids a lot of code duplication for things that are almost the same but not quite(thats V3). “Clinical information is delegated to a tree of name-value pairs with no good way to control them”

Isn’t that what the semantic web actually is? That tree is semantically rich and can be templated. That actually gives you good administration support that V2 has and extendable semantics much like OWL, with backward compatability with display orientated consumers. Thats not a bad place to be in my book.

The issue is constraints, V2 and V3 place them in different places, but in the end the V2 solution actually works better in software and avoids a lot of code duplication for things that are almost the same but not quite(thats V3).

]]> Comment on Question: Interpreter Needed flag in HL7 v2 by Grahame http://www.healthintersections.com.au/?p=885#comment-2475 Grahame Tue, 01 May 2012 23:08:20 +0000 http://www.healthintersections.com.au/?p=885#comment-2475 Well. If, yes . But that assumes that the underlying record keeping and clerical systems support even this simple case. Well. If, yes . But that assumes that the underlying record keeping and clerical systems support even this simple case.

]]> Comment on Question: Interpreter Needed flag in HL7 v2 by Colin http://www.healthintersections.com.au/?p=885#comment-2474 Colin Tue, 01 May 2012 23:05:20 +0000 http://www.healthintersections.com.au/?p=885#comment-2474 interpreter needed for which language? If the patient is aboriginal Australian and the GP speaks their language or the patient is in the country of their native language and a GP there has access to the data, an interpreter is not required (but maybe for the GP to read the record!) It would be better to pass the primary language and "English not spoken". interpreter needed for which language?
If the patient is aboriginal Australian and the GP speaks their language or the patient is in the country of their native language and a GP there has access to the data, an interpreter is not required (but maybe for the GP to read the record!)
It would be better to pass the primary language and “English not spoken”.

]]> Comment on FHIR Licensing Update by Grahame Grieve http://www.healthintersections.com.au/?p=868#comment-2364 Grahame Grieve Tue, 03 Apr 2012 04:01:24 +0000 http://www.healthintersections.com.au/?p=868#comment-2364 Just to add another note in response to private email this generated - HL7 membership is cheap compared to equivalent W3C membership. But you get different outcomes from membership of the W3C than you do for joining HL7. Just to add another note in response to private email this generated – HL7 membership is cheap compared to equivalent W3C membership. But you get different outcomes from membership of the W3C than you do for joining HL7.

]]> Comment on FHIR Licensing Update by Grahame Grieve http://www.healthintersections.com.au/?p=868#comment-2363 Grahame Grieve Tue, 03 Apr 2012 03:58:42 +0000 http://www.healthintersections.com.au/?p=868#comment-2363 Right. To be clear, the normative release wouldn't retrospectively become encumbered by a license fee, only future versions. This is a get out of jail card for HL7 in case it turns out to be a disaster. if FHIR adoption is widespread, then future versions won't be made encumbered. Right. To be clear, the normative release wouldn’t retrospectively become encumbered by a license fee, only future versions. This is a get out of jail card for HL7 in case it turns out to be a disaster. if FHIR adoption is widespread, then future versions won’t be made encumbered.

]]> Comment on FHIR Licensing Update by Jim McCusker http://www.healthintersections.com.au/?p=868#comment-2360 Jim McCusker Mon, 02 Apr 2012 15:58:28 +0000 http://www.healthintersections.com.au/?p=868#comment-2360 If I were an implementer I would worry that "The agreement would hold until the first normative publication of FHIR, after which the impact of this would be reassessed and other models could be considered" means that there is a risk FHIR would end up closed anyway. If I put the thousands of hours in needed to make a working FHIR-based mobile app, and THEN I find out that I have to pay royalties, then I might think twice about adopting it. If I were an implementer I would worry that “The agreement would hold until the first normative publication of FHIR, after which the impact of this would be reassessed and other models could be considered” means that there is a risk FHIR would end up closed anyway. If I put the thousands of hours in needed to make a working FHIR-based mobile app, and THEN I find out that I have to pay royalties, then I might think twice about adopting it.

]]> Comment on Question: OIDs for v2 tables by Grahame Grieve http://www.healthintersections.com.au/?p=863#comment-2354 Grahame Grieve Mon, 02 Apr 2012 03:27:42 +0000 http://www.healthintersections.com.au/?p=863#comment-2354 "Even more useful to have the content of those HL7-managed tables available for download" - in the standard. “Even more useful to have the content of those HL7-managed tables available for download” – in the standard.

]]>