Release 4

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) in it's permanent home (it will always be available at this URL). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

12.2 Pattern definition - Content

FHIR Infrastructure Maturity Level: 1Informative

A pattern to be followed by resources that represent a specific proposal, plan and/or order for some sort of action or service.

This is NOT a resource. It is not part of the FHIR schema and cannot appear directly in FHIR instances. It is a logical model that defines a pattern adhered to by other resources. This pattern serves two purposes:

  • It offers guidance to work groups designing resources and helps ensure consistency of content created by different work groups
  • It provides a standard "view" that might be useful for implementers in processing and manipulating all resources that adhere to the same pattern. (Tooling that supports this may become available in a future release.)

This pattern describes common properties typically found on "definition" resources. "Definition" resources are resources that describe clinical, administrative or other events that can potentially occur. They do so in a manner that is independent of a particular patient or subject and independent of any particular timeframe. Examples include protocols, order sets, questionnaires, etc. Definitions are intended to be instantiated by Requests (orders, plans and proposals) and Events. For example a PlanDefinition might represent an order set that is subsequently instantiated by a combination of MedicationRequests and ServiceRequests and results in the execution of various MedicationAdministration, Procedure and Observation events. This pattern only applies to definitions of activities, not of objects or roles.

This logical model is one of three common workflow patterns. The other two patterns are Event and Request. This pattern is followed by (or is intended to be followed by a number of other FHIR resources/

Both definitions and requests deal with activities that "can" occur, but requests represent a specific intention for something to occur and are bound to a specific context of subject and time, while definitions represent mere "possibility" rather than intention and are independent of a specific subject or timeframe.

This model represents a pattern. It provides a standard list of data elements with cardinalities, data types, definitions, rationale and usage notes that will ideally be adhered to by resources that fall into the "definition" workflow category. However, adherence to this pattern is not mandatory. Not all healthcare domains are the same. Concepts that may be generally applicable (and thus are included in this standard pattern) might still not be relevant everywhere or may be sufficiently uncommon that they are more appropriate to include as extensions than as core properties of the resource. Work groups are encouraged to adjust descriptions, usage notes and rationale to be specific to their resource (e.g. use the term "protocol" or "questionnaire" rather than "definition"). As well, design notes in the comments column marked with [square brackets] identifies areas where domain variation is expected and encouraged. Other variation, including differences in names, cardinalities, data types and the decision to omit an element outright are also possible, but should be discussed with the FHIR Infrastructure work group's Workflow project to ensure the rationale for non-alignment is understood, to confirm that the deviation is necessary and to identify whether any adjustments to the pattern are appropriate.

This pattern provides a linkage to the W5 list of standard data elements. Resources that adhere to this pattern should ensure their w5 mappings are consistent, as is their data element ordering.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Definition ILogicalDefinition Pattern
... url Σ0..1uriLogical canonical URL to reference this {{title}} (globally unique)
... identifier Σ0..1IdentifierBusiness Identifier for {{title}}
... version Σ0..1stringBusiness version of the {{title}}
... title Σ0..1stringName for this {{title}} (Human friendly)
... derivedFromCanonical Σ0..*canonical(Definition)Based on FHIR protocol or definition
... derivedFromUri Σ0..*uriBased on external protocol or definition
... partOf Σ0..*canonical(Definition)Part of referenced definition
... replaces Σ0..*canonical(Definition)Request(s) replaced by this request
... status ?!Σ1..1codedraft | active | retired | unknown
PublicationStatus (Required)
... experimental ?!Σ0..1booleanIf for testing purposes, not real usage
... subject[x] Σ0..1Type of individual the defined service is for
.... subjectCodeableConceptCodeableConcept
.... subjectReferenceReference(Group)
... date Σ0..1dateTimeDate status first applied
... publisher Σ0..1Reference(Practitioner | PractitionerRole | Organization)The name of the individual or organization that published the {{title}}
... contact Σ0..*ContactDetailContact details for the publisher
... description 0..1markdownNatural language description of the {{title}}
... useContext Σ0..*UsageContextContent intends to support these contexts
... jurisdiction Σ0..*CodeableConceptIntended jurisdiction for {{title}} (if applicable)
Jurisdiction (Extensible)
... purpose 0..1markdownWhy this {{title}} is defined
... copyright 0..1markdownUse and/or publishing restrictions
... approvalDate 0..1dateWhen {{title}} approved by publisher
... lastReviewDate 0..1dateLast review date for the {{title}}
... effectivePeriod Σ0..1PeriodThe effective date range for the {{title}}
... performerType Σ0..1CodeableConceptDesired kind of service performer

doco Documentation for this format

UML Diagram (Legend)

Definition (Logical)🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025url : uri [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025identifier : Identifier [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025version : string [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025title : string [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025derivedFromCanonical : canonical [0..*] « Definition »🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025derivedFromUri : uri [0..*]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025partOf : canonical [0..*] « Definition »🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025replaces : canonical [0..*] « Definition »🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025status : code [1..1] « 🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025PublicationStatus! »🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025experimental : boolean [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025subject[x] : Type [0..1] « CodeableConcept|Reference(Group) »🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025date : dateTime [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025publisher : Reference [0..1] « Practitioner|PractitionerRole| Organization »🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025contact : ContactDetail [0..*]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025description : markdown [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025useContext : UsageContext [0..*]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025jurisdiction : CodeableConcept [0..*] « 🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025Jurisdiction ValueSet+ »🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025purpose : markdown [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025copyright : markdown [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025approvalDate : date [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025lastReviewDate : date [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025effectivePeriod : Period [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025performerType : CodeableConcept [0..1]

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Definition ILogicalDefinition Pattern
... url Σ0..1uriLogical canonical URL to reference this {{title}} (globally unique)
... identifier Σ0..1IdentifierBusiness Identifier for {{title}}
... version Σ0..1stringBusiness version of the {{title}}
... title Σ0..1stringName for this {{title}} (Human friendly)
... derivedFromCanonical Σ0..*canonical(Definition)Based on FHIR protocol or definition
... derivedFromUri Σ0..*uriBased on external protocol or definition
... partOf Σ0..*canonical(Definition)Part of referenced definition
... replaces Σ0..*canonical(Definition)Request(s) replaced by this request
... status ?!Σ1..1codedraft | active | retired | unknown
PublicationStatus (Required)
... experimental ?!Σ0..1booleanIf for testing purposes, not real usage
... subject[x] Σ0..1Type of individual the defined service is for
.... subjectCodeableConceptCodeableConcept
.... subjectReferenceReference(Group)
... date Σ0..1dateTimeDate status first applied
... publisher Σ0..1Reference(Practitioner | PractitionerRole | Organization)The name of the individual or organization that published the {{title}}
... contact Σ0..*ContactDetailContact details for the publisher
... description 0..1markdownNatural language description of the {{title}}
... useContext Σ0..*UsageContextContent intends to support these contexts
... jurisdiction Σ0..*CodeableConceptIntended jurisdiction for {{title}} (if applicable)
Jurisdiction (Extensible)
... purpose 0..1markdownWhy this {{title}} is defined
... copyright 0..1markdownUse and/or publishing restrictions
... approvalDate 0..1dateWhen {{title}} approved by publisher
... lastReviewDate 0..1dateLast review date for the {{title}}
... effectivePeriod Σ0..1PeriodThe effective date range for the {{title}}
... performerType Σ0..1CodeableConceptDesired kind of service performer

doco Documentation for this format

UML Diagram (Legend)

Definition (Logical)🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025url : uri [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025identifier : Identifier [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025version : string [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025title : string [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025derivedFromCanonical : canonical [0..*] « Definition »🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025derivedFromUri : uri [0..*]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025partOf : canonical [0..*] « Definition »🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025replaces : canonical [0..*] « Definition »🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025status : code [1..1] « 🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025PublicationStatus! »🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025experimental : boolean [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025subject[x] : Type [0..1] « CodeableConcept|Reference(Group) »🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025date : dateTime [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025publisher : Reference [0..1] « Practitioner|PractitionerRole| Organization »🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025contact : ContactDetail [0..*]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025description : markdown [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025useContext : UsageContext [0..*]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025jurisdiction : CodeableConcept [0..*] « 🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025Jurisdiction ValueSet+ »🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025purpose : markdown [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025copyright : markdown [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025approvalDate : date [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025lastReviewDate : date [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025effectivePeriod : Period [0..1]🏆 ยอดนิยม: fhir/R/definition.html - Kapook Update 2025performerType : CodeableConcept [0..1]

 

alternate definitions: Master Definition XML + JSON.

PathDefinitionTypeReference
Definition.status The lifecycle status of an artifact.RequiredPublicationStatus
Definition.subject[x] Codes identifying the type of subject intended to be the recpient or focus of the defined action. These should ideally be consistent across definition resources.UnknownNo details provided yet
Definition.jurisdiction Countries and regions within which this artifact is targeted for use.ExtensibleJurisdiction ValueSet
Definition.performerType Identifies types of practitioners, devices or other agents that are intended to perform a defined action. While the detailed constraints of relevant agents will vary by resource, some degree of consistency around recommended codes across request and definition resources would be desirable.UnknownNo details provided yet

The following diagram shows the "typical" state machine diagram for resources following the Definition pattern. Note that not all resources will support all states, some resources may choose different names for certain states and some resources may introduce sub-states to the listed states. As well, additional transitions may be supported, including from terminal nodes (e.g. from "withdrawn" back to "active"). That said, most resources should align with this state machine fairly well.

Typical state machine diagram for resources following 
  the Definition pattern
url identifier version title derivedFromCanonical derivedFromUri partOf replaces status experimental subject[x] date publisher contact description useContext jurisdiction purpose copyright approvalDate lastReviewDate effectivePeriod performerType
ActivityDefinition 1 1 C 1 1 1 1 1 1 1 1 1 1 1 1 1
CapabilityStatement 1 1 1 1 1 1 1 T 1 1 1 1 1 1
ChargeItemDefinition 1 1 C 1 1 1 1 1 1 1 1 1 1 1 1
CodeSystem 1 1 C 1 1 1 1 1 1 T 1 1 1 1 1 1
CompartmentDefinition 1 1 1 1 1 1 T 1 1 1 1
ConceptMap 1 1 1 1 1 1 1 1 T 1 1 1 1 1 1
EffectEvidenceSynthesis 1 1 C 1 1 1 1 1 T 1 1 1 1 1 1 1 1
EventDefinition 1 1 C 1 1 1 1 1 1 T 1 1 1 1 1 1 1 1 1
Evidence 1 1 C 1 1 1 1 1 T 1 1 1 1 1 1 1 1
EvidenceVariable 1 1 C 1 1 1 1 1 T 1 1 1 1 1 1 1 1
ExampleScenario 1 1 C 1 1 1 1 1 T 1 1 1 1 1
GraphDefinition 1 1 1 1 1 1 T 1 1 1 1 1
ImplementationGuide 1 1 1 1 1 1 1 T 1 1 1 1 1
Library 1 1 C 1 1 1 1 1 1 T 1 1 1 1 1 1 1 1 1
Measure 1 1 C 1 1 1 1 1 1 T 1 1 1 1 1 1 1 1 1
MessageDefinition 1 1 C 1 1 1 1 1 1 T 1 1 1 1 1 1
NamingSystem 1 1 1 T 1 1 1 1
OperationDefinition 1 1 2 N 1 1 NTC 1 1 T 1 1 1 1 1
PlanDefinition 1 1 C 1 2 1 1 NC 1 1 T 1 3 NT 1 1 1 1 1 1 1
Questionnaire 1 1 C 1 1 1 1 1 NTC 1 1 T 1 1 1 1 1 1 1 1 1
ResearchDefinition 1 1 C 1 1 1 1 1 1 T 1 1 1 1 1 1 1 1 1
ResearchElementDefinition 1 1 C 1 1 1 1 1 1 T 1 1 1 1 1 1 1 1 1
RiskEvidenceSynthesis 1 1 C 1 1 1 1 1 T 1 1 1 1 1 1 1 1
SearchParameter 1 1 1 1 1 1 T 1 1 1 1 1
StructureDefinition 1 1 C 1 1 1 1 1 1 T 1 1 1 1 1 1
StructureMap 1 1 C 1 1 1 1 1 1 T 1 1 1 1 1 1
TerminologyCapabilities 1 1 1 1 1 1 1 T 1 1 1 1 1 1
TestScript 1 1 1 1 1 1 1 1 T 1 1 1 1 1 1
ValueSet 1 1 C 1 1 1 1 1 1 T 1 1 1 1 1 1