StructureDefinition-UKCore-Flag


Command 'tree' could not render: Resource was not found for 'canonical=https://fhir.hl7.org.uk/StructureDefinition/UKCore-Flag'

Detailed Descriptions

Command 'dict' could not render: Resource was not found for 'canonical=https://fhir.hl7.org.uk/StructureDefinition/UKCore-Flag'

Table View

Command 'table' could not render: Resource was not found for 'canonical=https://fhir.hl7.org.uk/StructureDefinition/UKCore-Flag'

XML View

Command 'xml' could not render: Resource was not found for 'canonical=https://fhir.hl7.org.uk/StructureDefinition/UKCore-Flag'

JSON View

Command 'json' could not render: Resource was not found for 'canonical=https://fhir.hl7.org.uk/StructureDefinition/UKCore-Flag'

Usage

This Profile has the following derived profiles:


This Profile is referenced in the following Extensions:


This Profile is referenced in the following Profiles:

Feedback

Click here to:

, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Examples

Food Allergy - An example to illustrate a flag regarding a food allergy.
Example UKCore-Flag-FoodAllergy

Example Usage Scenarios

The following are example usage scenarios for the UK Core Flag profile:

  • Query for flag information for a given Patient
  • Exchange flag information within a FHIR document or message.

Profile Specific Implementation Guidance:

Minimum Viable Content

A minimum viable content that all provider and consumer systems SHALL support are the following elements.

Element Reason
Flag.status Supports basic workflow.
Flag.code The coded value or textual component of the flag to display to the user.
Flag.subject The patient, location, group, organization, or practitioner etc. this is about record this flag is associated with.

subject

Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles:


encounter

Where possible, it is expected that the resource being referenced SHOULD conform to Profile UKCore-Encounter.


author

Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles: