Friday, October 04, 2013
Breath of Fresh Air for FIHR
From Clinical Statements Task Force
On Fri, Oct 4, 2013 at 9:05 AM, Lloyd McKenzie
... While you *could* pursue a RIM-based repository for FHIR, it's hard to imagine why you'd want to and the presence of extensions would make it quite complicated.
On Thu, Oct 3, 2013 at 8:20 PM, Grahame Grieve
> it's hard to imagine why you'd want to
I find it quite easy - because you've already invested a lot of work in one.
And there are a number of people who already have. I invite all of you to help work on the RIM Mappings for the existing resources that are of interest to you - they've fallen behind, and fundamentally this is driven by a lack of implementer interest in them.
On 4 October 2013 03:25:36 CEST Bob Dolin
To: Lloyd McKenzie
, Grahame Grieve
A bit late to the discussion.
Lloyd, are you asking why we should be mapping FHIR resources to the RIM?
On Thursday, October 03, 2013 6:23 PM Lloyd McKenzie wrote:
To: Grahame GrieveCc: Rik Smithies; Zel, M van der; Haarbrandt, Birger; RIMBAA; Clinical Statements Task Force
If you have one already, then yes it may make sense to use it. However, if you're coming at the problem new ..., I'm not sure what using a RIM back end for FHIR would buy you. Not saying it wouldn't buy you anything, just that I can't see it.