This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon CodeSystem http://hl7.org/fhir/safety-entries

FHIR Infrastructure icon Work Group Maturity Level: 0Informative Use Context: Country: World
Official URL: http://hl7.org/fhir/safety-entries Version: 6.0.0-cibuild
draft as of 2024-02-27 Computable Name: FHIRSafetyCheckListEntries
Flags: CaseSensitive, Complete. All codes ValueSet: http://hl7.org/fhir/ValueSet/safety-entries OID: 2.16.840.1.113883.4.642.4.1819

This Code system is not currently used

The checklist items icon defined as part of the FHIR specification.

This case-sensitive code system http://hl7.org/fhir/safety-entries defines the following codes in a Is-A heirarchy:


For each resource that my system handles, my system handles the full Life cycle (status codes, currency issues, and erroneous entry status)

btn btn

For each resource that my system handles, I've reviewed the Modifier elements

btn btn

My system checks for modifierExtension elements

btn btn

My system supports elements labeled as 'MustSupport' in the profiles that apply to my system

btn btn

My system has documented how distributed resource identification works in its relevant contexts of use, and where (and why) contained resources are used

btn btn

My system manages lists of current resources correctly

btn btn

When other systems return http errors from the RESTful API and Operations (perhaps using Operation Outcome), my system checks for them and handles them appropriately

btn btn

My system ensures checks for patient links (and/or merges) and handles data that is linked to patients accordingly

btn btn

My system publishes a Capability Statement with StructureDefinitions, ValueSets, and OperationDefinitions, etc., so other implementers know how the system functions

btn btn

All resources in use are valid against the base specification and the profiles that apply to my system (see note about the correct run-time use of validation)

btn btn

I've reviewed the Observation resource, and understand how focus is a mechanism for observations to be about someone or something other than the patient or subject of record.

btn btn

My system checks for timezones and adjusts times appropriately. (note: timezones are extremely difficult to get correct - see W3C Timezone Advice icon, and note that some fields should be timezone corrected, and others should not be)

btn btn

My system renders dates safely for changes in culture and language (the date formats D-M-Y and M-D-Y are not differentiated for many dates, and this is a well-known source of confusion. Systems should use the month name, or otherwise be specific for each date when rendering, unless there is solid confidence that such confusion cannot arise, even in the future when information/narrative from resources will be shared much more widely)

btn btn

My system takes care to ensure that clients can (for servers) or will (for clients) find the information they need when content that might reasonably be exposed using more than one FHIR resource. Possible patterns: Support a single search across the applicable resources, or expose data through each applicable resource. See discussion on Wiki Page icon for further information

btn btn

My system will display warnings returned by the server to the user

btn btn

My system checks whether the server processed all the requested search parameter, and is safe if servers ignore parameters (typically, either filters locally or warns the user)

btn btn

My system caters for parameters that have missing values when doing search operations, and responds correctly to the client with regard to erroneous search parameters

btn btn

My system includes appropriate default filters when searching based on patient context - e.g. filtering out entered-in-error records, filtering to only include active, living patients if appropriate, and clearly documents these (preferably including them in the self link for a search

btn btn

For each resource, I have checked whether resources can be deleted, and/or how records are marked as incorrect/no longer relevant

btn btn

Deletion of records (or equivalent updates in status) flow through the system so any replicated copies are deleted/updated

btn btn

(If a server) my documentation about deleted resources is clear, and my test sandbox (if exists) has deleted/error record cases in the test data

btn btn

My system checks that the right Patient consent has been granted (where applicable)

btn btn

My system sends an Accounting of Disclosure to the consenter as requested when permitted actions on resources are performed using an AuditEvent Resource

btn btn

My system ensures that system clocks are synchronized using a protocol like NTP or SNTP, or my server is robust against clients that have the wrong clock set

btn btn

My system uses security methods for an API to authenticate where Domain Name System (DNS) responses are coming from and ensure that they are valid

btn btn

Production exchange of patient or other sensitive data will always use some form of encryption on the wire

btn btn

Where resources are exchanged using HTTP, TLS icon should be utilized to protect the communications channel

btn btn

Where resources are exchanged using email, S/MIME icon should be used to protect the end-to-end communication

btn btn

Production exchange should utilize recommendations for Best-Current-Practice on TLS in BCP 195 icon

btn btn

My system utilizes a risk and use case appropriate OAuth profile (preferably Smart App Launch icon), with a clear policy on authentication strength

btn btn

My system uses OpenID Connect icon (or other suitable authentication protocol) to verify identity of end user, where it is necessary that end-users be identified to the client application, and has a clear policy on identity proofing

btn btn

My system applies appropriate access control to every request, using a combination of requester’s clearance (ABAC) and/or roles (RBAC)

btn btn

My system considers security labels on the affected resources when making access control decisions

btn btn

My system can render narratives properly and securely(where they are used)

btn btn

My system validates all input received (whether in resource format or other) from other actors so that it data is well-formed and does not contain content that would cause unwanted system behavior

btn btn

My system makes the right Provenance statements and AuditEvent logs, and uses the right security labels where appropriate

btn btn

Server: CORS (cross-origin resource sharing icon) is appropriately enabled (many clients are Javascript apps running in a browser)

btn btn

JSON is supported (many clients are Javascript apps running in a browser; XML is inconvenient at best)

btn btn

JSON is returned correctly when errors happen (clients often don't handle HTML errors well)

btn btn

The _format header is supported correctly

btn btn

Errors are trapped and an OperationOutcome returned

btn btn


See the full registry of code systems defined as part of FHIR.

Explanation of the columns that may appear on this page:

LevelA few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code