Contenu connexe Similaire à Vitalis 2016 FHIR Introduction (12) Vitalis 2016 FHIR Introduction1. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Introduction to
HL7® FHIR®
Ewout Kramer
FHIR Core team (and software developer)
Furore (Amsterdam, NL)
email: e.kramer@furore.com
web: http://thefhirplace.com
http://fhir.furore.com
skype: ewoutkramer
2. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
3. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
4. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Relative – No technology can make integration as fast as we’d like
That’s why we’re here
Building blocks – more on these to follow
The Acronym
5. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
6. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
HL7 v2.0
7. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
?
HL7 v3
8. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Focus on implementers
Keep common scenarios simple
Leverage existing technologies
Make content freely available
Invoke the community
9. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
If your neighbour 's son can’t
hack an app with
<your technology X>
in a weekend…..
you won’t get adopted
Focus on implementers..
10. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
THE RISE OF THE API
Background
10
11. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Your “Mobile” device becomes the Big Aggregator and Coordinator of data and functionality
What I want from my
healthcare app
12. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
The API economy
12
Where companies expose their (internal) digital business assets or services in
the form of (web) APIs to third parties with the goal of unlocking additional
business value through the creation of new assets
13. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
3rd-party becomes the
norm
13
14. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
2012
The Rise of the API
2016
15. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
So what about HL7 &
FHIR?
With FHIR, HL7 joins the ranks of the API troopers.
But other than Twitter, Facebook etc. HL7 has no “services” or
“functionality” to offer
FHIR is just a set of flexible standardized models and best-
practices that others can use to create healthcare API’s
3rd-party (app/software) developers can then seamlessly connect
to your FHIR API.
16. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
App marketplace…
17. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
NO: Region Helse-Vest
18. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
EHR Vendors…
19. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
COMPONENTS OF FHIR
In-Depth
20. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Divide health care data in discrete “building blocks”
MedicationPrescription Problem
A FHIR ‘Resource’
• Cover “the 80%”
• Unit of exchange
• Maintained & documented independently
• Have a textual description
21. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Resources - example
22. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Example – Patient
Resource
References
to other
Resources
23. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
References between
resources
A web of resources that can tell any story
24. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Clinical Scenario
First consultation
Complaining of pain in the r) ear for 3 days
with an elevated temperature. On
examination, temperature 38.5 degrees and
an inflamed r) ear drum with no perforation.
Diagnosis Otitis Media, and prescribed
Amoxil 250mg TDS for 5 days
Follow up consultation
5 days later returned with an itchy skin rash.
No breathing difficulties. On examination,
urticarial rash on both arms. No evidence
meningitis. Diagnosis of penicillin allergy.
Antibiotics changed to erythromycin and
advised not to take penicillin in the future.
Condition
Observation
Med
Allergy
Encounter
5 year old boy
Patient
25. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Resource view
26. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Extending Patient
References
to other
Resources
Yes, but where are:
• citizenship
• mothersmaidenname,
• us-core-race
Don’t worry, you can add extensions: your own elements –
FHIR even defines a few favorite ones!
27. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
+ =
Cover the 80% out of the box…
Everyone needs
extensions…
Simple choice – design for absolutely
everything or allow extensions
Everyone needs extensions, everyone
hates them!
28. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Resource Anatomy
28
29. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Resource Anatomy
29
30. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Exchange Patterns
30
REST
Documents Messages
Services
(API)
31. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
REST:“Repository”
model of healthcare
Hospital System
Create
Record
Create
Encounter
FHIR server
Patient Observation
Patient Patient
Order Observation
Observation
Diagnostic
Report
Notify new
Lab results
Update
Patient
data
Lab System
Post
Lab resultQuery
Lab orders
32. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR Messages
32
Used to inform or
instruct
Patient Admitted
Lab result
available
Similar to v2
messaging
33. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR Documents
33
Use for ‘point in time’
record
Discharge Summary
Referral
Similar to CDA
34. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR
Repository
Regardless of paradigm, the content is
the same
Lab System
FHIR
Message FHIR Document
National
Exchange
35. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
35
Questions?
(and then small break!)
36. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
WHY (UNIVERSAL)
STANDARDIZATION IS
HARD
36
37. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
1st: Ego’s
38. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
2nd: Cost
“Communicate first, standardize later”
“I need to be ready next month”
“Standardize first, communicate later”
“This needs to be done right, takes time”
CHAOS?
“He who ships code, wins”
39. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Interoperability
Interoperability: A model is agreed to that
allows all systems to exchange what needs to
be exchanged, without requiring any
design changes to the way their systems
works.
Well known deficiencies of this: semantic
scalability, fragmentation etc.
39
40. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Intraoperability
Rework the core structures of the systems
to function in an agreed way. Because all
the systems work the same way, then
exchange between the systems is easy
and straight forward.
Intraoperability has fewer deficiencies, but
they are much bigger: it’s much harder to
get agreement…
40
41. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
3rd: Different communities
and timelines
GP System –
Uses Prescriptions
Cancer Center –
Uses Prescriptions
Regional collaborations
– share prescriptions
Other regions – trying
the same thing
42. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
What can we do
promote interoperability
Produce basic building blocks everyone needs. Quickly!
Cooperate with your region/countries biggest players to
get them adopted
Open up a (FHIR, openEHR) registry to promote reusable
profiles, patterns & practices.
Let everyone publish their specialized “dialect” of FHIR
Re-integrate when need arises (= there’s interest and
money)
Promote, facilitate. Much more successful than
enforcement and subsidized projects.
43. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
“… the mad dreamers who tried to build a perfect
language” (terminology, information model)
A history lesson…
44. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR PROFILING
Adapting FHIR
45. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
The need for profiling
Need to be able to describe adaptations based
on use and context
Which resources and elements are used?
Which API features are used?
Which terminologies are used?
How to map these to local
requirements/implementations?
46. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Layered profiles
Country adapts a national profile
Regions or specialties may develop
specialized versions of national profile
Profile with use-case specific constraints
48
47. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Constraining a resource
Demand that the identifier uses your
national patient identifier
Limit names to just 1 (instead of 0..*)
Limit maritalStatus to another set of
codes that extends the one from
HL7 international
Add an extension to support
“RaceCode”
Note: hardly any
mandatory elements in
the core spec!
48. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Extensions
50 Note: could be JSON as well
Key = location of formal definition
Value = value according to definition
49. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
In v3 CDA…”text-based”
50. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
openEHR ADL
…computable!
51. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR:
StructureDefinition
53
Computable expression: as a Resource, just like Patient!
52. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Adapting the API
54
FHIR ServerFHIR REST
Complex
Operations
Read
Update Search
Check Drug
Interaction
Merge
Patient
Expand
ValueSet
Validate
53. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Conformance
Conformance Resources
55 55
“Implementation Guide”
Structure
Definition
SearchParam
Definition
ValueSet
Concept
Map
NamingSystem Operation
Definition
Forge
Excel
Implementation
Guide
TestScript
54. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Implementation Guide
Pour in your Conformance resources and add human
narrative:
Functional Requirement and Use case(s)
Data definitions
Actors and Interactions
Examples
Technical Implementation Guidance
Security
Help
Contact Information
56
55. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
56. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Publish!
58
Author & Store
Guide
Implementhttp://simplifier.net
http://registry.fhir.org
57. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR Registry
59
58. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FUTURE PLANS
60
59. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR Timeline
2012 20162014 2018 2020
First
Draft
2011 20152013 2017 2019
1st
DSTU
2nd
DSTU
3rd
STU Normative
First
Connectathon!
Update 1
Updates every
18-24 months
60. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
October 2015 – DSTU2
Conformance
ValueSet, Conformance,
StructureDefinition,
OperationDefinition
Scheduling
Appointment, Schedule, Slot
Workflow / PC
CarePlan, Goal, Episode, Alert,
Communication, ReferralRequest,
DiagnosticOrder
IHE XDS (MHD)
DocumentReference
DocumentManifest
IHE PCD
DeviceComponent
DeviceMetric
DICOM
ImagingStudy, ImagingObjectSelection
AuditEvent (ATNA)
W3C
Provenance
> 1.000 requests for changes processed
number of resources more or less doubled to just over 100
61. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
During the year…
63
20172016
DSTU 2 STU 3
OctMayJan
Workgroup
Meeting
Workgroup
Meeting
Workgroup
Meeting
62. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
October 2016 – STU3
New resources & support around:
Clinical Decision Support
Care coordination
Workflow management
Genomic data
eClaims
Provider directories
CCDA profiles
Consent management
250 requests for changes processed (so far)
64
63. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
STU?
Standard for TRIAL Use
“Regardless of the degree of prior
implementation, all aspects of the FHIR
specification are potentially subject to
change.”
64. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR Maturity Model
66
Level 0: “Draft”, Just added to the spec for first review
Level 1: Ready for test implementation by pilots
Level 2: Pilots exist and have interoperated with in realistic scenarios
Level 3: Meets quality guidelines, formal ballot resulting in changes
Level 4: Tested, verified and stable. Backw. compatibility becomes a prio.
Level 5: Widely implemented across scope and jurisdictions. Frozen.
65. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Going normative
Iterative process
First FMM level 4/5 in 2018
From 2018 updates every 18-24 months
More and more parts become level 4/5
67
66. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
THE FHIR COMMUNITY
Background
68
67. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
We exist now!
69
68. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Where in the world?
70
2015 HAPI FHIR Test Server statistics
69. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
New products every day
71
70. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
HSPC
Argonaut
SMART
(on FHIR)
US Co-operations
72
FHIR
C-CDA 1.1
FHIR Profiles
(MU3)
Profiles,
OIDC/OAuth
Services
Intermountain Healthcare, Veterans Affiars, IBM, Epic, Cerner, Mayo, Kaiser, …
71. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Gartner hype cycle
72. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
At your service
74
73. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Connectathons
75
74. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR foundation
Home of the community (not the SDO):
Implementers chats
Calender of events, webcasts
Repository of Extensions and profiles
Showcases, repo of FHIR projects
Best-practices & patterns
Open-source initiatives
Located at http://fhir.org76
75. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FINALLY…
77
76. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Life on the FHIR core
team
77. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Goal achieved?
It is fast to learn, implement and troubleshoot
It has a vibrant and open source community and
has frequently held hackathons.
Matures because we get LOADS of feedback
Spontaneous adoption (of a standard!)
79
78. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
But…
We can only make the technology bit easier
Interoperability is hard, and is a human
problem of common process and
understanding
FHIR cannot fix this. And it is no silver bullet.
80
79. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
81
Questions?
(and then lunch!)
80. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
82
Tutorials
All the latest information on FHIR
Connectathon
Meet fellow developers
Put FHIR to the test
Networking
FHIR experts and
authors on hand
http://fhir.furore.com/devdays
Notes de l'éditeur 0:10 The big aggregator – the extreme case is Apple HealthKit Dit wordt mogelijk gemaakt doordat systemen hun interne data en business processen aanbieden voor externe ontwikkelaars
Op een gecontroleerde wijze – via een goed ontworpen “API”
Dat was vroeger een term voor nerds, nu mag het in de board room: het is een manier van zakendoen
Niet langer lijm je mensen door ze naar je website te halen, en daar diensten aan te bieden
Maar steeds meer zorg je ervoor dat anderen apps kunnen bouwen waarmee zij jouw dienstenpakket versterken en aanvullen
Salesforce.com generates more than half of its $2.3 billion in revenue through its APIs, not its user interfaces. Twitter is said to process 13 billion transactions a day through its APIs. Google is around 5 billion transactions a day. For it’s part, Amazon is rapidly closing in on a trillion transactions. Not bad for an online bookseller.
Your portal becomes a small part of the total traffic to your sites “API” was a low-level term, but now it is about how a larger part of patient/client facing software is depending on how business start to expose their data and processes to client-facing software so it can be integrated in a larger whole. Again: Don’t expect you or your portal to be the center of the world, be humble
Now I hear you say: well this is all about today newest and hottest, mobile. But we need to realize that although the conventional markets stay, a larger and larger part will be about these consumer facing devices and software, the rest just operates in the background. And HL7 really needed to get back into that part of the market.
We need these others to make FHIR popular. App developers will communicate with innovative health solution providers and the big EHR vendors and only then realize that they are using a standardized API called FHIR. 0:20 Readily useable, contain “the 80%” (What’s the 80%...what’s maximum reuse? That’s HL7’s core business!)
Independent of context, fixed defined behaviour and meaning
Can reference each other
Units of exchange – suggests units of storage for implementers
Addressed through HTTP or other methods This is a critical concept in FHIR – the ability to reference between resources in a ‘web’ of relationships.
Also n Save resources to EHR using REST (+/- transaction), package as a document for the You can constrain away stuff you don’t need
You can add stuff to the basic models for your usecase
“Remove and add bricks as necessary” Build a resource in clinFHIR Build a resource in clinFHIR For each one – when to use “Standardize” medical data like “Patient”, “Order”, etc. These are resources
“Standardize” how to create/query/do notifications of this data 0:45 Though micro USB might be the exception ;-)
Why isn’t there a world standard for A/C plugs? They sprung up in different locations, the cost of using an adapter is small (220/110?). These vendors (and the hipster connecting to them) have only one need: communication. We have to enable them to produce software that enables better healthcare. We just should not be in the way. We may have focused on the inherent value of standardization and universal semantic operability.
When the “standardizers” realize not many comply to the standards, a normal reaction is to ask an authority or government to force vendors to comply.
This works only incidentally, and is often costly. It would be better if the vendors have motives to comply, rather than a financial impetus.
True for whole countries too (“yeah, country X started with a pilot and then they produced their local dialect ”)
“Drive-by” or “bottom-up” operability: “Communicate first, standardize later”
First, business partners. Then, collaborations, communities. Maybe, finally, nation-wide
It’s a natural process that people will want to make it work first, then only coordinate what they really need to, and then realize they can broaden their approach to a community.
“Support”, of course top-down should still be possible! Maybe even a combi in the long-term
You don’t need a central authority to model your data, before you can start. “Then again, we’re not Facebook or Twitter…..we do not write an API just for our own needs….we need to be everything to everyone…..now, how can we do that?” FHIR standardizes “the 80%”, but embraces adaption so there’s 20% that can be used to invent your own models and functionality
Premise seems to be that all communication needs to be standardized or put into a framework before communication can be successful. I think that we just have to focus on enabling the software vendors to search each group. Even if that means they’ll all be talking dialects
What language need to be standardized, depends on the context of communication. Within colleagues (in outside the same hospital), with other specialties, with the patient. Each has a bit of shared language, and “specialized” terms – we call it “jargon”.
Wie nog verder geïnspireerd wil raken:
Een boek over eeuwenlang falen om talen te standaardiseren en minder dubbelzinnig te maken.
Verplicht leesvoer voor terminologen en kennisredeneerders.
John Wilkins 1686 (en de Grieken)
James Cooke Brown (1988)
0:10 Also: TestScript resource Authoring workflow Publishing workflow Demo! 0:25 Note that dates are subject to change based on resources and the standards process 0:35 0:45 0:50