This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). 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

2.33 Pattern fivews - Content

FHIR Infrastructure

Maturity Level: 1

Informative

Who What When Where Why - Common pattern for all resources that deals with attribution.

2.33.1 Scope and Usage

All resources include some attribution information. Classically, this information includes:

Who
What
When
Where
Why

This is classically known as the 'Five Ws' - hence the name of this pattern. The pattern also includes additional information that is common across many resources.

The Five Ws logical model is NOT a resource. It is not part of the FHIR schema and cannot appear directly in FHIR instances. Instead, it 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.)

Note that the guidance here is around the types of information that might be captured, not around element names. For example "why" would more typically be labeled as something like "reason" and "where" would be more typically labeled "location"

2.33.2 Boundaries and Relationships

To do

2.33.3 Background and Context

To do

2.33.4 References

No resources follow this pattern.

Structure

Name	Flags	Card.	Type	Description & Constraints
FiveWs	I		Logical	Who What When Where Why - Common pattern for all resources that deals with attribution
identifier		0..*	Identifier	Business Identifier
version		0..1	string	Identifier for this version
status	?!	0..1	code	Status Field Canonical Status Codes for FHIR Resources (Required)
class		0..*	CodeableConcept	Classifier Field
grade		0..1	CodeableConcept	A field that indicates the potential impact of the content of the resource
what[x]		0..1		What this resource is about
whatCodeableConcept			CodeableConcept
whatReference			Reference(Any)
subject		0..*	Reference(Patient \| Practitioner \| RelatedPerson \| Organization)	Who this resource is about
context		0..1	Reference(Encounter \| EpisodeOfCare)	Context for the work described in this resource
init		0..1	dateTime	When the work described in this resource was started (or will be)
planned		0..*	Timing	When this resource is planned to occur
done[x]		0..1		When the work described in this resource was completed (or will be)
doneDateTime			dateTime
donePeriod			Period
recorded		0..1	instant	When this resource itself was created
author		0..*	Reference(Patient \| Practitioner \| RelatedPerson \| Organization)	Who authored the content of the resource
source		0..*	Reference(Patient \| Practitioner \| RelatedPerson \| Organization)	Who provided the information in this resource
actor		0..*	Reference(Patient \| Practitioner \| RelatedPerson \| Organization)	Who did the work described the resource (or will do)
cause		0..*	Reference(Patient \| Practitioner \| RelatedPerson \| Organization)	Who prompted the work described in the resource
witness		0..*	Reference(Patient \| Practitioner \| RelatedPerson)	Who attests to the content of the resource (individual or org)
who		0..*	Reference(Patient \| Practitioner \| RelatedPerson \| Organization)	An actor involved in the work described by this resource
where[x]		0..*		The location of the work described
whereCodeableConcept			CodeableConcept
whereReference			Reference(Location)
why[x]		0..*		Why this work was done
whyCodeableConcept			CodeableConcept
whyReference			Reference(Any)
Documentation for this format

UML Diagram (Legend)

Structure

Name	Flags	Card.	Type	Description & Constraints
FiveWs	I		Logical	Who What When Where Why - Common pattern for all resources that deals with attribution
identifier		0..*	Identifier	Business Identifier
version		0..1	string	Identifier for this version
status	?!	0..1	code	Status Field Canonical Status Codes for FHIR Resources (Required)
class		0..*	CodeableConcept	Classifier Field
grade		0..1	CodeableConcept	A field that indicates the potential impact of the content of the resource
what[x]		0..1		What this resource is about
whatCodeableConcept			CodeableConcept
whatReference			Reference(Any)
subject		0..*	Reference(Patient \| Practitioner \| RelatedPerson \| Organization)	Who this resource is about
context		0..1	Reference(Encounter \| EpisodeOfCare)	Context for the work described in this resource
init		0..1	dateTime	When the work described in this resource was started (or will be)
planned		0..*	Timing	When this resource is planned to occur
done[x]		0..1		When the work described in this resource was completed (or will be)
doneDateTime			dateTime
donePeriod			Period
recorded		0..1	instant	When this resource itself was created
author		0..*	Reference(Patient \| Practitioner \| RelatedPerson \| Organization)	Who authored the content of the resource
source		0..*	Reference(Patient \| Practitioner \| RelatedPerson \| Organization)	Who provided the information in this resource
actor		0..*	Reference(Patient \| Practitioner \| RelatedPerson \| Organization)	Who did the work described the resource (or will do)
cause		0..*	Reference(Patient \| Practitioner \| RelatedPerson \| Organization)	Who prompted the work described in the resource
witness		0..*	Reference(Patient \| Practitioner \| RelatedPerson)	Who attests to the content of the resource (individual or org)
who		0..*	Reference(Patient \| Practitioner \| RelatedPerson \| Organization)	An actor involved in the work described by this resource
where[x]		0..*		The location of the work described
whereCodeableConcept			CodeableConcept
whereReference			Reference(Location)
why[x]		0..*		Why this work was done
whyCodeableConcept			CodeableConcept
whyReference			Reference(Any)
Documentation for this format

