Healthcare Exchange Standards

NOVEMBER 28, 2017

I think the most useful value-add that an HIE can add is an API that is based on FHIR. This is true of an XDS based HIE, Regional Exchange (XCA), Vendor based EHR, nationwide Exchange, and Direct HISP. At an HIE level: Initially I would focus on enabling Apps to query for and read the data available in the HIE.

HIE 40

HIE FHIR EHR Interoperability 40

Healthcare Exchange Standards

MAY 2, 2024

The IHE-MHDS does not define a Document Repository Actor but does include architecture support for distributed FHIR Servers and thus the concept of a Document Repository is included in MHDS. IHE-MHDS does not define the Document Repository Actor, as the concept of a set of distributed FHIR Servers is very natural to REST architecture.

HIE 45

HIE FHIR Health Information 45

Healthcare Exchange Standards

MAY 4, 2023

The IHE IT-Infrastructure committee continues to produce new and improved specifications for HIE interoperability. It is intended to be read by HIE and Healthcare IT Executives and Architects, Standards Development Architects, and health data exchange stakeholders in academia.

FHIR 118

FHIR HIE Interoperability Health Data 118

Healthcare IT Today

MAY 23, 2023

Buckle also shares her experience at the Interop Showcase and details of the recent CommonWell FHIR Connectathon where CommonWell members leveraged FHIR to improve interoperability. FHIR, the API for automated data sharing, is mature and being adopted. This more recent standard makes trust automatable as well.

FHIR 119

FHIR HIE Interoperability Public Health 119

Healthcare Exchange Standards

NOVEMBER 22, 2019

Today on the FHIR Consent call we had a very useful discussion of how one would use FHIR Consent to do the same thing that BPPC does in XDS. Said another way, what is the degenerate form of FHIR Consent that is equal-to the functionality of BPPC, and what is the degenerate form of FHIR Consent that is compatible with BPPC.

FHIR 68

FHIR HIE 68

Healthcare Exchange Standards

NOVEMBER 21, 2017

The Wisconsin HIE (WISHIN) held a summit last week. The following diagram clearly shows Wisconsin leadership This is such an exciting perspective of what the Wisconsin HIE delivers today, and where they are targeting for future support. It seems to me that the statistics show a really strong and healthy HIE.

HIE 49

HIE FHIR Leadership 49

Healthcare Exchange Standards

APRIL 5, 2024

The International Patient Summary (IPS) content, as defined in the ISO 27269 data model specification, utilizes IHE’s document sharing infrastructure including cross-community, HIE, direct exchange models, and more. If you want a purely FHIR transport for this FHIR IPS, then look to the Mobile Health Document Sharing (MHDS) Profile

FHIR 63

FHIR HIE Mobile Health Health Information 63

Healthcare IT Today

FEBRUARY 25, 2024

A survey published in JAMIA found 73% of digital health vendors are using standards-based FHIR APIs when integrating with EHR systems. California-based HIE entity Serving Communities Health Information Organization is using NextGen Healthcare ’s Mirth interoperability solutions.

FHIR 93

FHIR Digital Health Telemedicine EHR 93

Healthcare Exchange Standards

DECEMBER 30, 2017

It happens that the framework for explaining why the future is bright for HIE comes from the Wisconsin HIE (WISHIN) fall summit. They used the following diagram to show what they viewed as the HIE future. The good news is that FHIR is a fantastic API for consuming data. Note slide decks are now available.

HIE 40

HIE FHIR Meaningful Use Leadership 40

Healthcare Exchange Standards

JANUARY 10, 2017

How does one put a FHIR Document into XDS? How does one find a FHIR Document in XDS? To learn more on Document Sharing, start here: Eating an Elephant -- How to approach IHE documentation on Health Information Exchange (HIE) So the Document Sharing family is a Content Agnostic mechanism for sharing Patient specific Documents.

FHIR 40

FHIR HIE Health Information Interoperability 40

Healthcare Exchange Standards

DECEMBER 3, 2020

This is an alternative to SMART-on-FHIR, and not intended to be conflicting. An update to the HIE-Whitepaper , bringing in the newly build FHIR based profiles. Each cover unique spaces with some overlap. Profiles like MHD, MHDS, mXDE, QEDm, PMIR, SVCM, mCSD, ATNA, and IUA. This document is available at [link].

HIE 40

HIE FHIR Health Information 40

Healthcare Exchange Standards

NOVEMBER 7, 2023

This winter quarter will be a lighter load, recognizing the holidays: Patient Scheduling, prospective look at FHIR R5/6, and evaluating impact of Gender Harmony. This specification is based on FHIR Version 4.0.1 , and references the Schedule , Slot , and Appointment resources.

FHIR 71

FHIR HIE Health Information 71

Healthcare Exchange Standards

MAY 9, 2019

