This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Organizations interested in FHIR"

From HL7Wiki
Jump to navigation Jump to search
(UWS)
 
(105 intermediate revisions by 48 users not shown)
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.
 +
 
 +
National FHIR Project can be registered [http://wiki.hl7.org/index.php?title=National_FHIR_Projects here]
 +
 
 +
==List of Organizations (in Alphabetical Order)==
 +
 
 +
===AEGIS.net, Inc.===
 +
* Website: [http://www.aegis.net AEGIS]
 +
* Contact: Mario Hyland [mailto:mario.hyland@aegis.net]
 +
* Interest: Testing FHIR - support FHIR develop and publish test cases and eventually published within the [https://touchstone.aegis.net/touchstone Touchstone Project] a Developers Integration Lab (DIL) initiative. Working on IHE, HL7, NwHIN and FHIR within the AEGIS Integrated Ecosystem a synthetic testing community of Health Care organizations.
 +
 
 +
 
 +
===Allscripts===
 +
* Website: [http://www.Allscripts.com Allscripts]
 +
* Contact: Jeffrey Danford [mailto:jeffrey.danford@allscripts.com]
 +
* Interest: Allscripts is committed to providing a FHIR API service that supports SMART on FHIR and mobile apps and Precision Medicine Initiative as part of the Allscripts Open Platform and the Allscripts Developer Program. For more information please visit http://developer.allscripts.com.
 +
 
 +
 
 +
===Alten Calsoft Labs===
 +
* Website: [http://www.altencalsoftlabs.com Alten Calsoft Labs]
 +
* Contact: Sandeep Vyas [mailto:sandeep.vyas@altencalsoftlabs.com]
 +
* Interest: Developing tools to help FHIR implementation to integrate systems. For more information please visit :[http://www.altencalsoftlabs.com/solutions/healthcare/fhir-implementation-framework/ FHIR implementation]
 +
 
 +
===ART-DECOR===
 +
* Website: [http://art-decor.org ART-DECOR]
 +
* Contact: Kai Heitmann [mailto:support@art-decor.org]
 +
* Interest: Profiling FHIR, Terminology, Testing FHIR - support FHIR development and publish implementation guidance at every level international, national, or regional.
 +
 
 +
 
 +
===Black Pear Software===
 +
* Website: [http://www.blackpear.com Black Pear]
 +
* Contact Dunmail Hodkinson [mailto:dunmail@blackpear.com]
 +
* Interest: Creating FHIR adapters for UK GP systems. Contributing to OpenEyes Interoperability Kit.
 +
 
 +
===By Light Professional IT Consulting===
 +
* Website: [http://bylight.com By Light]
 +
* Contact John Moehrke [mailto:John.Moehrke@bylight.com]
 +
* Interest: Healthcare IT Consulting services. Currently sub-contractor to VHA for Interoperability, eHEX, Direct, CDA, and FHIR services.
 +
 
 +
===Caristix===
 +
* Website: [http://www.caristix.com Caristix]
 +
* Contact: Jean-Luc Morin [mailto:jeanluc.morin@caristix.com]
 +
* Interest: Developing tools to help FHIR implementation to integrate systems.
 +
 
 +
 
 +
===Cerner===
 +
* Website: [http://www.cerner.com Cerner]
 +
* Contact: David McCallie [mailto:dmccallie@cerner.com]
 +
* Interest: The SMART on FHIR "App plugin" architecture; HIE extensions; SOA support for back-end integration services.
 +
 
 +
 
 +
=== Cognizant Technology Solutions ===
 +
* Website: [http://www.cognizant.com/healthcare Cognizant Technology Solutions]
 +
* Contact: Doug DeShazo [mailto:douglas.deshazo@cognizant.com]
 +
* Interest: Use of FHIR server in support of HIE, FHIR resources for XDS, CCDA, CCD and FHIR for mobile applications (IHE MHD TF Supplement).
 +
 
 +
 
 +
===CommonWell Health Alliance===
 +
* Website: [http://www.commonwellalliance.org/services CommonWell]
 +
* 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.
 +
 
 +
 
 +
===Corepoint Health===
 +
* Website: [http://corepointhealth.com/products/corepoint-integration-engine Corepoint Integration Engine]
 +
* Contact: Dave Shaver [mailto:dave.shaver_REMOVE_THIS@corepointhealth.com]
 +
* Interest: Supporting FHIR within comprehensive, #1-in-KLAS integration engine; support for both client and server roles, HL7 V2/CDA to FHIR mapping, and FHIR-to-FHIR mapping.
 +
 
 +
 
 +
===Datuit (SafeIX Application Platform) ===
 +
* Website: [http://www.datuit.com 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).
 +
 
 +
 
 +
=== Dräger ===
 +
* Website: [http://www.draeger.com draeger.com]
 +
* Contact: Gritje Meinke [mailto:gritje.meinke@draeger.com], Stefan Schlichting [mailto:stefan.schlichting@draeger.com]
 +
* Interest: Using FHIR to publish device data, using FHIR for interfacing with hospital information systems, using FHIR to share data with 3rd party applications.
 +
 
 +
 
 +
=== Epic ===
 +
* Website: [http://www.epic.com Epic.com]
 +
* Contact: Janet Campbell [mailto:Janet@epic.com]
 +
* Interest: Developing support for SMART-on-FHIR mobile and web applications.
 +
 
 +
 
 +
===GE Healthcare===
 +
* Website: [http://www.gehealthcare.com GE Healthcare]
 +
* 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.
 +
 
 +
 
 +
===Guys’ & St Thomas’ NHS Trust UK (Kings Health Partners)===
 +
* 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]
 +
* 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: [http://www.healthcentrix.com www.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.
 +
 
 +
 
 +
===Health-Comm GmbH (Germany)===
 +
* Website: [http://www.health-comm.de]
 +
* Contact: Simone Heckmann [mailto: simone.heckmann@health-comm.de]
 +
* Interest: Developping V2 / FHIR integration based on Cloverleaf(R), contributing to the FHIR specification, participation at connectathons
 +
 
 +
 
 +
===HEALTHCONNEX (Telstra Health)===
 +
* Contact: Brian Postlethwaite [mailto:bpostlethwaite@healthconnex.com.au]
 +
* Interest: Investigating suitability of FHIR for interfacing between internal and external products.
 +
* Contributing to the development of the FHIR standard - particularly appointments and directory related resources.
 +
* (company formerly known as DCA eHealth Solutions)
 +
 
 +
 
 +
===Health Samurai===
 +
* Website: [http://health-samurai.io]
 +
* Contact: Pavel Smirnov [mailto:pavel@health-samurai.io] and Nikolay Ryzhikov [mailto:niquola@health-samurai.io ]
 +
* Interest: Develop an ecosystem of connected healthcare applications and a development platform on top of an extended FHIR server Aidbox [https://aidbox.io]
 +
 
 +
 
 +
===Helios Software===
 +
* Website: [http://heliossoftware.com Helios Software]
 +
* Contact: Steve Munini [mailto:steve@heliossoftware.com]
 +
* Interest: Interest:  Commercial-grade implementation of HL7® FHIR® that runs on Apache Cassandra™.  Also, Helios Software consultants help our clients design, build and launch new FHIR-based healthcare products.
 +
 
 +
 
 +
===HL7 Colombia===
 +
* Website: [http://www.hl7.org.co www.hl7.org.co]
 +
* 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.
 +
 
 +
 
 +
===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===
 +
* Website: [http://www.ihe.net www.ihe.net]
 +
* 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)
 +
 
 +
 
 +
===Infor===
 +
* Website: [http://www.infor.com/solutions/cloverleaf/ Infor]
 +
* Contact: Joel Rydbeck [mailto:Joel.Rydbeck@infor.com], Ron Archambault [mailto:Ronald.Archambault@infor.com]
 +
* Interest: Develop FHIR resources for server/client enablement with existing applications and technologies to advance adoption of the standard. Contribute as an active member of FHIR committee.
 +
 
 +
 
 +
===InterSystems Corporation===
 +
* Website: [http://www.intersystems.com/healthshare InterSystems Corp.]
 +
* Contact: Matthew Spielman [mailto:matthew.spielman@intersystems.com email]
 +
* Interest: Developing intra-hospital and HIE-based FHIR solutions. Providing Caché based developer tools for FHIR.
 +
 
 +
 
 +
===Kainos Evolve===
 +
* Website: [http://www.kainos.com/evolve Kainos Evolve]
 +
* Contact: Alastair Allen [mailto:a.allen@kainos.com]
 +
* Interest: FHIR Server exposing Evolve services, enabling easy mobile app development and IHE-MHD.
 +
 
 +
 
 +
===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]
 +
* 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.
 +
 
 +
 
 +
===McKesson===
 +
* Website: [http://www.mckesson.com/ McKesson Corporation]
 +
* Contact: Colin Wright [mailto:colin.wright@mckesson.com]
 +
* Interest: Enabling FHIR on new and existing HIT systems. Particularly in conjunction with other standards (e.g., XDS, CDA) and in new web-based and mobile applications.
 +
 
 +
 
 +
===Medicity===
 +
* Website: [http://www.medicity.com/ Medciity]
 +
* Contact: Brian Ahier [mailto:bahier@medicity.com]
 +
* Interest: Medicity supports the SMART on FHIR "App plugin" architecture and developing HIE extensions. Provider directory is next step..
 +
 
 +
 
 +
===Mirth Corporation===
 +
* Website: [https://www.mirth.com/Products-and-Services/Mirth-Connect Mirth Connect]
 +
* Contact: Kelly Huang [mailto:kellyh@mirthcorp.com]
 +
* Interest: Developing tools for hosting and integrating with FHIR and other healthcare standard interfaces.
 +
 
 +
 
 +
===Mohawk College===
 +
* Website: [http://www.mohawkcollege.ca/ideaworks/MEDIC.html Mohawk College ideaworks]
 +
* 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
 +
 
 +
 
 +
===National Comprehensive Cancer Network (NCCN)===
 +
* Website: [https://www.nccn.org/ https://www.nccn.org/]
 +
* Contact: Mary Visceglia [mailto:Visceglia@nccn.org], Peter Lamb [mailto:Lamb@nccn.org]
 +
* Interest: Using FHIR resources to represent oncology-related medical content, especially around chemotherapy order templates. For more information, check out our FHIR working group for an international chemotherapy order template implementation guide at [http://wiki.hl7.org/index.php?title=FHIR_Chemotherapy_IG FHIR Chemotherapy IG]!
 +
 
 +
 
 +
===NEHTA (Australia)===
 +
* Website: [http://www.nehta.gov.au National E-Health Transition Authority]
 +
* Contact: Reuben Daniels [mailto:reuben.daniels@nehta.gov.au]
 +
* Interest: Contributing to the development of the FHIR standard and its implementation at a national level.
 +
 
 +
 
 +
===NHS Digital (England)===
 +
* Website: n/a
 +
* Contact: Richard Kavanagh [mailto:richard.kavanagh@nhs.net]
 +
* Interest: Multiple national scale FHIR developments using REST, Messaging and Document based approaches.
 +
 
 +
===Nictiz Netherlands===
 +
* Website: [http://www.nictiz.nl National ICT Institute in Healthcare (Nictiz)]
 +
* Contact: Alexander Henket [mailto:info@nictiz.nl]
 +
* Interest: Profiling FHIR, Terminology, Testing FHIR - support FHIR development and publish implementation guidance at European and Dutch national level.
 +
 
 +
 
 +
===Nortal===
 +
* Website: [http://www.nortal.com/what-we-do/industries/healthcare http://www.nortal.com]
 +
* Contact: Igor Bossenko [mailto:igor.bossenko@nortal.com], Jan Jasinski [mailto:jan.jasinski@nortal.com]
 +
* Interest: Building NHR/NHS solutions using FHIR standard. Implementation consits of central system based on a FHIR server and hospital information systems acting as the clients.
  
−
==List of Organizations (Alphabetical Order)==
 
  
 
===Open Mapping Software===
 
===Open Mapping Software===
−
* Website: : [http://www.OpenMapSW.com http://www.OpenMapSW.com]
+
* Website: [http://www.OpenMapSW.com http://www.OpenMapSW.com]
 
* 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===
−
* Website: : [http://www.oridashi.com/fhir http://www.oridashi.com/fhir]
+
* Website: [http://www.oridashi.com/fhir http://www.oridashi.com/fhir]
 
* 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===
+
 
−
* Website: : [http://www.orionhealth.com http://www.orionhealth.com]
+
===Ministry of Health and Long Term Care - Ontario===
 +
* Contact: Chris Pentleton [mailto:chris.pentleton@ontario.ca]
 +
* Interest: Production rollout of a Drug Repository and Immunization Repository using FHIR DSTU 2 - 1.4, Production Implementation of Mobile IOS for Mass Immunization Clinics.
 +
 
 +
 
 +
===Orion Health===
 +
* Website: [http://www.orionhealth.com http://www.orionhealth.com]
 
* Contact: David Hay [mailto:david.hay25@gmail.com]
 
* Contact: David Hay [mailto:david.hay25@gmail.com]
−
* 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).
+
* Interest: Developed a general purpose server - 'Blaze' to support access to HIE data, as well as adding FHIR to the existing Integration Engine (Rhapsody).
 +
 
 +
 
 +
===Pansoma===
 +
* Website: [http://www.pansoma.at http://www.pansoma.at]
 +
* Contact:
 +
* Interest: FHIR in XDS environment and patient administration
 +
 
 +
 
 +
===Qvera===
 +
* Website: [https://www.qvera.com/hl7-interface-engine/ Qvera Interface Engine]
 +
* Contact: Ron Shapiro [mailto:rshapiro@qvera.com]
 +
* Interest: Comprehensive FHIR support for both FHIR client and FHIR server, with the most intuitive and award-winning interface engine; To learn more, download our [https://www.qvera.com/fhir-starter-kit/ free FHIR Starter Kit] which includes pre-built mappings for FHIR queries, FHIR server responses, HL7 to FHIR mappings, CDA to FHIR mappings etc.
 +
 
 +
===Redox===
 +
* Website: [https://www.redoxengine.com https://www.redoxengine.com/]
 +
* Contact: George McLaughlin [mailto:george@redoxengine.com]
 +
 
 +
===The Sequoia Project.===
 +
* Website: [http://www.sequoiaproject.org The Sequoia Project]
 +
* Contact: Admin [mailto:admin@sequoiaproject.org]
 +
* Interest: Contribute to the development of specific FHIR resources, and functional capabilities (provider directory, security, document exchange, consent, others).  Active member of the Argonaut project.  Participating in FHIR Connectathons and testing activities.  Deployment of a FHIR-based provider directory server.  Potential interest in more involvement depending on our Participant needs. [http://www.sequoiaproject.org Sequoia Project]
 +
 
 +
 
 +
=== Standards and Interoperability Framework ===
 +
* Website: [http://wiki.siframework.org/BlueButton+Plus+Initiative http://wiki.siframework.org/BlueButton+Plus+Initiative]
 +
* Contact: Keith Boone [mailto:keith.boone@ge.com]
 +
* Interest: Use of FHIR XDS Entry resource to support access to C-CDA and CCD documents.
 +
 
 +
 
 +
===SYSNET International, Inc.===
 +
* Website: [http://www.sysnetint.com http://www.sysnetint.com]
 +
* Contact: Odysseas Pentakalos [mailto:odysseas@sysnetint.com]
 +
* Interest: Adding FHIR support for all patient registration events to the open source EMPI [http://www.openempi.org OpenEMPI]
 +
 
 +
 
 +
===Systelab Technologies - WERFEN===
 +
* Website: [http://www.systelabsw.com http://www.systelabsw.com]
 +
* Contact: Daniel Nebot Benabarre [mailto:daniel.nebot@werfen.com]
 +
* Interest: Contributing to the design and implementation of FHIR interfaces mainly in the Diagnostic, Documents, Patient Adm and Research domains, we seek to keep developing easily interoperable products for the IVD market.
 +
 
 +
 
 +
=== Systems Made Simple, Inc. ===
 +
* Website:  [http://www.systemsmadesimple.com http://www.systemsmadesimple.com]
 +
* Contact:  Gina Gallagher  [mailto:gina.gallagher@systemsmadesimple.com]
 +
* 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 http://www.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)
 +
 
 +
 
 +
===University Health Network (Toronto Canada)===
 +
* Websites: [http://uhn.ca http://uhn.ca] [http://jamesagnew.github.io/hapi-fhir/ http://jamesagnew.github.io/hapi-fhir/]
 +
* Contact: James Agnew [mailto:jamesagnew@gmail.com]
 +
* Interest:  Using FHIR to expose clinical data from a number of backing systems as a coherent API for app developers inside and outside the organization
 +
 
  
 
===University of Western Sydney===
 
===University of Western Sydney===
−
* Website: : [http://www.uws.edu.au/scem http://www.uws.edu.au/scem School]
+
* Website: [http://www.uws.edu.au/scem http://www.uws.edu.au/scem] School of Computing, Engineering and Mathematics
−
* Contact: David Hay [mailto:david.hay25@gmail.com]
+
* Contact: Klaus Veil [mailto:K.Veil@UWS.edu.au]
−
* 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).
+
* 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===
 +
* Website: [http://demo.iehr.us/vipr/fhir/ http://demo.iehr.us/vipr/fhir/]
 +
* 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.
 +
 
 +
 
 +
=== Vitoria City Hall - Brazil ===
 +
* Website: http://www.vitoria.es.gov.br/
 +
* Contact: Paulo César [mailto:paulo.cesar@vitoria.es.gov.br]
 +
* Interest:  Using FHIR to interoperate the electronic patient record data with service providers.
 +
 
 +
 
 +
===West Health Institute===
 +
* Website: [http://www.westhealth.org http://www.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.
 +
 
 +
 
 +
===Wolters Kluwer Health===
 +
* Website: http://wolterskluwer.com/products-services/our-portfolio/health.html
 +
* Contact: Howard Strasberg [mailto:howard.strasberg@wolterskluwer.com]
 +
* Interest: Clinical decision support applications.
 +
 
 +
 
 +
=== Xerox Healthcare Solutions ===
 +
* Website: [http://services.xerox.com/healthcare-solutions/enus.html Xerox Healthcare Solutions]
 +
* Contact:
 +
* Interest: Use of FHIR server in support of HIE, FHIR resources for XDS, CCDA, CCD and FHIR for mobile applications (IHE MHD TF Supplement).
 +
 
 +
 
 +
=== Yerkes National Primate Research Center (NIH) ===
 +
* Website: http://www.yerkes.emory.edu/
 +
* Contact: Jonathan Lowe [jonathan.m.lowe@emory.edu]
 +
* Interest:  A single database for the storage and analysis of all Biomarker assays and Genomic core analyses

Latest revision as of 19:02, 6 June 2018

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.

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.

National FHIR Project can be registered here

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 Touchstone Project a Developers Integration Lab (DIL) initiative. Working on IHE, HL7, NwHIN and FHIR within the AEGIS Integrated Ecosystem a synthetic testing community of Health Care organizations.


Allscripts

  • Website: Allscripts
  • Contact: Jeffrey Danford [2]
  • Interest: Allscripts is committed to providing a FHIR API service that supports SMART on FHIR and mobile apps and Precision Medicine Initiative as part of the Allscripts Open Platform and the Allscripts Developer Program. For more information please visit http://developer.allscripts.com.


Alten Calsoft Labs

ART-DECOR

  • Website: ART-DECOR
  • Contact: Kai Heitmann [4]
  • Interest: Profiling FHIR, Terminology, Testing FHIR - support FHIR development and publish implementation guidance at every level international, national, or regional.


Black Pear Software

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

By Light Professional IT Consulting

  • Website: By Light
  • Contact John Moehrke [6]
  • Interest: Healthcare IT Consulting services. Currently sub-contractor to VHA for Interoperability, eHEX, Direct, CDA, and FHIR services.

Caristix

  • Website: Caristix
  • Contact: Jean-Luc Morin [7]
  • Interest: Developing tools to help FHIR implementation to integrate systems.


Cerner

  • Website: Cerner
  • Contact: David McCallie [8]
  • Interest: The SMART on FHIR "App plugin" architecture; HIE extensions; SOA support for back-end integration services.


Cognizant Technology Solutions

  • Website: Cognizant Technology Solutions
  • Contact: Doug DeShazo [9]
  • Interest: Use of FHIR server in support of HIE, FHIR resources for XDS, CCDA, CCD and FHIR for mobile applications (IHE MHD TF Supplement).


CommonWell Health Alliance

  • Website: CommonWell
  • Contact: Peter Bernhardt [10]
  • 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.


Corepoint Health

  • Website: Corepoint Integration Engine
  • Contact: Dave Shaver [11]
  • Interest: Supporting FHIR within comprehensive, #1-in-KLAS integration engine; support for both client and server roles, HL7 V2/CDA to FHIR mapping, and FHIR-to-FHIR mapping.


Datuit (SafeIX Application Platform)

  • Website: datuit.com
  • Contact: Gordon Raup [12]
  • 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).


Dräger

  • Website: draeger.com
  • Contact: Gritje Meinke [13], Stefan Schlichting [14]
  • Interest: Using FHIR to publish device data, using FHIR for interfacing with hospital information systems, using FHIR to share data with 3rd party applications.


Epic

  • Website: Epic.com
  • Contact: Janet Campbell [15]
  • Interest: Developing support for SMART-on-FHIR mobile and web applications.


GE Healthcare

  • Website: GE Healthcare
  • Contact: John Moehrke [16]
  • 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 [17], Gary McAllister [18]
  • 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 [19]
  • 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.


Health-Comm GmbH (Germany)

  • Website: [20]
  • Contact: Simone Heckmann [mailto: simone.heckmann@health-comm.de]
  • Interest: Developping V2 / FHIR integration based on Cloverleaf(R), contributing to the FHIR specification, participation at connectathons


HEALTHCONNEX (Telstra Health)

  • Contact: Brian Postlethwaite [21]
  • Interest: Investigating suitability of FHIR for interfacing between internal and external products.
  • Contributing to the development of the FHIR standard - particularly appointments and directory related resources.
  • (company formerly known as DCA eHealth Solutions)


Health Samurai

  • Website: [22]
  • Contact: Pavel Smirnov [23] and Nikolay Ryzhikov [24]
  • Interest: Develop an ecosystem of connected healthcare applications and a development platform on top of an extended FHIR server Aidbox [25]


Helios Software

  • Website: Helios Software
  • Contact: Steve Munini [26]
  • Interest: Interest: Commercial-grade implementation of HL7® FHIR® that runs on Apache Cassandra™. Also, Helios Software consultants help our clients design, build and launch new FHIR-based healthcare products.


HL7 Colombia

  • Website: www.hl7.org.co
  • Contact: Mario Cortés [27]
  • 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 [28]
  • Interest: Using FHIR as an example of ICT 'mainstreaming' eHealth interoperability technology.


IHE

  • Website: www.ihe.net
  • Contact: Keith Boone [29]
  • 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)


Infor

  • Website: Infor
  • Contact: Joel Rydbeck [30], Ron Archambault [31]
  • Interest: Develop FHIR resources for server/client enablement with existing applications and technologies to advance adoption of the standard. Contribute as an active member of FHIR committee.


InterSystems Corporation

  • Website: InterSystems Corp.
  • Contact: Matthew Spielman email
  • Interest: Developing intra-hospital and HIE-based FHIR solutions. Providing Caché based developer tools for FHIR.


Kainos Evolve

  • Website: Kainos Evolve
  • Contact: Alastair Allen [32]
  • Interest: FHIR Server exposing Evolve services, enabling easy mobile app development and IHE-MHD.


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 [33]
  • 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.


McKesson

  • Website: McKesson Corporation
  • Contact: Colin Wright [34]
  • Interest: Enabling FHIR on new and existing HIT systems. Particularly in conjunction with other standards (e.g., XDS, CDA) and in new web-based and mobile applications.


Medicity

  • Website: Medciity
  • Contact: Brian Ahier [35]
  • Interest: Medicity supports the SMART on FHIR "App plugin" architecture and developing HIE extensions. Provider directory is next step..


Mirth Corporation

  • Website: Mirth Connect
  • Contact: Kelly Huang [36]
  • Interest: Developing tools for hosting and integrating with FHIR and other healthcare standard interfaces.


Mohawk College

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


National Comprehensive Cancer Network (NCCN)

  • Website: https://www.nccn.org/
  • Contact: Mary Visceglia [38], Peter Lamb [39]
  • Interest: Using FHIR resources to represent oncology-related medical content, especially around chemotherapy order templates. For more information, check out our FHIR working group for an international chemotherapy order template implementation guide at FHIR Chemotherapy IG!


NEHTA (Australia)


NHS Digital (England)

  • Website: n/a
  • Contact: Richard Kavanagh [41]
  • Interest: Multiple national scale FHIR developments using REST, Messaging and Document based approaches.

Nictiz Netherlands


Nortal

  • Website: http://www.nortal.com
  • Contact: Igor Bossenko [43], Jan Jasinski [44]
  • Interest: Building NHR/NHS solutions using FHIR standard. Implementation consits of central system based on a FHIR server and hospital information systems acting as the clients.


Open Mapping Software

  • Website: http://www.OpenMapSW.com
  • Contact: Robert Worden [45]
  • 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 [46]
  • Interest: Implementing FHIR server interface for Australian primary care systems to support appropriate 3rd party clinical data access.


Ministry of Health and Long Term Care - Ontario

  • Contact: Chris Pentleton [47]
  • Interest: Production rollout of a Drug Repository and Immunization Repository using FHIR DSTU 2 - 1.4, Production Implementation of Mobile IOS for Mass Immunization Clinics.


Orion Health

  • Website: http://www.orionhealth.com
  • Contact: David Hay [48]
  • Interest: Developed a general purpose server - 'Blaze' to support access to HIE data, as well as adding FHIR to the existing Integration Engine (Rhapsody).


Pansoma


Qvera

  • Website: Qvera Interface Engine
  • Contact: Ron Shapiro [49]
  • Interest: Comprehensive FHIR support for both FHIR client and FHIR server, with the most intuitive and award-winning interface engine; To learn more, download our free FHIR Starter Kit which includes pre-built mappings for FHIR queries, FHIR server responses, HL7 to FHIR mappings, CDA to FHIR mappings etc.

Redox

The Sequoia Project.

  • Website: The Sequoia Project
  • Contact: Admin [51]
  • Interest: Contribute to the development of specific FHIR resources, and functional capabilities (provider directory, security, document exchange, consent, others). Active member of the Argonaut project. Participating in FHIR Connectathons and testing activities. Deployment of a FHIR-based provider directory server. Potential interest in more involvement depending on our Participant needs. Sequoia Project


Standards and Interoperability Framework


SYSNET International, Inc.


Systelab Technologies - WERFEN

  • Website: http://www.systelabsw.com
  • Contact: Daniel Nebot Benabarre [54]
  • Interest: Contributing to the design and implementation of FHIR interfaces mainly in the Diagnostic, Documents, Patient Adm and Research domains, we seek to keep developing easily interoperable products for the IVD market.


Systems Made Simple, Inc.

  • Website: http://www.systemsmadesimple.com
  • Contact: Gina Gallagher [55]
  • 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 [56]
  • Interest: Use of FHIR for community based healthcare process integration (e.g. scheduling, care management)


University Health Network (Toronto Canada)


University of Western Sydney

  • Website: http://www.uws.edu.au/scem School of Computing, Engineering and Mathematics
  • Contact: Klaus Veil [58]
  • 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


Vitoria City Hall - Brazil


West Health Institute

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


Wolters Kluwer Health


Xerox Healthcare Solutions

  • Website: Xerox Healthcare Solutions
  • Contact:
  • Interest: Use of FHIR server in support of HIE, FHIR resources for XDS, CCDA, CCD and FHIR for mobile applications (IHE MHD TF Supplement).


Yerkes National Primate Research Center (NIH)

  • Website: http://www.yerkes.emory.edu/
  • Contact: Jonathan Lowe [jonathan.m.lowe@emory.edu]
  • Interest: A single database for the storage and analysis of all Biomarker assays and Genomic core analyses
Retrieved from "https://wiki.hl7.org/w/index.php?title=Organizations_interested_in_FHIR&oldid=157950"