UML Diagram (Legend)

alternate definitions: Master Definition XML + JSON.

2.33.5.1 Terminology Bindings

Path	Definition	Type	Reference
FiveWs.status	Status Field.	Required	CanonicalStatusCodesForFHIRResources

Path

Definition

Type

Reference

FiveWs.status

Status Field.

Required

CanonicalStatusCodesForFHIRResources

Todo

2.33.5.2 Mappings

	identifier	version	status	class	grade	what[x]	subject	context	init	planned	done[x]	recorded	author	source	actor	cause	witness	who	where[x]	why[x]
Account	1		1	1 N		1 N	1				1 N
ActivityDefinition	2 N	1	1	1 N								1 N					1 N			1 N
AdverseEvent			1	2 N		1 N	1	1 N			1 N	1 N	1 N		1
AllergyIntolerance	1		2 N	2 N	1 N	1 N	1 N	1 N	1 N			1 N	1 N	1 N
Appointment	1		1	2 N				1 NC	1 N		1 N							1 N
AppointmentResponse	1								1 N		1 N							1 N
AuditEvent						8 NC		8 NC			1 N	1					4 N	7 N	5 N	3 N
Basic	1					1 N	1					1 N	1
BiologicallyDerivedProduct	1
BodyStructure	1		1 N			5 NC	1 N
Bundle	1			1 N					1 N
CapabilityStatement	1 N	1	1	1 N								1 N					1 N			1 N
CapabilityStatement2	1 N	1	1	1 N								1 N					1 N			1 N
CarePlan	1		1	1 N		1 N	1	1 N		1 N		1 N	1	1 N	1 N					1 N
CareTeam	1		1	1 N			1		1 N						1 N					1 N
ChargeItem	1		1			1 N	1	1			1 N				2 N					2 N
ChargeItemDefinition	2 N	1	1	1 N								1 N					1 N
Claim	2		1	3 N			1 N				2 N	1 N	1 N	1 N	1 N	1 N			2 N
ClaimResponse	1		1	3 N			1 N				1 N	1 N		2 N					1 N	1 N
ClinicalImpression	1		1				1	1 N			1 N	1 N			1 N					1 N
CodeSystem	2 N	1	1	1 N								1 N					1 N			1 N
Communication	1		1	1 N	1 N		1	3 NC			2 N				2 N					1 N
CommunicationRequest	1		1	1 N	1 N		1	2 NC		1 N		1 N	1 N		2 N					1 N
CompartmentDefinition	1 N	1	1	1 N								1 N					1 N			1 N
Composition	1		1	3 N			1	1 N			1 N		2				1 N
ConceptMap	2 N	1	1	1 N								1 N					1 N			1 N
Condition	1		2 N	1 N	1 N	1 N	1	1 N	1 N		1 N	1 N	1 N	1 N						2 N
ConditionDefinition	2 N	1	1	1 N								1 N					1 N
Consent	1		1	1 N			1 N					1 N			1 N		1 N
Contract			1			21 NC					2 N	1 N	2 N		1 N					1 N
Coverage	1		1	1 N			4 N				1 N		1 N
CoverageEligibilityRequest	1		1	2 N			1 N				1 N	1 N	1 N	2 N				1 N	1 N
CoverageEligibilityResponse	1		1	1 N			1 N				1 N	1 N		2 N						1 N
DetectedIssue	1		1	1 N	1 N		1 N					1 N	1							3 N
Device	2 N		2 NC			12 N	1 N							2 N					2 N
DeviceDefinition	1					4 N								2 N					1 N
DeviceMetric	1			2 N
DeviceRequest	1		1	1 N	1 N	4 NC	1	1 N		1 N		1 N	1 N		2 N					1 N
DeviceUseStatement	1		1				1				1 N	1 N			2 N					1 N
DiagnosticReport	1		1	1 N		1 N	1	1 N			1 N	1 N			2 N
DocumentManifest	2 N		1	1 N			1				1 N		1			1 N
DocumentReference	2 N		2 N			2 NC	1	1 NC				1 N					1 N
Encounter	1		1	2 N	1 N		1	1 NC			1 N							1 N	1 N	2 N
Endpoint	1		1	1 N		1 N					1 N
EnrollmentRequest															2 N
EnrollmentResponse															1 N
EpisodeOfCare	1		1	1 N		1 N	1 N		1 N
EventDefinition	2 N	1	1	1 N								1 N					1 N			1 N
Evidence	2 N	1	1									1 N
EvidenceVariable	2 N	1	1									1 N					1 N
ExampleScenario	2 N	1	1	1 N								1 N					1 N			1 N
ExplanationOfBenefit	1		1	3 N			1 N				3 N	1 N	2 N	2 N	1 N	1 N			3 N	1 N
FamilyMemberHistory	1		1				1 N					1 N								1 N
Flag	1		1	1 N		1 N	1	2 N					1
Goal	1		1 N	1 N	1 N	1 N	1			1 N	1 N	1 N		1 N						1 N
GraphDefinition	1 N	1	1	1 N								1 N					1 N			1 N
Group	1		1 N	2 N		1 N
GuidanceResponse	1		1				1	1 N			1 N				1 N					1 N
HealthcareService	1		1 N	1 N															1 N
ImagingStudy	1		1	1 N			1	1 N	1 N						1	2 N	1 N		1 N	1 N
Immunization	1		1			1 N	1 N	1 N			1 N	1		2 N	1				1 N
ImmunizationEvaluation	1		1				1 N		1 N
ImmunizationRecommendation	1						1 N
ImplementationGuide	1 N	1	1	1 N								1 N					1 N
InsurancePlan	2		1	1 N
Invoice	1		1			1 N	1				1 N				1
Library	2 N	1	1	1 N		1 N						1 N					1 N			1 N
Linkage			1 N										1
List	1		1	1 N		1 N	1	1 N				1 N	1 N
Location	1		2 N	3 N
Measure	2 N	1	1	1 N								1 N					1 N			1 N
MeasureReport	1		1	1 N		1 N	1					1 N		1 N
Medication	1			1 N											1 N
MedicationAdministration	1		1			1 N	1	2 NC			1 N	1			1 N
MedicationDispense	1		1			1 N	1	1 NC
MedicationKnowledge				1 N											1 N
MedicationRequest	1		1	2 N	1 N	1 N	1	2 NC				1 N	1 N		1 N			2 N		1 N
MedicationUsage	1		1	1 N		1 N	1				1 N	1 N		1 N						1 N
MessageDefinition	2 N	1	1	1 N								1 N					1 N			1 N
MessageHeader						1 N	3 N						2 N		1 N		1 N			1 N
MolecularSequence	1
NamingSystem	2 N	1	1	1 N								1 N					2 N
NutritionIntake	1		1	1 N		1 N	1				1 N	1 N		1 N						1 N
NutritionOrder	1		1	1 N		5 NC	1 N	1 N				1 N	1 N
Observation	1		1	1 N		2 N	2 N	1 N			1 N	1 N			1 N
ObservationDefinition				1 N		1 N
OperationDefinition	1 N	1	1	2 N								1 N					1 N			1 N
Organization	1		1 N	1 N
OrganizationAffiliation	1		1 N								1 N								1 N
Patient	1		1 N
PaymentNotice	1		1				2 N					1 N		1 N
PaymentReconciliation	1		1								1 N	1 N		1 N						1 N
Person	1		1 N
PlanDefinition	2 N	1	1	1 N								1 N					1 N			1 N
Practitioner	1		1 N
PractitionerRole	1		1 N								1 N								1 N
Procedure	1		1	1 N		1 N	1	1 N			1 N	1	1 N	1 N	1				1 N	1 N
Provenance						1 NC					1 N	1			1 N			1 N	1 N	2 N
Questionnaire	2 N	1	1	1 N								1 N					1 N			1 N
QuestionnaireResponse	1		1				1	1 N				1 N	1	1
RelatedPerson	1		1 N	1 N							1 N
RequestGroup	1		1	1 N	1 N	1 N	1	1 N				1 N	1		1 N					1 N
ResearchStudy	1		1			2 NC	1 N				1 N				2 N				1 N	1 N
ResearchSubject	1		3 N
RiskAssessment	1		1	1 N		1 N	1	1 N			1 N				1 N					1 N
Schedule	1		1 N	3 N			1 N			1 N
SearchParameter	1 N	1	1	1 N								1 N					1 N			1 N
ServiceRequest	1		1	2 N	1 N	1 N	1	1 N		1 N		1 N	1 N		3 N					1 N
Slot	1			4 N						2 N
Specimen	2 N		1			1 N	1		2 N		1 N				1 N					1 N
StructureDefinition	2 N	1	1	1 N								1 N					1 N			1 N
StructureMap	2 N	1	1	1 N								1 N					1 N			1 N
Subscription	1		1			1 N	1 N				1 N									1 N
Substance	1		1	1 N		1 N
SupplyDelivery											1 N
SupplyRequest	1		1	1 N	1 N	3 NC				1 N		1 N	1 N		1 N					1 N
Task	1		1	1 N	1 N	2 N	1 N	1 N			1 N	1 N	1 N		2 N				1 N	2 N
TerminologyCapabilities	1 N	1	1	1 N								1 N					1 N			1 N
TestReport	1		1									1 N
TestScript	2 N	1	1	1 N								1 N					1 N			1 N
Topic	2 N	1	1	1 N								1 N	1 N							1 N
ValueSet	2 N	1	1	1 N					1 N			1 N					1 N			1 N
VerificationResult																		1
VisionPrescription	1		1				1 N	1 N				1 N	1 N