This is an update of what is going on in Security and Privacy in, and around, the FHIR specification. This is an update of what is going on in Security and Privacy in, and around, the FHIR specification. GDPR driven activities: The Security WG has done an assessment of FHIR in the context of GDPR.

FHIR 40

FHIR HIE Health Information 40

Healthcare Exchange Standards

FEBRUARY 27, 2020

This profile shows how to build a Document Sharing Exchange using IHE profiled FHIR® standard, rather than the legacy IHE profiles that is dominated by XDS and HL7® v2. The HIE also contains systems, illustrated in green, that submit and consume documents. This profile will assemble profiles and define a Document Registry.

Mobile Health 105

Mobile Health HIE FHIR Health Information 105

Healthcare Exchange Standards

MARCH 3, 2021

Does that mean we don't move to nationwide http RESTful FHIR? I expect, as I have said before, that the green-fields will/should use http RESTful FHIR. My main concern is that we are trying to apply http RESTful FHIR to the hardest problem (Treatment, Payment, and Operations) when we already have a solution there.

FHIR 117

FHIR HIE 117

Healthcare Exchange Standards

NOVEMBER 25, 2017

The next item on the HIE Future is Bright list is movement from "Multiple Point-to-Point Connections" to "Single Connection to Hub". In the case of most HIE traffic today it is for the PurposeOfUse of "Treatment". Very minor mention of FHIR. This change is purely administrative, but is still significant.

HIE 40

HIE eHealth FHIR Public Health 40

Redox

NOVEMBER 21, 2023

Is this just another HIE? Of note, the XCPD, XCA, and XDR profiles do not currently support FHIR natively. A few features of the CA DxF set it apart from traditional health information exchanges (HIEs) and networks (HINs). The table below is an overview of Access-provided features and services.

HIE 59

HIE FHIR Health Information Nursing 59

Healthcare Exchange Standards

APRIL 6, 2018

I want an Access Log, that is a log of every time my data was accessed (Direct or Exchange or FHIR). There no network that I know of that provides a view of how the HIE was used to expose the Patient data. But the fact the data is NOT accessible at all is a problem How about the Patient and their Devices author directly into FHIR.

HIE 40

HIE FHIR Health Information Patient Experience 40

Healthcare Exchange Standards

FEBRUARY 25, 2016

Two independent projects this week sent to the FHIR mailing list their diagrams of how they are using FHIR as an API to classic XDS environments. The power of using FHIR as a simplifying API to classic environments. Our project will use FHIR as an abstraction layer for the application. privacy consent). Well done!

FHIR 40

FHIR HIE EHR Interoperability 40

Healthcare Exchange Standards

MARCH 7, 2023

This is a new FHIR specification that expresses what a International Patient Summary (IPS) would look like. This is a FHIR-Document, much like a CDA Document, but using FHIR fundamentals rather than the HL7 v3 model that is the basis of CDA. Note that the Document Sharing exchanges can handle very well this new FHIR-Document.

FHIR 68

FHIR HIE Health Information 68

Healthcare Exchange Standards

NOVEMBER 24, 2017

So I often get frustrated when someone says that the HIE needs to become Patient Centered. There is no other purpose of an HIE besides the Patient. There is nothing in existing HIE that is "Provider-Centered". I truly feel sorry for Providers that are going out-of-their-way to use an HIE for the benefit of their Patient.

HIE 40

HIE FHIR Health Information HIPAA 40

Redox

MARCH 7, 2024

The benefits of connecting to a QHIN via Redox A single connection for all your integration needs: Redox will connect our customers to TEFCA, while also connecting them to any other system required to power their solutions, workflows, or analytics, via a single HL7 ® Fast Interoperability Healthcare Resources (FHIR ® ) or Redox JSON-based API.

FHIR 59

FHIR Interoperability eHealth HIE 59

Healthcare Exchange Standards

DECEMBER 30, 2021

The last time I did a year-end report was at the end of 2017 - HIE Future is Bright - stepping into 2018. 1.6k) Agile improvements toward #FHIR (1.5k) Security of #FHIR implementations concerns (1k) It is good to see that the Alisa Knight cybersecurity attacks on #FHIR were not a big reason for visitors to my blog.

FHIR 75

FHIR Health Information HIE Healthcare IT 75

Healthcare Exchange Standards

FEBRUARY 19, 2024

Update HIE Whitepaper and MHDS with newest Profiles. Previously PDQm supported only the FHIR query, which does not give the server the power to utilize algorithms. Support for the normal FHIR dynamic discovery using the metadata endpoint returning a CapabilityStatement is used in operational environments to detect server support.

FHIR 63

FHIR HIE 63

Healthcare Exchange Standards

OCTOBER 24, 2022

Add an ITI-65 FHIR Documents Publish option with support in ITI-65 to include a FHIR Document Bundle as an alternative to Binary. Converted from PDF to a FHIR IG. Very focused on #FHIR, but also enabled by existing and successful XDS/XCA Health Information Exchange. Each of these new options may survive or may be removed.

