FHIR

Question 1

EHR

Answer 1

electronic health record - contains patient’s data digitized

Question 2

HL7

Answer 2

small standards development organization (their community members made FHIR)

Question 3

FHIR

Answer 3

Open-source EHR standard data model and RESTful API made for techies, not medical experts.

Only contains what’s needed for 80% of systems, nothing more to prevent bloat, remaining 20% of use cases can be developed by the individual. Almost nothing is mandatory, which makes it less interoperable.

Question 4

FHIR stands for

Answer 4

Fast (to adopt without medical knowledge)
Healthcare
Interoperability
Resources (HTTP ones)

Question 5

smile CDR

Answer 5

open source library for implementing FHIR in Java

Question 6

kafka

Answer 6

open-source distributed event store and stream-processing platform

Question 7

connectathon

Answer 7

type of event where health tech industry leaders gather to test standards as part of its development process

Question 8

encounter

Answer 8

a doctor’s appointment or hospital stay

Question 9

observation

Answer 9

a measurement on the patient (e.g. lab value)

Question 10

DiagnosticReport

Answer 10

an entire health report (e.g. lab report, xray report)

Question 11

MedicationPrescription

Answer 11

Rx for meds

Question 12

Resource attributes

Answer 12

Metadata (ID, version, tag, profiles, etc)
Extensions (info that didn’t fit in the 80% of use cases)
Narrative (HTML presentation of resource, optional but good for interoperability)
Body (resource data)

Question 13

FHIR encodings

Answer 13

JSON almost all the time
XML sometimes
researchers like RDF/Turtle

Question 14

Identifier

Answer 14

datatype representing the identifier for anything, consisting of:
system (URI indicating type of identifier)
value (actual identifier)

Question 15

FHIR IG

Answer 15

implementation guide - informal modification of FHIR spec for a specific use case

Question 16

Code

Answer 16

Something machine-readable often used in health Consists of:

system: URI indicating the standard for this code
code: The actual code
display: Human readable display name of the code

Question 17

EMR

Answer 17

electronic medical record

Question 18

Extension

Answer 18

key-value pair of a URL to either a FHIR datatype or nested extension

Question 19

parts of a FHIR resource URL

Answer 19

Base URL (server location)
Type (of resource)
PKID

Question 20

relative vs absolute link

Answer 20

relative URL assumes the same base URL as the current resource, absolute link specifies a constant base URL regardless of where it is hosted

Question 21

expression

Answer 21

determines what attribute a search parameter references (e.g. Patient.address.state)

Question 22

string search

Answer 22

case-insensitive search, but can be an exact match (by adding “:exact” to to the query param)

Question 23

token as a query param

Answer 23

For identifiers and codes, query specifies the URI as a query param then the ID directly after it separated by a pipe (e.g. “identifier=http://foo|123”)

Question 24

reference chaining

Answer 24

using expressions as a query param

(e.g. “[resource]?patient.name=Smith”

Question 25

EMR

Answer 25

electronic medical record - similar to EHR but contains only the information that would be found on a paper chart and are not as interoperable (may need to be faxed)

Question 26

US Core Implementation Guide

Answer 26

IG made to allow phone apps to connect to EMRs/EHRs that has all basic resources for interoperability in the US

Question 27

Argonaut Project

Answer 27

FHIR’s project to solidify the US Core IG

Question 28

Carin IG

Answer 28

IG by carin (organization that lets consumers access health data) for consumer directed exchange of data

Question 29

Gravity Project

Answer 29

IG project to incorporate social determinants of health into EHRs

Question 30

IPS

Answer 30

International Patient Summary project to meaningfully summarize health data for global use, mostly for Europe across borders