This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Organizations interested in FHIR"
Jump to navigation
Jump to search
Brett.esler (talk | contribs) |
|||
| Line 9: | Line 9: | ||
* Contact: Robert Worden [mailto:robert@OpenMapSW.com] | * Contact: Robert Worden [mailto:robert@OpenMapSW.com] | ||
* Interest: Developing open source tools for mapping and transforming between FHIR and other healthcare representations - inc. V2, CDA, and RDBMS. FHIR and data quality. | * Interest: Developing open source tools for mapping and transforming between FHIR and other healthcare representations - inc. V2, CDA, and RDBMS. FHIR and data quality. | ||
| + | |||
| + | ===Oridashi=== | ||
| + | * Website: : [http://www.oridashi.com/fhir http://www.oridashi.com/fhir] | ||
| + | * Contact: Brett Esler [mailto:brett.esler@oridashi.com.au] | ||
| + | * Interest: Implementing FHIR server interface for Australian primary care systems to support appropriate 3rd party clinical data access. | ||
===Orion health=== | ===Orion health=== | ||
Revision as of 22:36, 3 June 2013
Contents
Page Purpose
This page is a location where organizations that have an interest in FHIR can register that interest. This includes both vendors implementing or intending to implement FHIR based interfaces, and potential users of those services.
List of Organizations (Alphabetical Order)
Open Mapping Software
- Website: : http://www.OpenMapSW.com
- Contact: Robert Worden [1]
- Interest: Developing open source tools for mapping and transforming between FHIR and other healthcare representations - inc. V2, CDA, and RDBMS. FHIR and data quality.
Oridashi
- Website: : http://www.oridashi.com/fhir
- Contact: Brett Esler [2]
- Interest: Implementing FHIR server interface for Australian primary care systems to support appropriate 3rd party clinical data access.
Orion health
- Website: : http://www.orionhealth.com
- Contact: David Hay [3]
- Interest: Planning to develop a general 'FHIR Engine' to support access to HIE data, as well as adding FHIR to the existing Integration Engine (Rhapsody).
