Implementation Guide

$10 / year

An implementation guide (IG) is a set of rules about how Fast Healthcare Interoperability Resources (FHIR) resources are used (or should be used) to solve a particular problem, with associated documentation to support and clarify the usage. The Implementation Guide resource is a single resource that defines the logical content of the IG, along with the important entry pages into the publication, so that the logical package that the IG represents, so that the contents are computable.

Complexity

In particular, validators are able to use the Implementation Guide resource to validate content against the implementation guide as a whole. The significant conformance expectation introduced by the Implementation Guide resource is the idea of Default Profiles. Implementations may conform to multiple implementation guides at once, but this requires that the implementation guides are compatible.

Implementation Guides contain two different types of resource references:
– Contents: A set of logical statements which implementations must conform to. These are almost always conformance resources
– Examples: Examples that illustrate the intent of the profiles defined in the implementation guide. These can be any kind of resource

An application’s Capability Statement may identify one or more implementation guides that an application conforms to.

Date Created

2018-09-20

Last Modified

2018-12-27

Version

4.0.0

Update Frequency

Annual

Temporal Coverage

N/A

Spatial Coverage

United States

Source

John Snow Labs; Health Level Seven International;

Source License URL

Source License Requirements

N/A

Source Citation

N/A

Keywords

FHIR, HL7, Medical Terminology, Processes Data, Processes Information, Processes Documentation, Health Information Exchange, Electronic Health Records, FHIR Smart, Smart on FHIR

Other Titles

FHIR Implementation Guide Resource, Electronic Health Records Exchange Through FHIR

NameDescriptionTypeConstraints
Concept_NameName of the concept in the FHIR structure.stringrequired : 1
Computer_Ready_NameA Computer-ready name (e.g. a token) that identifies the structure - suitable for code generation. Note that this name (and other names relevant for code generation, including element & slice names, codes etc) may collide with reserved words in the relevant target language, and code generators will need to handle this.string-
TypeThe type the structure describes.string-
Dollar_RefThe "$ref" string value contains a Uniform Resource Identifier (URI) which identifies the location of the JSON value being referenced.string-
DescriptionA free text natural language description of the structure and its use.string-
ItemsThe value of the keyword should be an object or an array of objects. If the keyword value is an object, then for the data array to be valid each item of the array should be valid according to the schema in this value.string-
EnumThe enum is used to restrict a value to a fixed set of values. It must be an array with at least one element, where each element is unique.string-
RequiredThe value of the keyword should be an array of unique strings. The data object to be valid should contain all properties with names equal to the elements in the keyword value.string-
ConstThe value of this keyword can be anything. The data is valid if it is deeply equal to the value of the keyword.string-
Concept_NameComputer_Ready_NameTypeDollar_RefDescriptionItemsEnumRequiredConst
ImplementationGuide['resourceType']
ImplementationGuide_DependsOn['uri']
ImplementationGuide_Global['profile']
ImplementationGuide_Manifest['resource']
ImplementationGuide_Resource['reference']
ImplementationGuide_Definition['resource']
ImplementationGuide_Resource1['reference']
ImplementationGuide_url#/definitions/ElementExtensions for url
ImplementationGuide_name#/definitions/ElementExtensions for name
ImplementationGuide_date#/definitions/ElementExtensions for date
Related Data Packages