FHIR 52

FHIR HIE Health Information Health Data 52

Healthcare Exchange Standards

OCTOBER 24, 2019

Most use of FHIR today is as an API to an organizations health information (EHR). However what is being asked latey is how does one scale FHIR to a nation. I have plenty of articles on how a Nationwide Health Information Exchange (HIE) could be built with the IHE XD* family of profiles.

FHIR 45

FHIR Health Information HIE EHR 45

Healthcare Exchange Standards

FEBRUARY 27, 2021

Something supported by IHE Document Sharing (XDS/XDR/XDM/XCA/MHD), something enabled and using #FHIR. Some background that is important can be found in the IHE HIE-Witepaper in the section on " Principles of IHE for Health Document Sharing ". Everything else in the Bundle is just FHIR Resources. When is a Document a Document?

FHIR 81

FHIR HIE 81

Healthcare IT Today

SEPTEMBER 30, 2023

Read more… Making Healthcare App Development and FHIR Data Access Easy. Digital health developers shouldn’t have to learn the hundreds of flavors of FHIR implementations and APIs to share data , Patrick Schiess at Darena Solutions told John. Read more… CIO Podcast : Digital Transformation.

FHIR 109

FHIR Interoperability Healthcare IT HIE 109

Healthcare Exchange Standards

MAY 13, 2016

There is renewed discussion, much like back in January, around the need to go beyond testing just the FHIR Resource 'interoperability'. This reference system needs to pick a minimum-useful set of FHIR resource centric workflows. This is more than just a selection of FHIR Resources. Each actor must do something useful.

FHIR 40

FHIR Interoperability HIE Leadership 40

Healthcare IT Today

FEBRUARY 14, 2024

healthpolicyvalentines @ONC_HealthIT — Grace Vinton (@HITeaWithGrace) February 11, 2024 Roses are red, Violets are blue, I went to the CHPL, & found a FHIR endpoint for you! Telephone lines to HIEs, to @CarequalityNet & QHINs. What does that mean for patients? Less fragmented health data.

Health Policy 80

Health Policy Meaningful Use HIE EMR 80

Healthcare IT News - Telehealth

SEPTEMBER 5, 2023

September 04, 2023 Sponsored Healthcare reforms an opportunity to boost digital maturity and benefit providers Digital reforms like SATUSEHAT in Indonesia encourage healthcare providers to adopt the FHIR.

EMR 98

EMR HIE FHIR Mental health 98

Redox

AUGUST 8, 2023

JSON, XML, pipe delimited) and is siloed within a myriad of source systems like electronic health records (EHR), medical imaging databases, claims processing systems, revenue cycle solutions, health information exchanges (HIE), and so on. Databricks supports both reading and writing of all FHIR resources in standard FHIR Bundle exchanges.

FHIR 52

FHIR Interoperability EHR HIE 52

Healthcare Exchange Standards

FEBRUARY 20, 2021

HIE-Whitepaper -- the whitepaper needed to be updated to include the FHIR based models that we have published in the MHD family. This also includes the use of QEDm and mXDE to make FHIR Resource level data available from the shared documents, making consumption more easy. FHIR does not have an explicit analog for home community.

FHIR 72

FHIR HIE 72

Healthcare Exchange Standards

FEBRUARY 5, 2021

Here is the HIE-Whitepaper Those looking to deploy a Health Information Exchange will find guidance on recognized principles and mechanisms. Where an exchange is based on legacy IHE profiles of XDS or XCA, there is guidance on how to enable a more easy on-ramp and off-ramp in the MHD profile that uses FHIR for the API.

Health Information 70

Health Information FHIR Interoperability HIE 70

Healthcare IT Today

AUGUST 27, 2022

In a nutshell, real-time updates enabled by FHIR are the future. Read more… Education and Communication Can Catalyze HIE Adoption. In another dispatch from the Civitas Networks / DirectTrust event, John learned that many HIE projects suffer from a marketing problem. Medical conversation AI vendor Abridge received $12.5

HIE 92

HIE Primary Care EHR Healthcare IT 92

Healthcare Exchange Standards

MARCH 16, 2015

This happened to be the same timeframe that Grahame was fanning the FHIR flames. So we joined forces and brought the concepts needed for XDS into FHIR®. So now, I take those FHIR based Resources and re-write the profile. This simplified API is based on the HL7 FHIR RESTful API. The basics are shown here.

FHIR 40

FHIR Mobile Health mHealth Meaningful Use 40

Healthcare IT Today

SEPTEMBER 11, 2023

But despite the availability of FHIR and of APIs from many vendors, interoperability is often described as “difficult and “not frictionless” according to Loyd Bittle, CEO and Founder at Innovar Healthcare. Patients, regulators, and payers are insisting on data exchange in health care.

Interoperability 66

Interoperability HIE EMR Health Data 66