This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Microsoft is previewing its new Azure IoT Connector for FHIR, an API feature that enables healthcare organizations to scale secure connectivity for an array of devices streaming protected health information. WHY IT MATTERS. "Developers have to build their own secure pipelines from scratch. THE LARGER TREND. ON THE RECORD.
It’s currently fed by HL7 version 2 messages and there’s a User Interface for authorized users, but there was always a plan to introduce a FHIR interface to some point – something that has been accelerated by the current COVID pandemic of course. So what would a FHIR API look like?
FHIR DevDays Amsterdam/Europe edition is coming up soon: November 17-20. I didn’t just write this blog post to flog the DevDays event, much as I love it. And, of course, it’s in the european timezone, though there’s also a session specially scheduled for a friendly time in Asia/Pac. LMICs discount.
News from Capitol Hill In a blog post, HHS Assistant Secretary for Technology Policy Micky Tripathi said behavior and not technology “is far and away the biggest impediment to progress” when it comes to information blocking. About 90% still use a mix of CDAs, HL7 v2 messages, and ADT transfers.
I am getting excited to give two IHE on FHIR tutorials at FHIR DevDays in Boston. The FHIR DevDays event is focused on educating IT professionals in the newest standard in healthcare, FHIR – Fast Healthcare Interoperability Resources. My blog articles on the topic of FHIR , Document Sharing , and Privacy
I have given a tutorial on FHIR Security and Privacy at a couple of HL7 events, and some HL7 distance learning. See Security Topics , Consent/Privacy , and FHIR for index to these articles. These recordings are available on the HL7 Education on Demand site. It is not clear when I will be asked to give the tutorial again.
One of the SMA objectives is to consider the Conference in advance and offer thoughts about what we’ll expect, which I did here in the HIMSS blog space. The cloud and FHIR standards are fostering a new era of interoperability in health care.
I am rather excited that I have been asked about FHIR Security Labels lately by people getting started at implementing. This is foundational to what we have put into FHIR. link] -- His blog where he discusses these topics, and will likely announce anything he does. Thus, I can't tell how widely it has been implemented.
I will be giving the FHIR Privacy and Security tutorial again at Sydney HL7 meeting on Thursday afternoon (our normal Wednesday afternoon agenda slot). See [link] As always I welcome any suggestions for improving the slides.
There’s a thread running on chat.fhir.org about the FHIR JSON format. In FHIR, the base types are called ‘primitive types’ – things such as ‘string’, ‘integer’, ‘boolean’ etc. This thread needs some background, so here goes… Background. Current JSON Form.
This year marked my inaugural voyage to HL7® FHIR® DevDays , alongside my Redox colleagues, Autumn Ike , and Mike Paetz. This blog represents our collective Top 5 takeaways from this year’s 4-day affair. This expert community built around FHIR is as collectively passionate as they are incredibly knowledgeable.
Over the next several weeks I will release a series of blogs highlighting the way Redox is helping our customers overcome these gaps to uncover the possible. Up first: Using bulk FHIR. What is bulk FHIR? That’s where bulk FHIR comes in. bulk FHIR is a significant step closer to that.
Care teams can use FHIR, IoT, EHR and other applications to make decisions around patient treatment plans, according to the company. Moore in a blog post in May about the launch. The system also incorporates the Bookings app into Microsoft Teams, which is HIPAA-compliant, to smooth the process of conducting telehealth appointments.
See Security Topics , Consent/Privacy , and FHIR for index to these articles. Notes and references that I posted after last years presentation Note this is NOT a SMART-on-FHIR tutorial - See that one on Monday Afternoon
Sorry to my audience for not getting much from my blog lately. Some blog topics: IHE (ITI and possibly others) Plans for next year. Something assertive about OAuth and FHIR I often write an article based on some random question I got via email. You can try to use my blog " Ask Me A Question " I am very sick of forms.
I blogged half as many articles as last year, and yet my readership only dropped by 16%. I wish I had more than 28 blog articles this year to give you. Falling mostly in the category of FHIR, Consent/AccessControl, or De-Identification. I am amazed at all you loyal readers. I hope that they were useful.
We spent a bit of time in the last post describing why we want to have data coded, how FHIR supports coded data – especially the external terminologies where the concepts are defined – and described some of the RESTful API calls that we could make to retrieve specific Observations and DiagnosticReports from the repository.
Many will say that http RESTful is functioning on a global basis with Google, Facebook, LinkedIn, Wiki, and Blogs. 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. This is true, but these are all monolithic servers.
Document Sharing - YouTube -- [link] Metadata handbook - [link] All the Document Sharing profiles [link] White-Paper Enabling doc sharing through IHE Profiles White-Paper XDS Affinity Domain Template White-Paper HIT Standards for HIM Practices White-Paper Access Control My Blog topic on Document Sharing Is it IHE work on FHIR?
A survey published in JAMIA found 73% of digital health vendors are using standards-based FHIR APIs when integrating with EHR systems. The news isn’t all good, as ONC noted in a blog post , as 68% of vendors are also using some form of proprietary APIs as well.
I’ve asked HL7 members to comment on the things they’re doing below (but honestly, they probably won’t have time – I’m getting this blog post out in a hurry between builds). But we’ll do the best with what we’ve got.
I have effected some changes in HL7 as well as blog articles about those capabilities that exist. These solutions are most well developed in FHIR, but are fundamental provenance, data tagging, and Consent so can work with most standardized data and datasets. AI and privacy are hot topics lately.
I am asked how someone can get engaged with developments in Privacy/Security around FHIR. I am especially encouraging to anyone that has either coding experience, or deployment experience; as I find that too many people engaged in Privacy/Security around FHIR are coming from the theoretical perspective. This includes DICOM and FHIR.
The secret of getting started is breaking your complex overwhelming tasks into small manageable tasks, and then starting on the first one." - Mark Twain Over the year, my blog saw mostly the same amount of visitors (90k), and I posted mostly the same number of articles (30). The secret of getting ahead is getting started.
My recent blog post from Wes Rishel (thanks) got Steve Posnack thinking, and he’s responded with some statistics around adoption of FHIR in USA: Heat Wave: The U.S. is Poised to Catch FHIR in 2019.
This is a cross-post from my personal blog. The organizers of the FHIR #DevDays conference next month have announced the four finalists who will come to Amsterdam to present their ideas to a panel of judges. In contrast to this, the HL7 FHIR organization said explicitly this June that #FHIR exists to serve patient needs.
Rene asked for an outline of Security topics for FHIR for an upcoming tutorial he is giving. The easy answer is go read all my blog articles under the #FHIR topic The second easy answer is to point at the FHIR security pages. There are efforts underway to create a Privacy Consent Directive modeled in FHIR.
As FHIR matures, the security topic becomes more and more important. In fact the specification they have " FHIR OAuth 2 " is not open for review, yet. It is made up of a set of strings that represent a few FHIR resources. It is not a complete list of FHIR resource types.
The FHIR standard is a data-model and interface (API) specification for access to health-care data. FHIR has a data type structure for an Identifier that is designed to hold any kind of globally unique identifier. All of these are information managed in another domain outside of FHIR. and his blog.
Bulk Data Access The addition of a Bulk Data Access in #FHIR was a hot topic at the San Diego workgroup meeting. Grahame has explained it on his blog. The only hint at what the Problem is a fragment of a sentence in the first paragraph of Grahame's blog article. ". Which is not a definition of a use-case.
In general these profiles are thinner than previous as the FHIR specification in DSTU2 is far more readable and complete. As such these IHE profiles rely more on the good readability of the FHIR specification in DSTU2. Other Blog articles on FHIR Topic John Updated at 9:37am Central time.
I have been asked quite often to explain how to secure FHIR. The basics of Security for FHIR are written up on the FHIR Specification. Don’t worry about security The first answer is the one I give to those in HL7 that are working on developing FHIR, or just getting their feet wet learning FHIR. Not too big.
The paper discusses the experience so far with applying the W3C PROV model to the HL7 FHIR model. Much of the material and inspiration came from my blog post in March on " Provenance vs Audit - its not a competition ". Search for "FHIR". I wrote a paper for W3C PROV program with Arnon and Adriane from Mitre.
Grahame got this question on FHIR Consent , and forward it to me to answer. Question: I am using the FHIR Contract resource ( [link] ) to convey the patient consent for a provider to access specific FHIR resources (Ex: Observation, MedicationOrder, DiagnosticReport…). It is the first use-case to not disclose any lab-results.
I have been working with some of the teams wanting to do something with Privacy Consent and are coming to the FHIR Connectathon in San Diego. An example of this is -- SMART-on-FHIR. There is some consent gathering application that presents these Privacy Policies to Patients, and records the Consent ceremony as a FHIR Consent resource.
There’s a lot more information on SMART – including a number of posts on this blog. In real life you’d query some store of tokens that the Authorization server has issued, check that they exist and haven’t expired, manage refresh tokens and suchlike. So that’s how we can make our app more secure.
The topic is Patient Privacy Consent; the discussion is if this should be modeled as a core FHIR Resource, or as a core FHIR Profile upon the Contract Resource. When we first started to model Privacy Consent Directive in FHIR, we had just finished (mostly finished) the CDA Privacy Consent Directive. Break away from Contract.
App Orchard, for its part, lets developers use a FHIR-based API to access an Epic development sandbox. Source : Bots in healthcare: interview with Thomas Schulz, Organiser of Botscamp [link] ) 2018 Digital Health Prediction 4 : Mobile phone manufacturers will follow Apple's lead on connecting to hospital EHRs using FHIR.
Thus lacking this permission, the FHIR Server would silently blind the user to any data that is restricted by Consent. I might blog further on these potential solutions. So in addition to the normal Role-Based-Access-Control, there would be an additional ‘permission’ that would be necessary for a user to be able to declare break-glass.
We organize all of the trending information in your field so you don't have to. Join 48,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content