Interest in FHIR?

Hello all,
There is a RESTful API that is gaining some popularity called FHIR (Fast Healthcare Interoperability Resources). There are three resources:

I think if would be a useful thing to:

Does anyone want to work on this? I have setup a repository on github:

https://github.com/openhie/openinfoman-fhir

to hold the stored functions and FHIR adapter. It is empty at the moment, but hopefully we can start getting it filled soon.

Cheers,
-carl

PS Sorry for the cross-posting.

Hi Charles,

Just a quick update…. we now have ability to map the FHIR location and practitioner resources. Note that there are some questions as to how best to map these from the CSD entities. As an example:

There are some more things that need to be done:

  • Add the XML representation of the FHIR organization resource
  • Add in the search parameters for location and facility
  • Create the JSON output for the FHIR resources
  • Cross link the practitioner organization and location resource (probably need to add some metadata to the existing stored functions)
  • Discuss with FHIR group on the best mapping

Cheers,
-carl

···

On Wed, Jul 30, 2014 at 3:23 PM, Carl Leitner litlfred@gmail.com wrote:

Hello all,
There is a RESTful API that is gaining some popularity called FHIR (Fast Healthcare Interoperability Resources). There are three resources:

I think if would be a useful thing to:

Does anyone want to work on this? I have setup a repository on github:

https://github.com/openhie/openinfoman-fhir

to hold the stored functions and FHIR adapter. It is empty at the moment, but hopefully we can start getting it filled soon.

Cheers,
-carl

PS Sorry for the cross-posting.

You received this message because you are subscribed to the Google Groups “ihe-csd-implementors” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ihe-csd-implementors+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Hi Carl,

I think the Facility Registry community would be interested to see how we can support some of the todo list here as it pertains to location specifically. I will take it to the community and explore how we might move forward. Thanks for sharing this thread though, I remember we had an initial conversation at the strategy meetings for OpenHIE this past winter right when FHIR came out, but we hadn’t progressed very far. Perhaps we should consider this as an item to potentially include in our OHIE architecture roadmaps?

Best,

Scott

···

On Thu, Jul 31, 2014 at 9:41 AM, Charles Chigoriwa cchigoriwa@gmail.com wrote:

Hi Carl

It is encouraging to note that you have started working on CSD >FHIR mapping. I guess we will add more code as our understanding of FHIR gets better.

Discussing with FHIR group will be extremely helpful in the mapping part. I think we need to be part of the FHIR group.

Many thanks Carl for the efforts.

Regards

Charles

You received this message because you are subscribed to the Google Groups “ihe-csd-implementors” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ihe-csd-implementors+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


Scott Teesdale
Project Manager - InSTEDD

Email: steesdale@instedd.org

Skype: scott.teesdale

Social: Twitter / LinkedIn

On Thu, Jul 31, 2014 at 3:11 PM, Carl Leitner litlfred@gmail.com wrote:

Hi Charles,
Just a quick update…. we now have ability to map the FHIR location and practitioner resources. Note that there are some questions as to how best to map these from the CSD entities. As an example:

There are some more things that need to be done:

  • Add the XML representation of the FHIR organization resource
  • Add in the search parameters for location and facility
  • Create the JSON output for the FHIR resources
  • Cross link the practitioner organization and location resource (probably need to add some metadata to the existing stored functions)
  • Discuss with FHIR group on the best mapping

Cheers,
-carl

On Jul 31, 2014, at 4:24 AM, Charles Chigoriwa cchigoriwa@gmail.com wrote:

Hi Carl

I have just taken a bird`s eye view of FHIR and it seems quite interesting. It is vital to see our CSD speaking fluent FHIR. I therefore assign this work to my team (HITRAC) to work on adding flesh to openinfoman-fhir.

I think we can have a conference call for this if you have time on your side.

Regards

Charles

On Wed, Jul 30, 2014 at 3:23 PM, Carl Leitner litlfred@gmail.com wrote:

Hello all,
There is a RESTful API that is gaining some popularity called FHIR (Fast Healthcare Interoperability Resources). There are three resources:

I think if would be a useful thing to:

Does anyone want to work on this? I have setup a repository on github:

https://github.com/openhie/openinfoman-fhir

to hold the stored functions and FHIR adapter. It is empty at the moment, but hopefully we can start getting it filled soon.

Cheers,
-carl

PS Sorry for the cross-posting.

You received this message because you are subscribed to the Google Groups “ihe-csd-implementors” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ihe-csd-implementors+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Hi Scott,

Sounds good.
Cheers,
-carl

···

On Thu, Jul 31, 2014 at 9:41 AM, Charles Chigoriwa cchigoriwa@gmail.com wrote:

Hi Carl

It is encouraging to note that you have started working on CSD >FHIR mapping. I guess we will add more code as our understanding of FHIR gets better.

Discussing with FHIR group will be extremely helpful in the mapping part. I think we need to be part of the FHIR group.

Many thanks Carl for the efforts.

Regards

Charles

You received this message because you are subscribed to the Google Groups “ihe-csd-implementors” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ihe-csd-implementors+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


Scott Teesdale
Project Manager - InSTEDD

Email: steesdale@instedd.org

Skype: scott.teesdale

Social: Twitter / LinkedIn

On Thu, Jul 31, 2014 at 3:11 PM, Carl Leitner litlfred@gmail.com wrote:

Hi Charles,
Just a quick update…. we now have ability to map the FHIR location and practitioner resources. Note that there are some questions as to how best to map these from the CSD entities. As an example:

There are some more things that need to be done:

  • Add the XML representation of the FHIR organization resource
  • Add in the search parameters for location and facility
  • Create the JSON output for the FHIR resources
  • Cross link the practitioner organization and location resource (probably need to add some metadata to the existing stored functions)
  • Discuss with FHIR group on the best mapping

Cheers,
-carl

On Jul 31, 2014, at 4:24 AM, Charles Chigoriwa cchigoriwa@gmail.com wrote:

Hi Carl

I have just taken a bird`s eye view of FHIR and it seems quite interesting. It is vital to see our CSD speaking fluent FHIR. I therefore assign this work to my team (HITRAC) to work on adding flesh to openinfoman-fhir.

I think we can have a conference call for this if you have time on your side.

Regards

Charles

On Wed, Jul 30, 2014 at 3:23 PM, Carl Leitner litlfred@gmail.com wrote:

Hello all,
There is a RESTful API that is gaining some popularity called FHIR (Fast Healthcare Interoperability Resources). There are three resources:

I think if would be a useful thing to:

Does anyone want to work on this? I have setup a repository on github:

https://github.com/openhie/openinfoman-fhir

to hold the stored functions and FHIR adapter. It is empty at the moment, but hopefully we can start getting it filled soon.

Cheers,
-carl

PS Sorry for the cross-posting.

You received this message because you are subscribed to the Google Groups “ihe-csd-implementors” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ihe-csd-implementors+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.