This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Organizations interested in FHIR"

From HL7Wiki
Jump to navigation Jump to search
m (fixed links format)
Line 1: Line 1:
 
==Page Purpose==
 
==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.
+
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.
  
Note that making an entry on this page in no way obligates you to do anything! This is purely for informational purposes, and to provide useful contacts.
+
Note that making an entry on this page in no way obligates you to do anything! This is purely for informational purposes and to provide useful contacts.
 +
 
 +
==List of Organizations (in Alphabetical Order)==
  
==List of Organizations (Alphabetical Order)==
 
  
 
===AEGIS.net, Inc.===
 
===AEGIS.net, Inc.===
* Website: [http://www.aegis.net| AEGIS]
+
* Website: [http://www.aegis.net AEGIS]
 
* Contact: Mario Hyland [mailto:mario.hyland@aegis.net]
 
* Contact: Mario Hyland [mailto:mario.hyland@aegis.net]
 
* Interest: Testing FHIR - support FHIR develop and publish test cases and eventually published within the Developers Integration Lab (DIL). Working on IHE, and NwHIN within the AEGIS Integrated Ecosystem a synthetic community of Health Care organizations.
 
* Interest: Testing FHIR - support FHIR develop and publish test cases and eventually published within the Developers Integration Lab (DIL). Working on IHE, and NwHIN within the AEGIS Integrated Ecosystem a synthetic community of Health Care organizations.
 +
  
 
===Black Pear Software===
 
===Black Pear Software===
* Website: [http://www.blackpear.com]
+
* Website: [http://www.blackpear.com Black Pear]
 
* Contact Dunmail Hodkinson [mailto:dunmail@blackpear.com]
 
* Contact Dunmail Hodkinson [mailto:dunmail@blackpear.com]
 
* Interest: Creating FHIR adapters for UK GP systems. Contributing to OpenEyes Interoperability Kit.
 
* Interest: Creating FHIR adapters for UK GP systems. Contributing to OpenEyes Interoperability Kit.
 +
  
 
===CommonWell Health Alliance===
 
===CommonWell Health Alliance===
* Website: [http://www.commonwellalliance.org/services | CommonWell]
+
* Website: [http://www.commonwellalliance.org/services CommonWell]
 
* Contact: Peter Bernhardt [mailto:peter.bernhardt@relayhealth.com]
 
* Contact: Peter Bernhardt [mailto:peter.bernhardt@relayhealth.com]
 
* Interest: Using FHIR to support patient linking and matching services. CommonWell launched its interoperability services in January 2014 as part of its initial pilot rollout.
 
* Interest: Using FHIR to support patient linking and matching services. CommonWell launched its interoperability services in January 2014 as part of its initial pilot rollout.
 +
  
 
===Datuit (SafeIX Application Platform) ===
 
===Datuit (SafeIX Application Platform) ===
* Website: [http://www.datuit.com | datuit.com]
+
* Website: [http://www.datuit.com datuit.com]
 
* Contact: Gordon Raup [mailto:graup@datuit.com]
 
* Contact: Gordon Raup [mailto:graup@datuit.com]
 
* Interest: In the process of adding FHIR as one of the formats for apps to request and receive patient PHI from our SafeIX Application Platform (in addition to using our original SafeIX Fragments API).
 
* Interest: In the process of adding FHIR as one of the formats for apps to request and receive patient PHI from our SafeIX Application Platform (in addition to using our original SafeIX Fragments API).
 +
  
 
===DCA eHealth Solutions (Telstra Health)===
 
===DCA eHealth Solutions (Telstra Health)===
 
* Contact: Brian Postlethwaite [mailto:brianpos@optushome.com.au]
 
* Contact: Brian Postlethwaite [mailto:brianpos@optushome.com.au]
* Interest: Investigating suitability of fhir for interfacing between internal and external products.
+
* Interest: Investigating suitability of FHIR for interfacing between internal and external products.
 +
 
  
===GE Healhcare===
+
===GE Healthcare===
* Website: [http://www.gehealthcare.com| GE Healthcare]
+
* Website: [http://www.gehealthcare.com GE Healthcare]
 
* Contact: John Moehrke [mailto:john.moehrke@med.ge.com]
 
* Contact: John Moehrke [mailto:john.moehrke@med.ge.com]
 
* Interest: Using FHIR as a last-mile API to enable mHealth applications. Working with IHE on cross-development of IHE-MHD (XDS) and other.  
 
* Interest: Using FHIR as a last-mile API to enable mHealth applications. Working with IHE on cross-development of IHE-MHD (XDS) and other.  
 +
  
 
===Guys’ & St Thomas’ NHS Trust UK (Kings Health Partners)===
 
===Guys’ & St Thomas’ NHS Trust UK (Kings Health Partners)===
* Website: [http://www.guysandstthomas.nhs.uk/| http://www.guysandstthomas.nhs.uk/]
+
* Website: [http://www.guysandstthomas.nhs.uk/ http://www.guysandstthomas.nhs.uk/]
 
* Contact: Peter Swallow [mailto:Peter.Swallow@gstt.nhs.uk],  Gary McAllister [mailto:gary.mcallister@gstt.nhs.uk]
 
* Contact: Peter Swallow [mailto:Peter.Swallow@gstt.nhs.uk],  Gary McAllister [mailto:gary.mcallister@gstt.nhs.uk]
 
* Interest:  Project to share patient data between hospitals in London UK (Guys’ & St Thomas’ NHS Trust, Kings College Hospital and South London & Maudsley) currently in a Live Pilot. Starting to adopt FHIR.
 
* Interest:  Project to share patient data between hospitals in London UK (Guys’ & St Thomas’ NHS Trust, Kings College Hospital and South London & Maudsley) currently in a Live Pilot. Starting to adopt FHIR.
 +
  
 
===Healthcentrix===
 
===Healthcentrix===
* Website: [http://www.healthcentrix.com| www.healthcentrix.com]
+
* Website: [http://www.healthcentrix.com www.healthcentrix.com]
 
* Contact: José Olmo [mailto:jmolmo@healthcentrix.com]
 
* Contact: José Olmo [mailto:jmolmo@healthcentrix.com]
 
* Interest:Development of PHR and Patient Engagement solution based on FHIR, integrating with IHE-XDS, CDA and Direct protocol, and CDS/vMR system. Mobiles apps and Web Portals for patients and doctors uses FHIR server like their main services platform.
 
* Interest:Development of PHR and Patient Engagement solution based on FHIR, integrating with IHE-XDS, CDA and Direct protocol, and CDS/vMR system. Mobiles apps and Web Portals for patients and doctors uses FHIR server like their main services platform.
 +
  
 
===HL7 Colombia===
 
===HL7 Colombia===
* Website: [http://www.hl7.org.co| www.hl7.org.co]
+
* Website: [http://www.hl7.org.co www.hl7.org.co]
 
* Contact: Mario Cortés [mailto:mario.cortes@datasalud.net]
 
* Contact: Mario Cortés [mailto:mario.cortes@datasalud.net]
 
* Interest: Localization of FHIR specifications in Colombia and promotion for adoption at the HL7 user community in this country.
 
* Interest: Localization of FHIR specifications in Colombia and promotion for adoption at the HL7 user community in this country.
 +
 +
 +
===HL7 Systems & Services===
 +
* Website: [http://www.HL7.com.au/FHIR www.HL7.com.au/FHIR]
 +
* Contact: Admin@HL7.com.au [mailto:Admin@HL7.com.au]
 +
* Interest: Using FHIR as an example of ICT 'mainstreaming' eHealth interoperability technology.
 +
  
 
===IHE===
 
===IHE===
* Website: [http://www.ihe.net| www.ihe.net]
+
* Website: [http://www.ihe.net www.ihe.net]
 
* Contact: Keith Boone [mailto:keith.boone@ge.com]
 
* Contact: Keith Boone [mailto:keith.boone@ge.com]
 
* Interest: Integrating the Healthcare Enterprise has an interest, both in IT Infrastructure (in MHD and PDQ for Mobile, and in Patient Care Coordination (it is referenced in the DAF White Paper from PCC)
 
* Interest: Integrating the Healthcare Enterprise has an interest, both in IT Infrastructure (in MHD and PDQ for Mobile, and in Patient Care Coordination (it is referenced in the DAF White Paper from PCC)
 +
  
 
===Kyung Hee University Korea, Shaukat Khanum Memorial and Cancer Hospital Pakistan, School of Electrical Engineering and Computer Science, NUST Pakistan===
 
===Kyung Hee University Korea, Shaukat Khanum Memorial and Cancer Hospital Pakistan, School of Electrical Engineering and Computer Science, NUST Pakistan===
* Website: [http://uclab.khu.ac.kr/smartCDSS/ | Smart CDSS]
+
* Website: [http://uclab.khu.ac.kr/smartCDSS/ Smart CDSS]
 
* Contact: Maqbool Hussain [mailto:maqbool.hussain@seecs.edu.pk]
 
* Contact: Maqbool Hussain [mailto:maqbool.hussain@seecs.edu.pk]
 
* Interest: Building FHIR based framework that enables communication between clinical decision support system - called Smart CDSS - and hospital system from Shaukat Khanum Memorial Cancer Hospital for Head and Neck cancer department.
 
* Interest: Building FHIR based framework that enables communication between clinical decision support system - called Smart CDSS - and hospital system from Shaukat Khanum Memorial Cancer Hospital for Head and Neck cancer department.
Line 63: Line 80:
  
 
===Mohawk College===
 
===Mohawk College===
* Website: [http://www.mohawkcollege.ca/ideaworks/MEDIC.html| Mohawk College ideaworks]
+
* Website: [http://www.mohawkcollege.ca/ideaworks/MEDIC.html Mohawk College ideaworks]
 
* Contact: Duane Bender [mailto:duane.bender@mohawkcollege.ca]
 
* Contact: Duane Bender [mailto:duane.bender@mohawkcollege.ca]
 
* Interest: Building an Objective-C reference framework for FHIR implementations on IOS, expanding existing reference and testing implementations to include FHIR interfaces
 
* Interest: Building an Objective-C reference framework for FHIR implementations on IOS, expanding existing reference and testing implementations to include FHIR interfaces
Line 72: Line 89:
 
* Contact: Richard Kavanagh [mailto:richard.kavanagh@hscic.gov.uk]
 
* Contact: Richard Kavanagh [mailto:richard.kavanagh@hscic.gov.uk]
 
* Interest: Proof of concept to assess whether FHIR is suitable for the integration between suppliers and consumers of information for a national Renal care network.
 
* Interest: Proof of concept to assess whether FHIR is suitable for the integration between suppliers and consumers of information for a national Renal care network.
 +
  
 
===Nortal===
 
===Nortal===
Line 77: Line 95:
 
* Contact: Igor Bossenko [mailto:igor.bossenko@nortal.com]
 
* Contact: Igor Bossenko [mailto:igor.bossenko@nortal.com]
 
* Interest: Building NHR solutions using FHIR standard.
 
* Interest: Building NHR solutions using FHIR standard.
 +
  
 
===Open Mapping Software===
 
===Open Mapping Software===
Line 82: Line 101:
 
* 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===
 
===Oridashi===
Line 87: Line 107:
 
* Contact: Brett Esler [mailto:brett.esler@oridashi.com.au]
 
* 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.
 
* Interest: Implementing FHIR server interface for Australian primary care systems to support appropriate 3rd party clinical data access.
 +
  
 
===Orion Health===
 
===Orion Health===
Line 92: Line 113:
 
* Contact: David Hay [mailto:david.hay25@gmail.com]
 
* Contact: David Hay [mailto:david.hay25@gmail.com]
 
* Interest: Developed a general purpose server - 'Blaze' to support access to HIE data, as well as adding FHIR to the existing Integration Engine (Rhapsody).
 
* Interest: Developed a general purpose server - 'Blaze' to support access to HIE data, as well as adding FHIR to the existing Integration Engine (Rhapsody).
 +
  
 
=== Standards and Interoperability Framework ===
 
=== Standards and Interoperability Framework ===
Line 97: Line 119:
 
* Contact: Keith Boone [mailto:keith.boone@ge.com]
 
* Contact: Keith Boone [mailto:keith.boone@ge.com]
 
* Interest: Use of FHIR XDS Entry resource to support access to C-CDA and CCD documents.
 
* Interest: Use of FHIR XDS Entry resource to support access to C-CDA and CCD documents.
 +
  
 
=== Systems Made Simple, Inc. ===
 
=== Systems Made Simple, Inc. ===
Line 104: Line 127:
 
** Prime contractor for Veterans Health Administration for the development of the Integrated Electronic Health Record
 
** Prime contractor for Veterans Health Administration for the development of the Integrated Electronic Health Record
 
** Research and prototyping of FHIR capabilities.
 
** Research and prototyping of FHIR capabilities.
 +
  
 
===Thrasys, Inc===
 
===Thrasys, Inc===
Line 109: Line 133:
 
* Contact: Randy Belknap [mailto:randy.belknap@thrasys.com]
 
* Contact: Randy Belknap [mailto:randy.belknap@thrasys.com]
 
* Interest:  Use of FHIR for community based healthcare process integration (e.g. scheduling, care management)
 
* Interest:  Use of FHIR for community based healthcare process integration (e.g. scheduling, care management)
 +
  
 
===University of Western Sydney===
 
===University of Western Sydney===
 
* Website: [http://www.uws.edu.au/scem http://www.uws.edu.au/scem] School of Computing, Engineering and Mathematics
 
* Website: [http://www.uws.edu.au/scem http://www.uws.edu.au/scem] School of Computing, Engineering and Mathematics
 
* Contact: Klaus Veil [mailto:K.Veil@UWS.edu.au]
 
* Contact: Klaus Veil [mailto:K.Veil@UWS.edu.au]
* Interest: Research & Student Projects.  In late 2012 a team of five students created a browser-based proof-of-concept FHIR hospital information system implementation.  The results will be presented in a paper at the 2013 Health Informatics Conference in Adelaide, Australia.
+
* Interest: Research & Student Projects.  In late 2012 a team of five students created a browser-based proof-of-concept FHIR hospital information system implementation.  The results were presented in a paper at the 2013 Health Informatics Conference in Adelaide, Australia.
 +
 
  
 
===Veterans Health Administration - Integrated Electronic Health Record===
 
===Veterans Health Administration - Integrated Electronic Health Record===
Line 119: Line 145:
 
* Contact: Seth Rylan Gainey [mailto:seth.gainey@navy.mil], Michael Ramirez [mailto:michael.a.ramirez@navy.mil]
 
* Contact: Seth Rylan Gainey [mailto:seth.gainey@navy.mil], Michael Ramirez [mailto:michael.a.ramirez@navy.mil]
 
* Interest: VA/DoD interoperablity. A proof-of-concept and research effort directed towards the goal of  [http://www.defense.gov/news/EHRDoDVAFactSheet.pdf Integrated Electronic Health Record (iEHR)] to support seamless integration of VA/DoD EHR systems by using FHIR as a common clinical model.
 
* Interest: VA/DoD interoperablity. A proof-of-concept and research effort directed towards the goal of  [http://www.defense.gov/news/EHRDoDVAFactSheet.pdf Integrated Electronic Health Record (iEHR)] to support seamless integration of VA/DoD EHR systems by using FHIR as a common clinical model.
 +
  
 
===West Health Institute===
 
===West Health Institute===
 
* Website: [http://www.westhealth.org http://www.westhealth.org]
 
* Website: [http://www.westhealth.org http://www.westhealth.org]
* Contact: Michael Ekaireb [mailto:mekaireb@westhealth.org|mailto:mekaireb@westhealth.org]
+
* Contact: Michael Ekaireb [mailto:mekaireb@westhealth.org]
* Interest: Interfacing a PCA infusion pump simulator that implements ISO/IEEE 11073 DIM, with a HL7 Fhir server via an Observation Reporter.
+
* Interest: Interfacing a PCA infusion pump simulator that implements ISO/IEEE 11073 DIM, with a HL7 FHIR server via an Observation Reporter.

Revision as of 13:22, 1 May 2014

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.

Note that making an entry on this page in no way obligates you to do anything! This is purely for informational purposes and to provide useful contacts.

List of Organizations (in Alphabetical Order)

AEGIS.net, Inc.

  • Website: AEGIS
  • Contact: Mario Hyland [1]
  • Interest: Testing FHIR - support FHIR develop and publish test cases and eventually published within the Developers Integration Lab (DIL). Working on IHE, and NwHIN within the AEGIS Integrated Ecosystem a synthetic community of Health Care organizations.


Black Pear Software

  • Website: Black Pear
  • Contact Dunmail Hodkinson [2]
  • Interest: Creating FHIR adapters for UK GP systems. Contributing to OpenEyes Interoperability Kit.


CommonWell Health Alliance

  • Website: CommonWell
  • Contact: Peter Bernhardt [3]
  • Interest: Using FHIR to support patient linking and matching services. CommonWell launched its interoperability services in January 2014 as part of its initial pilot rollout.


Datuit (SafeIX Application Platform)

  • Website: datuit.com
  • Contact: Gordon Raup [4]
  • Interest: In the process of adding FHIR as one of the formats for apps to request and receive patient PHI from our SafeIX Application Platform (in addition to using our original SafeIX Fragments API).


DCA eHealth Solutions (Telstra Health)

  • Contact: Brian Postlethwaite [5]
  • Interest: Investigating suitability of FHIR for interfacing between internal and external products.


GE Healthcare

  • Website: GE Healthcare
  • Contact: John Moehrke [6]
  • Interest: Using FHIR as a last-mile API to enable mHealth applications. Working with IHE on cross-development of IHE-MHD (XDS) and other.


Guys’ & St Thomas’ NHS Trust UK (Kings Health Partners)

  • Website: http://www.guysandstthomas.nhs.uk/
  • Contact: Peter Swallow [7], Gary McAllister [8]
  • Interest: Project to share patient data between hospitals in London UK (Guys’ & St Thomas’ NHS Trust, Kings College Hospital and South London & Maudsley) currently in a Live Pilot. Starting to adopt FHIR.


Healthcentrix

  • Website: www.healthcentrix.com
  • Contact: José Olmo [9]
  • Interest:Development of PHR and Patient Engagement solution based on FHIR, integrating with IHE-XDS, CDA and Direct protocol, and CDS/vMR system. Mobiles apps and Web Portals for patients and doctors uses FHIR server like their main services platform.


HL7 Colombia

  • Website: www.hl7.org.co
  • Contact: Mario Cortés [10]
  • Interest: Localization of FHIR specifications in Colombia and promotion for adoption at the HL7 user community in this country.


HL7 Systems & Services

  • Website: www.HL7.com.au/FHIR
  • Contact: Admin@HL7.com.au [11]
  • Interest: Using FHIR as an example of ICT 'mainstreaming' eHealth interoperability technology.


IHE

  • Website: www.ihe.net
  • Contact: Keith Boone [12]
  • Interest: Integrating the Healthcare Enterprise has an interest, both in IT Infrastructure (in MHD and PDQ for Mobile, and in Patient Care Coordination (it is referenced in the DAF White Paper from PCC)


Kyung Hee University Korea, Shaukat Khanum Memorial and Cancer Hospital Pakistan, School of Electrical Engineering and Computer Science, NUST Pakistan

  • Website: Smart CDSS
  • Contact: Maqbool Hussain [13]
  • Interest: Building FHIR based framework that enables communication between clinical decision support system - called Smart CDSS - and hospital system from Shaukat Khanum Memorial Cancer Hospital for Head and Neck cancer department.


Mohawk College

  • Website: Mohawk College ideaworks
  • Contact: Duane Bender [14]
  • Interest: Building an Objective-C reference framework for FHIR implementations on IOS, expanding existing reference and testing implementations to include FHIR interfaces


NHS England

  • Website: n/a
  • Contact: Richard Kavanagh [15]
  • Interest: Proof of concept to assess whether FHIR is suitable for the integration between suppliers and consumers of information for a national Renal care network.


Nortal


Open Mapping Software

  • Website: http://www.OpenMapSW.com
  • Contact: Robert Worden [17]
  • 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 [18]
  • 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 [19]
  • Interest: Developed a general purpose server - 'Blaze' to support access to HIE data, as well as adding FHIR to the existing Integration Engine (Rhapsody).


Standards and Interoperability Framework


Systems Made Simple, Inc.

  • Website: http://www.systemsmadesimple.com
  • Contact: Gina Gallagher [21]
  • Interests:
    • Prime contractor for Veterans Health Administration for the development of the Integrated Electronic Health Record
    • Research and prototyping of FHIR capabilities.


Thrasys, Inc

  • Website: http://www.thrasys.com
  • Contact: Randy Belknap [22]
  • Interest: Use of FHIR for community based healthcare process integration (e.g. scheduling, care management)


University of Western Sydney

  • Website: http://www.uws.edu.au/scem School of Computing, Engineering and Mathematics
  • Contact: Klaus Veil [23]
  • Interest: Research & Student Projects. In late 2012 a team of five students created a browser-based proof-of-concept FHIR hospital information system implementation. The results were presented in a paper at the 2013 Health Informatics Conference in Adelaide, Australia.


Veterans Health Administration - Integrated Electronic Health Record


West Health Institute

  • Website: http://www.westhealth.org
  • Contact: Michael Ekaireb [26]
  • Interest: Interfacing a PCA infusion pump simulator that implements ISO/IEEE 11073 DIM, with a HL7 FHIR server via an Observation Reporter.