??.?? Logical Model definition - Content

??.??.1 Scope and Usage

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.)

??.??.2 Boundaries and Relationships

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/

??.??.3 Background and Context

This resource 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.

Unlike the request and event patterns, this pattern has not yet been formally reviewed, nor applied to any of its candidate resources. It should therefore be treated as a draft for comment. Alignment with this pattern (and the content of the pattern) will be discussed by work groups as part of ballot reconciliation.

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
• UML
• Both

Structure

Name	Flags	Card.	Type	Description & Constraints
Definition			Logical	Definition Pattern
identifier	Σ	0..1	Identifier	Business Identifer for definition/protocol
definition	Σ	0..*	Reference(Definition)	Instantiates protocol or definition
parent	Σ	0..*	Reference(Definition)	Part of referenced definition
replaces	Σ	0..*	Reference(Definition)	Request(s) replaced by this request
status	?!Σ	1..1	code	draft | active | withdrawn DefinitionStatus (Required)
subject[x]	Σ	0..1		Type of individual the defined service is for
subjectCodeableConcept			CodeableConcept
subjectReference			Reference(Group)
date	Σ	0..1	dateTime	Date status first applied
author	Σ	0..1	Reference(Practitioner | Organization)	Who/what is requesting service
performerType	Σ	0..1	CodeableConcept	Desired kind of service performer
Documentation for this format

Structure

Name	Flags	Card.	Type	Description & Constraints
Definition			Logical	Definition Pattern
identifier	Σ	0..1	Identifier	Business Identifer for definition/protocol
definition	Σ	0..*	Reference(Definition)	Instantiates protocol or definition
parent	Σ	0..*	Reference(Definition)	Part of referenced definition
replaces	Σ	0..*	Reference(Definition)	Request(s) replaced by this request
status	?!Σ	1..1	code	draft | active | withdrawn DefinitionStatus (Required)
subject[x]	Σ	0..1		Type of individual the defined service is for
subjectCodeableConcept			CodeableConcept
subjectReference			Reference(Group)
date	Σ	0..1	dateTime	Date status first applied
author	Σ	0..1	Reference(Practitioner | Organization)	Who/what is requesting service
performerType	Σ	0..1	CodeableConcept	Desired kind of service performer
Documentation for this format

UML Diagram (Legend)