MyHealth@Eu Laboratory Report
0.0.1 - qa-preview
150
MyHealth@Eu Laboratory Report - Local Development build (v0.0.1) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Draft as of 2024-11-21 |
Definitions for the Recipient logical model.
Guidance on how to interpret the contents of this table can be found here
0. Recipient | |||||
Definition | Information recipient (intended recipient or recipients of the report, additional recipients might be identified by the ordering party, e.g. GP, other specialist), if applicable. Section A1.4 of the MyHealth@EUguideline. | ||||
Short | A.1.4 - Information recipient | ||||
Logical Model | Instances of this logical model are not marked to be the target of a Reference | ||||
2. Recipient.identifier | |||||
Definition | The health professional identification number. Either an internal identifier assigned by a healthcare provider institution or (preferably) a national health professional ID such as the license or registration number. In case when recipient is not a health professional, e.g. patient, appropriate personal identifier should be used. | ||||
Short | Recipient identifier | ||||
Note | This is a business identifier, not a resource identifier (see discussion) | ||||
Control | 0..* | ||||
Type | Identifier | ||||
Obligations |
| ||||
4. Recipient.name | |||||
Definition | Person name. Either Recipient name or the Organization name should be provided. | ||||
Short | Recipient name | ||||
Control | 0..* | ||||
Type | HumanName | ||||
6. Recipient.organization | |||||
Definition | The healthcare provider organization information. | ||||
Short | Recipient organization | ||||
Control | 0..* | ||||
Type | BackboneElement | ||||
8. Recipient.organization.name | |||||
Definition | Name of the organization | ||||
Short | Organization Name | ||||
Control | 0..1 | ||||
Type | string | ||||
Primitive Value | This primitive element may be present, or absent, or replaced by an extension | ||||
10. Recipient.organization.address | |||||
Definition | Address of the organization | ||||
Short | Organization Address | ||||
Control | 0..* | ||||
Type | Address | ||||
12. Recipient.organization.telecom | |||||
Definition | Telecom of the organization | ||||
Short | Organization telecom | ||||
Control | 0..* | ||||
Type | ContactPoint | ||||
14. Recipient.address | |||||
Definition | Mailing and home or office addresses. The addresses are always sequences of address parts (e.g., street address line, country, ZIP code, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose. - Preferred system(s): | ||||
Short | Address | ||||
Control | 0..* | ||||
Type | Address | ||||
16. Recipient.country | |||||
Definition | Country of the recipient. - Preferred system(s): ISO 3166 | ||||
Short | Country | ||||
Control | 0..* | ||||
Type | CodeableConcept | ||||
Obligations |
| ||||
18. Recipient.telecom | |||||
Definition | Telecommunication contact information (addresses) associated to a person. Multiple telecommunication addresses might be provided. - Preferred system(s): | ||||
Short | Telecom | ||||
Control | 0..* | ||||
Type | ContactPoint | ||||
Obligations |
|
Guidance on how to interpret the contents of this table can be found here
0. Recipient | |||||
Definition | Information recipient (intended recipient or recipients of the report, additional recipients might be identified by the ordering party, e.g. GP, other specialist), if applicable. Section A1.4 of the MyHealth@EUguideline. | ||||
Short | A.1.4 - Information recipient | ||||
Control | 0..* | ||||
Is Modifier | false | ||||
Logical Model | Instances of this logical model are not marked to be the target of a Reference | ||||
2. Recipient.identifier | |||||
Definition | The health professional identification number. Either an internal identifier assigned by a healthcare provider institution or (preferably) a national health professional ID such as the license or registration number. In case when recipient is not a health professional, e.g. patient, appropriate personal identifier should be used. | ||||
Short | Recipient identifier | ||||
Note | This is a business identifier, not a resource identifier (see discussion) | ||||
Control | 0..* | ||||
Type | Identifier | ||||
Obligations |
| ||||
4. Recipient.name | |||||
Definition | Person name. Either Recipient name or the Organization name should be provided. | ||||
Short | Recipient name | ||||
Control | 0..* | ||||
Type | HumanName | ||||
6. Recipient.organization | |||||
Definition | The healthcare provider organization information. | ||||
Short | Recipient organization | ||||
Control | 0..* | ||||
Type | BackboneElement | ||||
Invariants | ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count()) ) | ||||
8. Recipient.organization.modifierExtension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||
Short | Extensions that cannot be ignored even if unrecognized | ||||
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Is Modifier | true because Modifier extensions are expected to modify the meaning or interpretation of the element that contains them | ||||
Summary | true | ||||
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||
Alternate Names | extensions, user content, modifiers | ||||
Invariants | ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists()) | ||||
10. Recipient.organization.name | |||||
Definition | Name of the organization | ||||
Short | Organization Name | ||||
Control | 0..1 | ||||
Type | string | ||||
Primitive Value | This primitive element may be present, or absent, or replaced by an extension | ||||
12. Recipient.organization.address | |||||
Definition | Address of the organization | ||||
Short | Organization Address | ||||
Control | 0..* | ||||
Type | Address | ||||
14. Recipient.organization.telecom | |||||
Definition | Telecom of the organization | ||||
Short | Organization telecom | ||||
Control | 0..* | ||||
Type | ContactPoint | ||||
16. Recipient.address | |||||
Definition | Mailing and home or office addresses. The addresses are always sequences of address parts (e.g., street address line, country, ZIP code, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose. - Preferred system(s): | ||||
Short | Address | ||||
Control | 0..* | ||||
Type | Address | ||||
18. Recipient.country | |||||
Definition | Country of the recipient. - Preferred system(s): ISO 3166 | ||||
Short | Country | ||||
Control | 0..* | ||||
Type | CodeableConcept | ||||
Obligations |
| ||||
20. Recipient.telecom | |||||
Definition | Telecommunication contact information (addresses) associated to a person. Multiple telecommunication addresses might be provided. - Preferred system(s): | ||||
Short | Telecom | ||||
Control | 0..* | ||||
Type | ContactPoint | ||||
Obligations |
|
Guidance on how to interpret the contents of this table can be found here
0. Recipient | |||||
Definition | Information recipient (intended recipient or recipients of the report, additional recipients might be identified by the ordering party, e.g. GP, other specialist), if applicable. Section A1.4 of the MyHealth@EUguideline. | ||||
Short | A.1.4 - Information recipient | ||||
Control | 0..* | ||||
Is Modifier | false | ||||
Logical Model | Instances of this logical model are not marked to be the target of a Reference | ||||
2. Recipient.identifier | |||||
Definition | The health professional identification number. Either an internal identifier assigned by a healthcare provider institution or (preferably) a national health professional ID such as the license or registration number. In case when recipient is not a health professional, e.g. patient, appropriate personal identifier should be used. | ||||
Short | Recipient identifier | ||||
Note | This is a business identifier, not a resource identifier (see discussion) | ||||
Control | 0..* | ||||
Type | Identifier | ||||
Obligations |
| ||||
4. Recipient.name | |||||
Definition | Person name. Either Recipient name or the Organization name should be provided. | ||||
Short | Recipient name | ||||
Control | 0..* | ||||
Type | HumanName | ||||
6. Recipient.organization | |||||
Definition | The healthcare provider organization information. | ||||
Short | Recipient organization | ||||
Control | 0..* | ||||
Type | BackboneElement | ||||
Invariants | ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count()) ) | ||||
8. Recipient.organization.id | |||||
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||
Short | Unique id for inter-element referencing | ||||
Control | 0..1 | ||||
Type | string | ||||
Is Modifier | false | ||||
XML Format | In the XML format, this property is represented as an attribute. | ||||
Summary | false | ||||
10. Recipient.organization.extension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||
Short | Additional content defined by implementations | ||||
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Is Modifier | false | ||||
Summary | false | ||||
Alternate Names | extensions, user content | ||||
Invariants | ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count()) )ext-1: Must have either extensions or value[x], not both ( extension.exists() != value.exists() ) | ||||
Slicing | This element introduces a set of slices on Recipient.organization.extension . The slices areUnordered and Open, and can be differentiated using the following discriminators: | ||||
12. Recipient.organization.modifierExtension | |||||
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||
Short | Extensions that cannot be ignored even if unrecognized | ||||
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||
Control | 0..* | ||||
Type | Extension | ||||
Is Modifier | true because Modifier extensions are expected to modify the meaning or interpretation of the element that contains them | ||||
Summary | true | ||||
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||
Alternate Names | extensions, user content, modifiers | ||||
Invariants | ele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count()) )ext-1: Must have either extensions or value[x], not both ( extension.exists() != value.exists() ) | ||||
14. Recipient.organization.name | |||||
Definition | Name of the organization | ||||
Short | Organization Name | ||||
Control | 0..1 | ||||
Type | string | ||||
Primitive Value | This primitive element may be present, or absent, or replaced by an extension | ||||
16. Recipient.organization.address | |||||
Definition | Address of the organization | ||||
Short | Organization Address | ||||
Control | 0..* | ||||
Type | Address | ||||
18. Recipient.organization.telecom | |||||
Definition | Telecom of the organization | ||||
Short | Organization telecom | ||||
Control | 0..* | ||||
Type | ContactPoint | ||||
20. Recipient.address | |||||
Definition | Mailing and home or office addresses. The addresses are always sequences of address parts (e.g., street address line, country, ZIP code, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose. - Preferred system(s): | ||||
Short | Address | ||||
Control | 0..* | ||||
Type | Address | ||||
22. Recipient.country | |||||
Definition | Country of the recipient. - Preferred system(s): ISO 3166 | ||||
Short | Country | ||||
Control | 0..* | ||||
Type | CodeableConcept | ||||
Obligations |
| ||||
24. Recipient.telecom | |||||
Definition | Telecommunication contact information (addresses) associated to a person. Multiple telecommunication addresses might be provided. - Preferred system(s): | ||||
Short | Telecom | ||||
Control | 0..* | ||||
Type | ContactPoint | ||||
Obligations |
|