Discover and read the best of Twitter Threads about #FHIR
Most recents (13)
My long overdue tweet-through of @ONC_HealthIT's #HTI1 rule begins.
Highlights: Certification has new requirements for decision support, patient demographics, and observation and electronic case reporting (eCR), + updates to USCDI. #HTI1
The TOC provides more highlights: 
These #AI text generation algorithms are getting scarily good at general code, blogs and poems. But does it work on something so niche as @HL7 #FHIR?
My testing below š
My testing below š
Let's start simple, please generate me a #FHIR patient resource with a name and birth date. And yes ā
it generates a flawless Patient instance with a name and birthDate value (that validates with no issues: simplifier.net/snippet/wardweā¦)
It even includes some extra explanation...
It even includes some extra explanation...
Let's make it a bit harder.
This algorithm remembers our previous conversation, so we can just continue with asking it to add an extension for capturing the patient's 'Race' value, for which the US Core IG has a common extension: hl7.org/fhir/us/core/Sā¦ š
This algorithm remembers our previous conversation, so we can just continue with asking it to add an extension for capturing the patient's 'Race' value, for which the US Core IG has a common extension: hl7.org/fhir/us/core/Sā¦ š
$Cheq #ToIP #UFWG
Interested in understanding more exactly what @trustoverip is?
It's only one google search away.
trustoverip.org/our-work/workiā¦
Interested in understanding more exactly what @trustoverip is?
It's only one google search away.
trustoverip.org/our-work/workiā¦
Or maybe you just don't understand still where #SSI and #DID's are going to be applied!
$Cheq #ToIP @trustoverip
#fhir #fhiroca #ghpc #iata #interoperability
trustoverip.org/get-involved/wā¦
$Cheq #ToIP @trustoverip
#fhir #fhiroca #ghpc #iata #interoperability
trustoverip.org/get-involved/wā¦
And if any of this is news to you, you may want to sit down to understand that #DID's, Decentralised Identifiers are the first approved and recommended Identifier since the #URL.
$Cheq #didcheq
w3.org/TR/did-core/
$Cheq #didcheq
w3.org/TR/did-core/
Everyone else is napping at this time, so Iām finally getting around to my first read through of #TheSANERRule. I havenāt quite started yet, but am hoping that what I find can make that label stick. federalregister.gov/documents/2022ā¦
federalregister.gov/d/2022-08268/pā¦ says: āwould also revise the hospital and critical access hospital (CAH) conditions of participation (CoPs) for infection prevention and control and antibiotic stewardship programsā, this is why I might call it #TheSANERRule, and where I will focus.
#TheSANERRule has 638 pages in print form govinfo.gov/content/pkg/FRā¦, and covers a number of additional topics. Iām expecting that somewhere around 200-250 pages matter to me.
1/16 So, a long weekend to reflect on @DHRewired last week. After a couple of dog-walks and marathon poo-picking sessions, plenty of time to think. I keep coming back to the #frontline #digitisation programme. I offer this constructively. If you want to discuss, contact me
2/16 The session with the biggest impact was #Tim #Ferris. He talked about his experience in Boston at Mass Gen and he stressed that once theyād put a single system in across 8 hospitals, all staff were part of one team and they were all on the same page for every patient
3/16 What greatly troubled me is that there was no acknowledgement in the world of ICS where we are driving vertical integration, we cannot be working on a single system
Read through tweet through now starting on @alissaknight's PLAYING WITH #FHIR: HACKING AND SECURING FHIR APIS report.
I'm going to read and give you my stream of consciousness as I'm reading. I'll blog about it later.
These are my notes, and the tag is #HackingFHIR
I'm going to read and give you my stream of consciousness as I'm reading. I'll blog about it later.
These are my notes, and the tag is #HackingFHIR
P1: "Alissa Knight has spent the last year focusing on hacking
Fast Healthcare Interoperability and Resources (FHIR) APIs,... #HackingFHIR
Fast Healthcare Interoperability and Resources (FHIR) APIs,... #HackingFHIR
Yup, I read her last report on a related topic, and can attest there's a big investment in time, and her credentials are solid as a white hat hacker #HackingFHIR
I have found most non-technical explanations of FHIR (š„) to be unsatisfactory. Key things to know are as followsā¦ 1/š§µ
FHIR (Fast Healthcare Interoperability Resources) defines a standard way to organize health data. By having a standard, a computer programmer can write an application (app) that requests data from a source location without having to ask anyone how the data are organized. 2/
This means that a computer application can be written once and work the same no matter which source (e.g., hospital) it requests data from. This is called interoperability. 3/
Here's a fun #NINO - the UK's National Insurance Number - [Thread] to start the weekend š
Maybe I should do an #NHSnumber one sometime? It's a fascinating story, which (ironically) starts with these...
Maybe I should do an #NHSnumber one sometime? It's a fascinating story, which (ironically) starts with these...
[With thanks to @guy_herbert, @TomSamaki, @PrivacyMatters & others for encouragement!]
Before I start a geeky 'deep dive' on the #NHSnumber, to provide some (personal/professional) context that will hopefully become apparent, I'll just drop these two images here:
Before I start a geeky 'deep dive' on the #NHSnumber, to provide some (personal/professional) context that will hopefully become apparent, I'll just drop these two images here:
So, to begin.
After the Second World War, in a time when we started to think (again) what a #civilised society would be, and when our leaders tried to agree #principles like #UDHR that might prevent the recurrence of genocide, and support #dignity and #HumanRights for all...
After the Second World War, in a time when we started to think (again) what a #civilised society would be, and when our leaders tried to agree #principles like #UDHR that might prevent the recurrence of genocide, and support #dignity and #HumanRights for all...
Hey patient activists - do you know of dangerous errors in someone's medical record, the kind that can cause harm or diagnostic errors? Want to help improve that?
Orientation for developers Thursday 1pm ET; public (YOU) is welcome. Blog post:
confluence.hl7.org/pages/viewpageā¦
/thread
Orientation for developers Thursday 1pm ET; public (YOU) is welcome. Blog post:
confluence.hl7.org/pages/viewpageā¦
/thread
The @HL7 #FHIR Patient Empowermt group has an APPROVED PROJECT to define data standards to submit correction requests through apps.
Sound like a worthy project? Our first "Connectathon" is in Jan, & Thurs 12/15 @ 1pm ET is an orientation for software devels. ALL INVITED. /2
Sound like a worthy project? Our first "Connectathon" is in Jan, & Thurs 12/15 @ 1pm ET is an orientation for software devels. ALL INVITED. /2
Patients & non-coders, all are welcome; HL7 meetings are all fully open. Beware - this is a technical meeting - but it will be great if a few dozen patient voices show up with moral support for this important project!
GoToMeeting 1pm ET Thurs: global.gotomeeting.com/join/322275573 /end
GoToMeeting 1pm ET Thurs: global.gotomeeting.com/join/322275573 /end
#NewHIPAA Proposed Privacy Rule Thread starting. These are my notes, there'll be a blog post summarizing these later. 1/??? And I'm not even going to try to count these or tag all with #NewHIPAA, I'll just keep them in this thread.
357 pages, PDF here: hhs.gov/sites/default/ā¦
357 pages, PDF here: hhs.gov/sites/default/ā¦
Basically this is needed because healthcare providers say "I can't do that b/c HIPAA, and patients say "yes you can", and lawyers say "but ...", and trees, we need to save some trees.
A lot of the input on this rule came from a request for information in 2018.
A lot of the input on this rule came from a request for information in 2018.
The big points are: Give me my damn data, and let me take notes, and do it faster, and you can get it in the form and format that you ask for, w/o having to bring umpteen forms of id, clarifying when you can be charged, changing the fee structure, making fees more transparent ...
Our release today is once again dedicated to helping healthcare professionals deal with #COVID19 - we are right behind our frontline staff across the #NHS dealing with this crisis. Read about our changes here or in the thread below:
tpp-uk.com/news/tpp-covidā¦ 1/20
tpp-uk.com/news/tpp-covidā¦ 1/20
Creating coded pathology results from pre-defined textual strings in incoming pathology messages - rollout coming in the next few days @NHSDigital
2/20
2/20
Set up 25 new #COVID19 units specifically for āhot hubsā completely free of charge @NHSEngland @NHSProviders
3/20
3/20
1/ Here is an update on the current status of #mCODE (thread format) based on the Cancer Data Summit @MITREcorp mitre.org/cancer-data-suā¦
1/
A tweetstorm that will make some people mad. I apologize in advance.
There are two perspectives on the IHE SOAP-based specifications (primarily XDS, XCA and XCPD), not mutually exclusive
A tweetstorm that will make some people mad. I apologize in advance.
There are two perspectives on the IHE SOAP-based specifications (primarily XDS, XCA and XCPD), not mutually exclusive
2)
a) They have worked in practice, so should not be ripped and replaced
b) They are legacy technology and we should work on more modern alternatives.
A 3rd perspective, enshrined in #TEFCA #QTF is:
c) We should continue to make them the core of our health infrastructure
a) They have worked in practice, so should not be ripped and replaced
b) They are legacy technology and we should work on more modern alternatives.
A 3rd perspective, enshrined in #TEFCA #QTF is:
c) We should continue to make them the core of our health infrastructure
3)
The world "legacy" makes people mad -- my perspective is that technology moves on regardless of whether we like it or not. Some standards, particularly low level networking standards, have stood the test of time, some have... not
The world "legacy" makes people mad -- my perspective is that technology moves on regardless of whether we like it or not. Some standards, particularly low level networking standards, have stood the test of time, some have... not
