article thumbnail

FHIR Forms: Theory and background

HAY on FHIR

In this set of posts we’re going to dig into how FHIR supports the use of forms in collecting information. . Forms are ubiquitous in healthcare (and other domains for that matter) so it makes sense that there is some specific support in FHIR for them. The Questionnaire (Q) Is the definition of a form. Simple really.

FHIR 104
article thumbnail

Accessing Lab data via FHIR – part 4

HAY on FHIR

Could be FHIR resources, but more likely a database structure specific to the needs of the lab domain. Well, the simple explanation is that it is a FHIR server (in that it exposes a FHIR interface) that specializes in terminology functionality. FHIR Operation? Above them all is a Terminology Server.

FHIR 121
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Hard #FHIR Safety Problem: Synchronization

Health Intersections

It’s a common thing for implementers to want to do with FHIR: connect to a FHIR server, and make a local copy of the information provided by the server, and then check back occasionally with the server for updates – that is, new resources, or changes to existing resources. (In “I never took X”).

FHIR 99
article thumbnail

#FHIR and the Gartner Hype Cycle

Health Intersections

On a forum for FHIR Foundation members, I raised the subject of where FHIR is on the Gartner Hype Cycle (see Gartner write up , or Wikipedia ). FHIR Foundation member Wes Rishel ( @wrishel ), who’s a FHIR user, and also was a Gartner Analyst before he retired, graciously made this contribution that I could post here.

FHIR 79
article thumbnail

Simple definition of ABAC and #FHIR

Healthcare Exchange Standards

Users are grouped into "clearances" (aka roles); this might be a FHIR PractitionerRole, CareTeam, RelatedPerson, and Group; but might be something non-FHIR (aka OAuth, LDAP, etc). The SLS must understand FHIR. Policies indicate what "clearance" (aka roles) have access to each data "classification".

FHIR 52
article thumbnail

FHIR enabling an Immunization Registry- part 3

HAY on FHIR

Looking at the proposal for the next version of FHIR (R5) it is multiple, but we can’t use that yet. The ‘plan definition’ extension specifies the url and value explicitly, while the ‘disease covered’ uses a named extension. These were: planDefinitionUrl. diseaseCovered.

FHIR 105
article thumbnail

Converting v2 to FHIR

HAY on FHIR

At the recent Working Group Meeting in Montreal, I participated in the ‘v2 to FHIR’ stream – focused on how can the HL7 community give advice to implementers about converting v2 messages into FHIR bundles. To actually process (convert to FHIR) a message, click the ‘Convert’ button to the upper right.

FHIR 69