ONCOnnectTumorboardIG - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

• Content
• Detailed Descriptions
• Mappings
• Examples
• XML
• JSON
• TTL

Resource Profile: Patient History (Profile)

Captures the patient's history, including conditions and events that are relevant to their health status.

Usages:

• Refer to this Profile: Registration (Profile)
• Examples for this Profile: List/ONCOnnect-EX-TB-OncologicalHistory

You can also check for usages in the FHIR IG Statistics

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

• Key Elements Table
• Differential Table
• Snapshot Table
• Statistics/References
• All

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
List	C	0..*	List	A list is a curated collection of resources Constraints: lst-1, lst-2, lst-3
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
status	?!Σ	1..1	code	current | retired | entered-in-error Binding: ListStatus (required): The current state of the list. Required Pattern: current
mode	?!Σ	1..1	code	working | snapshot | changes Binding: ListMode (required): The processing mode that applies to this list. Required Pattern: snapshot
code	Σ	1..1	CodeableConcept	What the purpose of this list is Binding: ExampleUseCodesForList (example): What the purpose of a list is. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (Complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://loinc.org
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: 35090-0
display		1..1	string	Representation defined by the system Fixed Value: Patient history
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
subject	Σ	1..1	Reference(Patient (Profile))	If all resources have the same subject
entry	C	0..*	BackboneElement	A list of all relevant patient history items, such as previous surgeries, treatments, or previous tumor boards. Examplary events are listed below: | Event | Profile | |----------------------|---------------------------------------| | CT-Staging + Staging | ONCOnnect PR TB TNMStaging | | Operation | MII PR Onkologie Operation | | Tumorkonferenz | MII PR Onkologie Tumorkonferenz | | Radiotherapie | MII PR Onkologie Strahlentherapie | | Chemotherapie | MII PR Medikation MedicationStatement | | Erstdiagnose | Condition? | | Leitlinientherapie | CarePlan/Observation? | | (Sonstiges) | Observation / .. | In case it is not possible or requires significant effort to track the patient history in a structured way, you should still use one base resource per event, but only use the note property to capture the information. This is why this profile only defines the Reference type to link to FHIR base resources and not the specific MII profiles. E.g. the MII Onkologie Operation profile would require a structured OPS code. Please include a date (YYYY-MM-DD, YYYY-MM or YYYY) in the note to indicate when the event occurred.
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
deleted	?!C	0..1	boolean	If this item is actually marked as deleted
item		1..1	Reference(MedicationStatement | Procedure | Observation | CarePlan | Condition)	Actual entry
emptyReason	C	0..1	CodeableConcept	Why list is empty Binding: ListEmptyReasons (required)
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code	URI
List.status	required	Pattern Value: current http://hl7.org/fhir/ValueSet/list-status|4.0.1 From the FHIR Standard
List.mode	required	Pattern Value: snapshot http://hl7.org/fhir/ValueSet/list-mode|4.0.1 From the FHIR Standard
List.code	example	Pattern Value: LOINC Code 35090-0("Patient history") http://hl7.org/fhir/ValueSet/list-example-codes From the FHIR Standard
List.emptyReason	required	ListEmptyReasons http://hl7.org/fhir/ValueSet/list-empty-reason|4.0.1 From the FHIR Standard

Constraints

Id	Grade	Path(s)	Details	Requirements
dom-2	error	List	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-3	error	List	If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource : contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4	error	List	If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated : contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5	error	List	If a resource is contained in another resource, it SHALL NOT have a security label : contained.meta.security.empty()
dom-6	best practice	List	A resource should have narrative for robust management : text.`div`.exists()
ele-1	error	**ALL** elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	**ALL** extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()
lst-1	error	List	A list can only have an emptyReason if it is empty : emptyReason.empty() or entry.empty()
lst-2	error	List	The deleted flag can only be used if the mode of the list is "changes" : mode = 'changes' or entry.deleted.empty()
lst-3	error	List	An entry date can only be used if the mode of the list is "working" : mode = 'working' or entry.date.empty()

This structure is derived from List

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
List		0..*	List	A list is a curated collection of resources
status		1..1	code	current | retired | entered-in-error Required Pattern: current
mode		1..1	code	working | snapshot | changes Required Pattern: snapshot
code		1..1	CodeableConcept	What the purpose of this list is Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (Complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://loinc.org
code		1..1	code	Symbol in syntax defined by the system Fixed Value: 35090-0
display		1..1	string	Representation defined by the system Fixed Value: Patient history
subject		1..1	Reference(Patient (Profile))	If all resources have the same subject
entry		0..*	BackboneElement	A list of all relevant patient history items, such as previous surgeries, treatments, or previous tumor boards. Examplary events are listed below: | Event | Profile | |----------------------|---------------------------------------| | CT-Staging + Staging | ONCOnnect PR TB TNMStaging | | Operation | MII PR Onkologie Operation | | Tumorkonferenz | MII PR Onkologie Tumorkonferenz | | Radiotherapie | MII PR Onkologie Strahlentherapie | | Chemotherapie | MII PR Medikation MedicationStatement | | Erstdiagnose | Condition? | | Leitlinientherapie | CarePlan/Observation? | | (Sonstiges) | Observation / .. | In case it is not possible or requires significant effort to track the patient history in a structured way, you should still use one base resource per event, but only use the note property to capture the information. This is why this profile only defines the Reference type to link to FHIR base resources and not the specific MII profiles. E.g. the MII Onkologie Operation profile would require a structured OPS code. Please include a date (YYYY-MM-DD, YYYY-MM or YYYY) in the note to indicate when the event occurred.
item		1..1	Reference(MedicationStatement | Procedure | Observation | CarePlan | Condition)	Actual entry
emptyReason		0..1	CodeableConcept	Why list is empty Binding: ListEmptyReasons (required)
Documentation for this format

Terminology Bindings (Differential)

Path	Conformance	ValueSet	URI
List.emptyReason	required	ListEmptyReasons http://hl7.org/fhir/ValueSet/list-empty-reason|4.0.1 From the FHIR Standard

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
List	C	0..*	List	A list is a curated collection of resources Constraints: lst-1, lst-2, lst-3
id	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: CommonLanguages (preferred): A human language. Additional Bindings Purpose AllLanguages Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements
contained		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier		0..*	Identifier	Business identifier
status	?!Σ	1..1	code	current | retired | entered-in-error Binding: ListStatus (required): The current state of the list. Required Pattern: current
mode	?!Σ	1..1	code	working | snapshot | changes Binding: ListMode (required): The processing mode that applies to this list. Required Pattern: snapshot
title	Σ	0..1	string	Descriptive name for the list Example General: Dr. Jane's Patients
code	Σ	1..1	CodeableConcept	What the purpose of this list is Binding: ExampleUseCodesForList (example): What the purpose of a list is. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (Complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://loinc.org
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: 35090-0
display		1..1	string	Representation defined by the system Fixed Value: Patient history
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
subject	Σ	1..1	Reference(Patient (Profile))	If all resources have the same subject
encounter		0..1	Reference(Encounter)	Context in which list created
date	Σ	0..1	dateTime	When the list was prepared
source	Σ	0..1	Reference(Practitioner | PractitionerRole | Patient | Device)	Who and/or what defined the list contents (aka Author)
orderedBy		0..1	CodeableConcept	What order the list has Binding: ListOrderCodes (preferred): What order applies to the items in a list.
note		0..*	Annotation	Comments about the list
entry	C	0..*	BackboneElement	A list of all relevant patient history items, such as previous surgeries, treatments, or previous tumor boards. Examplary events are listed below: | Event | Profile | |----------------------|---------------------------------------| | CT-Staging + Staging | ONCOnnect PR TB TNMStaging | | Operation | MII PR Onkologie Operation | | Tumorkonferenz | MII PR Onkologie Tumorkonferenz | | Radiotherapie | MII PR Onkologie Strahlentherapie | | Chemotherapie | MII PR Medikation MedicationStatement | | Erstdiagnose | Condition? | | Leitlinientherapie | CarePlan/Observation? | | (Sonstiges) | Observation / .. | In case it is not possible or requires significant effort to track the patient history in a structured way, you should still use one base resource per event, but only use the note property to capture the information. This is why this profile only defines the Reference type to link to FHIR base resources and not the specific MII profiles. E.g. the MII Onkologie Operation profile would require a structured OPS code. Please include a date (YYYY-MM-DD, YYYY-MM or YYYY) in the note to indicate when the event occurred.
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
flag		0..1	CodeableConcept	Status/Workflow information about this item Binding: PatientMedicineChangeTypes (example): Codes that provide further information about the reason and meaning of the item in the list.
deleted	?!C	0..1	boolean	If this item is actually marked as deleted
date		0..1	dateTime	When item added to list
item		1..1	Reference(MedicationStatement | Procedure | Observation | CarePlan | Condition)	Actual entry
emptyReason	C	0..1	CodeableConcept	Why list is empty Binding: ListEmptyReasons (required)
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code	URI
List.language	preferred	CommonLanguages http://hl7.org/fhir/ValueSet/languages From the FHIR Standard Additional Bindings Purpose AllLanguages Max Binding
List.status	required	Pattern Value: current http://hl7.org/fhir/ValueSet/list-status|4.0.1 From the FHIR Standard
List.mode	required	Pattern Value: snapshot http://hl7.org/fhir/ValueSet/list-mode|4.0.1 From the FHIR Standard
List.code	example	Pattern Value: LOINC Code 35090-0("Patient history") http://hl7.org/fhir/ValueSet/list-example-codes From the FHIR Standard
List.orderedBy	preferred	ListOrderCodes http://hl7.org/fhir/ValueSet/list-order From the FHIR Standard
List.entry.flag	example	PatientMedicineChangeTypes http://hl7.org/fhir/ValueSet/list-item-flag From the FHIR Standard
List.emptyReason	required	ListEmptyReasons http://hl7.org/fhir/ValueSet/list-empty-reason|4.0.1 From the FHIR Standard

Constraints

Id	Grade	Path(s)	Details	Requirements
dom-2	error	List	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-3	error	List	If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource : contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4	error	List	If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated : contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5	error	List	If a resource is contained in another resource, it SHALL NOT have a security label : contained.meta.security.empty()
dom-6	best practice	List	A resource should have narrative for robust management : text.`div`.exists()
ele-1	error	**ALL** elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	**ALL** extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()
lst-1	error	List	A list can only have an emptyReason if it is empty : emptyReason.empty() or entry.empty()
lst-2	error	List	The deleted flag can only be used if the mode of the list is "changes" : mode = 'changes' or entry.deleted.empty()
lst-3	error	List	An entry date can only be used if the mode of the list is "working" : mode = 'working' or entry.date.empty()

This structure is derived from List

Summary

Mandatory: 2 elements

Structures

This structure refers to these other structures:

• Patient (Profile) (https://fhir.ccc-onconnect.de/StructureDefinition/onconnect-pr-tb-patient)

Key Elements View

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
List	C	0..*	List	A list is a curated collection of resources Constraints: lst-1, lst-2, lst-3
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
status	?!Σ	1..1	code	current | retired | entered-in-error Binding: ListStatus (required): The current state of the list. Required Pattern: current
mode	?!Σ	1..1	code	working | snapshot | changes Binding: ListMode (required): The processing mode that applies to this list. Required Pattern: snapshot
code	Σ	1..1	CodeableConcept	What the purpose of this list is Binding: ExampleUseCodesForList (example): What the purpose of a list is. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (Complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://loinc.org
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: 35090-0
display		1..1	string	Representation defined by the system Fixed Value: Patient history
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
subject	Σ	1..1	Reference(Patient (Profile))	If all resources have the same subject
entry	C	0..*	BackboneElement	A list of all relevant patient history items, such as previous surgeries, treatments, or previous tumor boards. Examplary events are listed below: | Event | Profile | |----------------------|---------------------------------------| | CT-Staging + Staging | ONCOnnect PR TB TNMStaging | | Operation | MII PR Onkologie Operation | | Tumorkonferenz | MII PR Onkologie Tumorkonferenz | | Radiotherapie | MII PR Onkologie Strahlentherapie | | Chemotherapie | MII PR Medikation MedicationStatement | | Erstdiagnose | Condition? | | Leitlinientherapie | CarePlan/Observation? | | (Sonstiges) | Observation / .. | In case it is not possible or requires significant effort to track the patient history in a structured way, you should still use one base resource per event, but only use the note property to capture the information. This is why this profile only defines the Reference type to link to FHIR base resources and not the specific MII profiles. E.g. the MII Onkologie Operation profile would require a structured OPS code. Please include a date (YYYY-MM-DD, YYYY-MM or YYYY) in the note to indicate when the event occurred.
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
deleted	?!C	0..1	boolean	If this item is actually marked as deleted
item		1..1	Reference(MedicationStatement | Procedure | Observation | CarePlan | Condition)	Actual entry
emptyReason	C	0..1	CodeableConcept	Why list is empty Binding: ListEmptyReasons (required)
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code	URI
List.status	required	Pattern Value: current http://hl7.org/fhir/ValueSet/list-status|4.0.1 From the FHIR Standard
List.mode	required	Pattern Value: snapshot http://hl7.org/fhir/ValueSet/list-mode|4.0.1 From the FHIR Standard
List.code	example	Pattern Value: LOINC Code 35090-0("Patient history") http://hl7.org/fhir/ValueSet/list-example-codes From the FHIR Standard
List.emptyReason	required	ListEmptyReasons http://hl7.org/fhir/ValueSet/list-empty-reason|4.0.1 From the FHIR Standard

Constraints

Id	Grade	Path(s)	Details	Requirements
dom-2	error	List	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-3	error	List	If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource : contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4	error	List	If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated : contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5	error	List	If a resource is contained in another resource, it SHALL NOT have a security label : contained.meta.security.empty()
dom-6	best practice	List	A resource should have narrative for robust management : text.`div`.exists()
ele-1	error	**ALL** elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	**ALL** extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()
lst-1	error	List	A list can only have an emptyReason if it is empty : emptyReason.empty() or entry.empty()
lst-2	error	List	The deleted flag can only be used if the mode of the list is "changes" : mode = 'changes' or entry.deleted.empty()
lst-3	error	List	An entry date can only be used if the mode of the list is "working" : mode = 'working' or entry.date.empty()

Differential View

This structure is derived from List

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
List		0..*	List	A list is a curated collection of resources
status		1..1	code	current | retired | entered-in-error Required Pattern: current
mode		1..1	code	working | snapshot | changes Required Pattern: snapshot
code		1..1	CodeableConcept	What the purpose of this list is Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (Complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://loinc.org
code		1..1	code	Symbol in syntax defined by the system Fixed Value: 35090-0
display		1..1	string	Representation defined by the system Fixed Value: Patient history
subject		1..1	Reference(Patient (Profile))	If all resources have the same subject
entry		0..*	BackboneElement	A list of all relevant patient history items, such as previous surgeries, treatments, or previous tumor boards. Examplary events are listed below: | Event | Profile | |----------------------|---------------------------------------| | CT-Staging + Staging | ONCOnnect PR TB TNMStaging | | Operation | MII PR Onkologie Operation | | Tumorkonferenz | MII PR Onkologie Tumorkonferenz | | Radiotherapie | MII PR Onkologie Strahlentherapie | | Chemotherapie | MII PR Medikation MedicationStatement | | Erstdiagnose | Condition? | | Leitlinientherapie | CarePlan/Observation? | | (Sonstiges) | Observation / .. | In case it is not possible or requires significant effort to track the patient history in a structured way, you should still use one base resource per event, but only use the note property to capture the information. This is why this profile only defines the Reference type to link to FHIR base resources and not the specific MII profiles. E.g. the MII Onkologie Operation profile would require a structured OPS code. Please include a date (YYYY-MM-DD, YYYY-MM or YYYY) in the note to indicate when the event occurred.
item		1..1	Reference(MedicationStatement | Procedure | Observation | CarePlan | Condition)	Actual entry
emptyReason		0..1	CodeableConcept	Why list is empty Binding: ListEmptyReasons (required)
Documentation for this format

Terminology Bindings (Differential)

Path	Conformance	ValueSet	URI
List.emptyReason	required	ListEmptyReasons http://hl7.org/fhir/ValueSet/list-empty-reason|4.0.1 From the FHIR Standard

Snapshot View

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
List	C	0..*	List	A list is a curated collection of resources Constraints: lst-1, lst-2, lst-3
id	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: CommonLanguages (preferred): A human language. Additional Bindings Purpose AllLanguages Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements
contained		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier		0..*	Identifier	Business identifier
status	?!Σ	1..1	code	current | retired | entered-in-error Binding: ListStatus (required): The current state of the list. Required Pattern: current
mode	?!Σ	1..1	code	working | snapshot | changes Binding: ListMode (required): The processing mode that applies to this list. Required Pattern: snapshot
title	Σ	0..1	string	Descriptive name for the list Example General: Dr. Jane's Patients
code	Σ	1..1	CodeableConcept	What the purpose of this list is Binding: ExampleUseCodesForList (example): What the purpose of a list is. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (Complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://loinc.org
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: 35090-0
display		1..1	string	Representation defined by the system Fixed Value: Patient history
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
subject	Σ	1..1	Reference(Patient (Profile))	If all resources have the same subject
encounter		0..1	Reference(Encounter)	Context in which list created
date	Σ	0..1	dateTime	When the list was prepared
source	Σ	0..1	Reference(Practitioner | PractitionerRole | Patient | Device)	Who and/or what defined the list contents (aka Author)
orderedBy		0..1	CodeableConcept	What order the list has Binding: ListOrderCodes (preferred): What order applies to the items in a list.
note		0..*	Annotation	Comments about the list
entry	C	0..*	BackboneElement	A list of all relevant patient history items, such as previous surgeries, treatments, or previous tumor boards. Examplary events are listed below: | Event | Profile | |----------------------|---------------------------------------| | CT-Staging + Staging | ONCOnnect PR TB TNMStaging | | Operation | MII PR Onkologie Operation | | Tumorkonferenz | MII PR Onkologie Tumorkonferenz | | Radiotherapie | MII PR Onkologie Strahlentherapie | | Chemotherapie | MII PR Medikation MedicationStatement | | Erstdiagnose | Condition? | | Leitlinientherapie | CarePlan/Observation? | | (Sonstiges) | Observation / .. | In case it is not possible or requires significant effort to track the patient history in a structured way, you should still use one base resource per event, but only use the note property to capture the information. This is why this profile only defines the Reference type to link to FHIR base resources and not the specific MII profiles. E.g. the MII Onkologie Operation profile would require a structured OPS code. Please include a date (YYYY-MM-DD, YYYY-MM or YYYY) in the note to indicate when the event occurred.
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
flag		0..1	CodeableConcept	Status/Workflow information about this item Binding: PatientMedicineChangeTypes (example): Codes that provide further information about the reason and meaning of the item in the list.
deleted	?!C	0..1	boolean	If this item is actually marked as deleted
date		0..1	dateTime	When item added to list
item		1..1	Reference(MedicationStatement | Procedure | Observation | CarePlan | Condition)	Actual entry
emptyReason	C	0..1	CodeableConcept	Why list is empty Binding: ListEmptyReasons (required)
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code	URI
List.language	preferred	CommonLanguages http://hl7.org/fhir/ValueSet/languages From the FHIR Standard Additional Bindings Purpose AllLanguages Max Binding
List.status	required	Pattern Value: current http://hl7.org/fhir/ValueSet/list-status|4.0.1 From the FHIR Standard
List.mode	required	Pattern Value: snapshot http://hl7.org/fhir/ValueSet/list-mode|4.0.1 From the FHIR Standard
List.code	example	Pattern Value: LOINC Code 35090-0("Patient history") http://hl7.org/fhir/ValueSet/list-example-codes From the FHIR Standard
List.orderedBy	preferred	ListOrderCodes http://hl7.org/fhir/ValueSet/list-order From the FHIR Standard
List.entry.flag	example	PatientMedicineChangeTypes http://hl7.org/fhir/ValueSet/list-item-flag From the FHIR Standard
List.emptyReason	required	ListEmptyReasons http://hl7.org/fhir/ValueSet/list-empty-reason|4.0.1 From the FHIR Standard

Constraints

Id	Grade	Path(s)	Details	Requirements
dom-2	error	List	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-3	error	List	If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource : contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4	error	List	If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated : contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5	error	List	If a resource is contained in another resource, it SHALL NOT have a security label : contained.meta.security.empty()
dom-6	best practice	List	A resource should have narrative for robust management : text.`div`.exists()
ele-1	error	**ALL** elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	**ALL** extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()
lst-1	error	List	A list can only have an emptyReason if it is empty : emptyReason.empty() or entry.empty()
lst-2	error	List	The deleted flag can only be used if the mode of the list is "changes" : mode = 'changes' or entry.deleted.empty()
lst-3	error	List	An entry date can only be used if the mode of the list is "working" : mode = 'working' or entry.date.empty()

This structure is derived from List

Summary

Mandatory: 2 elements

Structures

This structure refers to these other structures:

• Patient (Profile) (https://fhir.ccc-onconnect.de/StructureDefinition/onconnect-pr-tb-patient)

Other representations of profile: CSV, Excel, Schematron