forked from hl7-fhir/fhir-dstu1
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathsummary.html
104 lines (89 loc) · 4.26 KB
/
summary.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
<!DOCTYPE HTML>
[%settitle Summary (Glossy)%]
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
[%file newheader%]
</head>
<body>
[%file newnavbar%]
<div class="col-9">
<a name="glossy"> </a>
<h1>Introducing HL7 FHIR</h1>
<p><a href="fhir-summary.pdf">Get this as a PDF</a></p>
<p>
FHIR® – Fast Healthcare Interoperability Resources (hl7.org/fhir) – is a next generation
standards framework created by HL7. FHIR combines the best features of HL7’s
Version 2, Version 3 and CDA® product lines while leveraging the latest web standards
and applying a tight focus on implementability.
</p>
<p>
FHIR solutions are built from a set of modular components called “Resources”. These
resources can easily be assembled into working systems that solve real world clinical
and administrative problems at a fraction of the price of existing alternatives.
FHIR is suitable for use in a wide variety of contexts – mobile phone apps,
cloud communications, EHR-based data sharing, server communication
in large institutional healthcare providers, and much more.
</p>
<h2>Why FHIR is better</h2>
<p>
FHIR offers many improvements over existing standards:
</p>
<ul>
<li>A strong focus on implementation – fast and easy to implement (multiple developers
have had simple interfaces working in a single day)</li>
<li>Multiple implementation libraries, many examples available to kick-start development</li>
<li>Specification is free for use with no restrictions</li>
<li>Interoperability out-of-the-box– base resources can be used as is, but can also be
adapted for local requirements</li>
<li>Evolutionary development path from HL7 Version 2 and CDA – standards can co-exist and
leverage each other</li>
<li>Strong foundation in Web standards– XML, JSON, HTTP, Atom, OAuth, etc.</li>
<li>Support for RESTful architectures and also seamless exchange of information using
messages or documents</li>
<li>Concise and easily understood specifications</li>
<li>A Human-readable wire format for ease of use by developers</li>
<li>Solid ontology-based analysis with a rigorous formal mapping for correctness</li>
</ul>
<h2>Flexibility</h2>
<p>
A central challenge for healthcare standards is how to handle variability caused by diverse
healthcare processes. Over time, more fields and optionality are added to the specification,
gradually adding cost and complexity to the resulting implementations. The alternative is relying
on custom extensions, but these create many implementation problems too.
</p>
<p>
FHIR solves this challenge by defining a simple framework for extending and adapting the existing
resources. All systems, no matter how they are developed, can easily read these extensions and
extension definitions can be retrieved using the same framework as retrieving other resources.
</p>
<p>
In addition, each resource carries a human-readable text representation using html as a fallback
display option for clinical safety. This is particularly important for complex clinical information
where many systems take a simple textual/document based approach.
</p>
<h2>Example Resource: Patient</h2>
<p>
This simple example shows the important parts of a resource: a local extension, the human
readable HTML presentation, and the standard defined data content.
</p>
<img src="shot.png"/>
<p>
FHIR has resources for administrative concepts such as patient, provider, organization
and device as well as a wide variety of clinical concepts covering problems, medications,
diagnostics, care plans, financial concerns and more.
</p>
<h2>The FHIR development process</h2>
<p>
FHIR is published as a Draft Standard for Trial Use. During the Trial Use phase, HL7 actively monitors implementations in order to continue to improve the specification, and is able to be responsive to their needs.
Due to the many advantages FHIR offers, trial use is already beginning right now.
</p>
<p>
Following this, HL7 will develop FHIR as a full normative specification, most likely through 2015.
</p>
<p>
<a href="http://www.hl7.org/fhir">http://www.hl7.org/fhir</a>. Follow us on Twitter using <a href="https://twitter.com/search?q=%23FHIR">#FHIR</a>
</p>
</div>
[%file newfooter%]
</body>
</html>