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. The Non-Patient File Sharing (NPFS) Profile defines how to share non-patient files such as clinical workflow definitions, domain policies, and stylesheets.

FHIR 70

FHIR HIE Health Information 70

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 MHDS Profile specifies how a collection of IHE profiles can be used by communities for exchanging health information. 3 - Section 4.0

Mobile Health 105

Mobile Health HIE FHIR Health Information 105

Healthcare IT Today

SEPTEMBER 30, 2023

Healthcare IT Today received a demo from Rajat Mukherji at Spectrum Enterprise on how to monitor network traffic in the hospital and at home – including temperature and humidity sensors in key locations. Read more… Making Healthcare App Development and FHIR Data Access Easy.

FHIR 104

FHIR Interoperability Healthcare IT HIE 104

Healthcare Exchange Standards

FEBRUARY 20, 2019

I have covered the vision of Data Segmentation for Privacy (DS4P) concept, and outline how a Security Labeling Service (SLS) would enable this grandiose vision of DS4P. However, there are stepping stones: The following is a slightly update on an article I wrote in July 2015 on how to set the confidentialityCode. for "_confidentiality".

FHIR 65

FHIR HIE Health Information Health Data 65

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 5, 2021

This white paper will show how various profiles work together to provide a standards based, interoperable approach to community and cross-community health information sharing. Here is the HIE-Whitepaper Those looking to deploy a Health Information Exchange will find guidance on recognized principles and mechanisms.

Health Information 69

Health Information FHIR Interoperability HIE 69

Healthcare IT Today

JUNE 17, 2023

In a panel discussion, experts from KeyCare, NTT, Rackspace, and Dell covered what hospitals need to do to protect data and clinical systems safe from cyberattacks no matter where they’re hosted , along with how to recover to minimize downtime and staff disruption. Read more… How to Make Healthcare Kiosks More Accessible for All.

Interoperability 88

Interoperability FHIR Healthcare IT eHealth 88

Healthcare Exchange Standards

AUGUST 21, 2018

This is described in the Enabling Document Sharing through IHE Profiles white paper (HIE using IHE). A Community deploying an HIE this way needs to define some metadata constraints and practices, so that the documents are found when they are needed. Each document shared is described by metadata.

HIE 40

HIE FHIR 40

Healthcare Exchange Standards

OCTOBER 10, 2017

Where the combined list is available in FHIR as a ValueSet of FormatCodes (updated in current build ) Important background :: Eating an Elephant -- How to approach IHE documentation on Health Information Exchange (HIE) and Healthcare Metadata The FormatCode is there to differentiate 'technical format'. is one FormatCode.

HIE 44

HIE FHIR Health Information 44

Healthcare Exchange Standards

AUGUST 3, 2016

Some examples where BPPC are used: Connecticut HIE: For release of Privileged Care information, a consent document SHALL be registered with HITE-CT in the form of a BPPC conformant document using the Opt-in for Legally Protected Data (ALL) policy. This article is all about IHE Document Sharing, and not about FHIR. Table 10.2.3-1

HIE 49

HIE FHIR Health Information Primary Care 49

Healthcare Exchange Standards

MAY 21, 2016

Some of my Privacy blog articles Healthcare Blockchain - Big-Data Pseudonyms on FHIR Start at Consent as a FHIR Resource FHIR Consent as a Resource or Profile Consent given to authorized representative Patient ID is critical to Enabling Privacy Consent to grant read access to a specific types of FHIR Resource electronic Privacy Consent -- Patient choice (..)

FHIR 40

FHIR HIE 40

Healthcare Exchange Standards

JULY 15, 2015

Available from the FHIR specification for easy reading. link] How to determine what the value should be? See FHIR Demonstration of DS4P. "M", because the content is less sensitive than normal, but still medical. for "_confidentiality". I don't disagree that this is a hard thing to determine.

FHIR 40

FHIR HIE Health Information 40

Healthcare Exchange Standards

JANUARY 11, 2022

Mobile Health Document Sharing The Mobile Health Document Sharing (MHDS) shows how to build a Document Sharing Exchange using IHE-profiled FHIR® standard, rather than the legacy IHE profiles that are dominated by XDS and HL7® v2. as the current HIE-Whitepaper contains MHD and MHDS now. Removed section 50.7

eHealth 97

eHealth Mobile Health HIE FHIR 97

Healthcare Exchange Standards

JANUARY 25, 2017

Given XDS and XCA interactions that are often used in an Health Information Exchange (HIE), or a National Health Information Exchange (NHIE); there is no standards/profiled way to enable a point-of-care consent gathering workflow. So today, if Consent is not already captured, and needed, then data access is blocked.

HIE 44

HIE FHIR Health Information 44

Healthcare Exchange Standards

SEPTEMBER 23, 2016

There is some strong discussion going on at HL7 around privacy concerns, especially now that HL7 FHIR has enabled easy application writing. There is concern that applications are being written by people that might not be as mature in the knowledge of how important Privacy is in healthcare.

Mobile Health 40

Mobile Health FHIR HIE mHealth 40

Healthcare Exchange Standards

FEBRUARY 20, 2019

See my other articles on Privacy Modes of patient centric communication Basics of Healthcare Data access rights in USA Privacy and Security Considerations for the use of Open APIs for Patient Directed Exchange GDPR on FHIR IHE Perspective on EU GDPR Privacy is not dead, but does need reinforcement Patient Centered HIE Apple should have a HEART HIE (..)

FHIR 51

FHIR HIE Health Data 51

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

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 Exchange Standards

APRIL 4, 2018

IHE is currently working on a "Handbook" intended to instruct an XDS Affinity Domain, or Community (XCA), or MHD community on how to structure their requirements on metadata. Later I explain how to deal with this fragility. IHE FormatCodes are mandatory In Wisconsin we have Interoperability What is MHD beyond XDS-on-FHIR?

HIE 45

HIE FHIR Health Information Interoperability 45

Healthcare Exchange Standards

OCTOBER 5, 2023

link] I'm trying to think through how to go about it and it seems challenging. But, what if a fhir-based app they use has server/architecture outside of ca? Very likely that this bill could be used to get a bunch of people together to define policy and profile how to make it work. Which ones? and I am on that project.

HIE 48

HIE FHIR 48