HealtheData1 USCDI4 Sandbox
0.0.0 - CI Build United States of America flag

HealtheData1 USCDI4 Sandbox - Local Development build (v0.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Guidance

Page standards status: Informative

Guidance

Referencing US Core Profiles

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc imperdiet nunc at massa porta rutrum. Duis ac nulla a velit hendrerit vehicula at nec urna. Sed gravida pellentesque molestie. Praesent commodo, sem et tincidunt vulputate, nisl nibh

Contained Resources

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc imperdiet nunc at massa porta rutrum. Duis ac nulla a velit hendrerit vehicula at nec urna. Sed gravida pellentesque molestie. Praesent commodo, sem et tincidunt vulputate, nisl nibh

Suppressed Data

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc imperdiet nunc at massa porta rutrum. Duis ac nulla a velit hendrerit vehicula at nec urna. Sed gravida pellentesque molestie. Praesent commodo, sem et tincidunt vulputate, nisl nibh

SNOMED CT United States Edition

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc imperdiet nunc at massa porta rutrum. Duis ac nulla a velit hendrerit vehicula at nec urna. Sed gravida pellentesque molestie. Praesent commodo, sem et tincidunt vulputate, nisl nibh

SNOMED CT Edition and Version Options

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc imperdiet nunc at massa porta rutrum. Duis ac nulla a velit hendrerit vehicula at nec urna. Sed gravida pellentesque molestie. Praesent commodo, sem et tincidunt vulputate, nisl nibh

Using UCUM codes in the [Quantity] datatype

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc imperdiet nunc at massa porta rutrum. Duis ac nulla a velit hendrerit vehicula at nec urna. Sed gravida pellentesque molestie. Praesent commodo, sem et tincidunt vulputate, nisl nibh

Representing Deleted Information

A FHIR Server SHOULD not delete records. A FHIR server SHOULD update the appropriate resource status to entered-in-error or inactive (refer to the next section on Representing Entered in Error Information). If a system supports the deletion of records, they SHOULD refer to the [Deletion Safety Checks] in the FHIR specification.

Representing Entered in Error Information

Clinical information that has been entered in error in the patient’s record needs to be represented by the FHIR Server in a way so that Clients can expose the corrected information to their end users.

Server Recommendations:

  • A FHIR Server SHOULD not delete resources.
  • A FHIR server SHOULD update the appropriate resource status to entered-in-error or inactive.
  • A FHIR Server SHOULD allow these resources to be searchable by client applications.
  • If the FHIR server has updated the resource status to entered-in-error:
    • For patient facing applications, A FHIR Server SHOULD remove the contents of resource leaving only an id and status. Note this typically will not be conformant with the US Core or FHIR StructureDefinitions.
    • For provider-facing applications, the content may be supplied with content and additional detail (such as the reason for the status change) that the patient viewing system would typically not have access to.

Narrative

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc imperdiet nunc at massa porta rutrum. Duis ac nulla a velit hendrerit vehicula at nec urna. Sed gravida pellentesque molestie. Praesent commodo, sem et tincidunt vulputate, nisl nibh

Language Support

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc imperdiet nunc at massa porta rutrum. Duis ac nulla a velit hendrerit vehicula at nec urna. Sed gravida pellentesque molestie. Praesent commodo, sem et tincidunt vulputate, nisl nibh

Timezone and Time Offsets (STRAWMAN PROPOSAL)

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc imperdiet nunc at massa porta rutrum. Duis ac nulla a velit hendrerit vehicula at nec urna. Sed gravida pellentesque molestie. Praesent commodo, sem et tincidunt vulputate, nisl nibh

Read (Fetch) Syntax

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc imperdiet nunc at massa porta rutrum. Duis ac nulla a velit hendrerit vehicula at nec urna. Sed gravida pellentesque molestie. Praesent commodo, sem et tincidunt vulputate, nisl nibh

Search Syntax

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc imperdiet nunc at massa porta rutrum. Duis ac nulla a velit hendrerit vehicula at nec urna. Sed gravida pellentesque molestie. Praesent commodo, sem et tincidunt vulputate, nisl nibh

Searching Multiple Patients

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc imperdiet nunc at massa porta rutrum. Duis ac nulla a velit hendrerit vehicula at nec urna. Sed gravida pellentesque molestie. Praesent commodo, sem et tincidunt vulputate, nisl nibh

Searching Multiple Patients

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc imperdiet nunc at massa porta rutrum. Duis ac nulla a velit hendrerit vehicula at nec urna. Sed gravida pellentesque molestie. Praesent commodo, sem et tincidunt vulputate, nisl nibh

Searching using lastUpdated

Servers that can accurately populate Meta.lastUpdated SHOULD support the _lastUpdated search parameter as defined in the core FHIR specifications. If Meta.lastUpdated is populated:

  • Note to clients that the most recent time does not necessarily reflect changes they can access. A record may change, but the client’s view of the resource may not (for example, if the client is not authorized to see the changed data).
  • Supporting Meta.lastUpdated in a resource does not imply support for searches using the _lastUpdated search parameter.
  • Support for searches using the _lastUpdated search parameter does not require servers to support Meta.lastUpdated; servers can use an alternative method to reliably track changes to an instance.
  • Note to servers that updating the timestamp too frequently is better than missing updates.

Many servers are unable to populate the Meta.lastUpdated element accurately. However, they SHOULD expose a method for clients to know if there are new or modified resources since their last polling time and advertise that mechanism in their CapabilityStatement. Work is in progress to:

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc imperdiet nunc at massa porta rutrum. Duis ac nulla a velit hendrerit vehicula at nec urna. Sed gravida pellentesque molestie. Praesent commodo, sem et tincidunt vulputate, nisl nibh

Across Platform Searches

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nunc imperdiet nunc at massa porta rutrum. Duis ac nulla a velit hendrerit vehicula at nec urna. Sed gravida pellentesque molestie. Praesent commodo, sem et tincidunt vulputate, nisl nibh

Limiting The Number Of Search Results