!!! Overview[1]
[{$pagename}] ([FHIR]) is a next generation standards [framework] created by [HL7].


[{$pagename}] combines the best features of [HL7]'s v2 , [HL7] v3  and [Clinical Document Architecture] ([CDA]) product lines while leveraging the latest web standards and applying a tight focus on [implementability|Implementation].

[{$pagename}] solutions are built from a set of modular components called "[Resources]". These [FHIR Resource] can easily be assembled into working systems that solve real world clinical and administrative problems at a fraction of the price of existing alternatives. [{$pagename}] is suitable for use in a wide variety of [contexts] – [Mobile Apps]s, [Cloud computing] communications, [Electronic Health Record]-based data sharing, server communication in large institutional [Health Care Providers], and much more.

There are also number of [Open Source] based tools that can foster worldwide adoption of the [HL7] standards


[{$pagename}] intent would be to migrate from the current practice of exchanging complex [Clinical Document Architecture] ([CDA]) documents to [FHIR] exchange sets of simpler, more modular and interoperable [FHIR] [JSON Objects]

!! Why [{$pagename}] is better 
FHIR offers many improvements over existing standards:
* A strong focus on [implementation] – fast and easy to implement (multiple developers have had simple interfaces working in a single day)
* Multiple implementation libraries, many examples available to kick-start development
* Specification is free for use with no restrictions
* Interoperability out-of-the-box– base resources can be used as is, but can also be adapted for local requirements
* Evolutionary development path from [HL7] Version 2 and [CDA] – standards can co-exist and leverage each other
* Strong foundation in Web standards– [XML], [JSON], [HTTP], [OAuth], etc.
* Support for [REST]ful architectures, seamless exchange of information using messages or documents, and service based architectures
* Concise and easily understood [specifications]
* A human-readable serialization format for ease of use by developers
* Solid [ontology]-based analysis with a rigorous formal mapping for correctness

[{$pagename}] requires any [Protected Resource] [MUST] document which [version] of [FHIR] applies to the resources it offers.

!! [{$pagename}] and [Authentication]
[FHIR] servers should [authenticate] the clients. The server may choose to [authenticate] the client system and [trust] it, or to [authenticate] the individual user by a variety of techniques. For web-centric use, [OpenID Connect]  may be used to authenticate users and [OAuth]  may be used to [authenticate] and/or authorize the users. The [Smart-On-FHIR profile] on [OAuth] is tightly integrated with [FHIR] and is the preferred method for using [OAuth].

The [HEART Profile] is a set of [privacy] and [security] [specifications] that enable an [individual|Natural Person] to control the [authorization] of access to [REST]ful health-related data sharing [APIs], and to facilitate the development of interoperable implementations of these specifications by others.

!! [{$pagename}] [Classifications]
[{$pagename}] is a [resource] that are classified into 6 sections:
* [Clinical|Clinical Data] - The content of a [Clinical Data]
* [Identification] - Supporting [entities] involved in the care process
* [WorkFlow] - Manage the healthcare process
* [Financial] - Resources that support the billing and payment parts of FHIR
* Conformance - Resources use to manage specification, development and testing of FHIR solutions
* Infrastructure - General functionality, and resources for internal [FHIR] requirements

!! [{$pagename}] Type
We may not have all the [{$pagename}] Types but these seemed to be of the most interest.
%%zebra-table
%%sortable
%%table-filter
||[{$pagename}]||Description||Link
|[Patient]|Demographic information about the patient|[http://www.hl7.org/fhir/stu3/patient.html|http://www.hl7.org/fhir/stu3/patient.html|target='_blank']
|MedicationRequest|Information about requests for medications for patients|[http://www.hl7.org/fhir/stu3/medicationrequest.html|http://www.hl7.org/fhir/stu3/medicationrequest.html|target='_blank']
|MedicationDispense|Information about supply of medications to a patient|[http://www.hl7.org/fhir/stu3/medicationdispense.html|http://www.hl7.org/fhir/stu3/medicationdispense.html|target='_blank']
|MedicationAdministration|Information about medications consumption or other administration|[http://www.hl7.org/fhir/stu3/medicationadministration.html|http://www.hl7.org/fhir/stu3/medicationadministration.html|target='_blank']
|MedicationStatement|Information about the believed state of a medication|[http://www.hl7.org/fhir/stu3/medicationstatement.html|http://www.hl7.org/fhir/stu3/medicationstatement.html|target='_blank']
|Observation|Information about observations performed by a healthcare provider|[http://www.hl7.org/fhir/stu3/observation.html|http://www.hl7.org/fhir/stu3/observation.html|target='_blank']
|Appointment|Information about scheduled appointments|[http://www.hl7.org/fhir/stu3/appointment.html|http://www.hl7.org/fhir/stu3/appointment.html|target='_blank']
|AllergyIntolerance|Information about allergies and drug intolerance|[http://www.hl7.org/fhir/stu3/allergyintolerance.html|http://www.hl7.org/fhir/stu3/allergyintolerance.html|target='_blank']
|Condition|Information about a patient's condition| [http://www.hl7.org/fhir/stu3/condition.html|http://www.hl7.org/fhir/stu3/condition.html|target='_blank']
|Immunization|Information about a patient's immunizations|[http://www.hl7.org/fhir/stu3/immunization.html|http://www.hl7.org/fhir/stu3/immunization.html|target='_blank']
|CarePlan|Information about a patient's care plan|[http://www.hl7.org/fhir/stu3/careplan.html|http://www.hl7.org/fhir/stu3/careplan.html|target='_blank']
|*|Wildcard representing all available resources under the given context.| 
/%
/%
/%


!! [{$pagename}] Tense
One of the most fundamental aspects of a [{$pagename}] is tense - where it fits into the timeline. Some [{$pagename}] are records of past events, some are plans for the future, etc. This table summarizes the categories:
%%zebra-table
%%sortable
%%table-filter
||Type||Description
|Past|A record of an event that has happened
|Present|A record that serves an exchange in real time
|Future|A record that describes a future intent
|Ongoing|A record that is maintained over time that tracks the state of a patient
|Unrelated|A record that doesn't relate to time (e.g. a fixed entity)
/%
/%
/%
Note that even future records end up in the past after the event they are concerned with passes.


!! [{$pagename}] [Security Considerations][3]
[{$pagename}] is not a security [protocol], nor does it define any security related functionality. However, [FHIR] does define exchange [protocols] and content models that need to be used with various security [protocols] defined elsewhere.

!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
----
* [#1] - [Guide to Resources|https://www.hl7.org/fhir/resourceguide.html|target='_blank'] - based on information obtained 2017-07-25- 
* [#2] - [Fast_Healthcare_Interoperability_Resources|Wikipedia:Fast_Healthcare_Interoperability_Resources|target='_blank'] - based on information obtained 2018-09-17- 
* [#3] - [6.1.0 FHIR Security|https://www.hl7.org/fhir/security.html|target='_blank'] - based on information obtained 2018-10-26- 
* [#4] - [IHE / HL7 / FHIR Summary|https://www.e-health-suisse.ch/fileadmin/user_upload/Dokumente/E/overview-ihe-hl7-fhir.pdf|target='_blank'] - based on information obtained 2020-01-01