Generated Narrative: StructureDefinition LaboratoryReport Name Flags Card. Type Description & Constraints<img src="[binary]" alt="doco" style="background-color: inherit"/> LaboratoryReport 0..* Element Elements defined in Ancestors:@id, <a href="http://hl7.org/fhir/R4/datatypes.html#Element" title="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.">extension Laborbericht basierend auf der SR 818.101.126 Verordnung des EDI über die Meldung von Beobachtungen übertragbarer Krankheiten des Menschen (https://www.fedlex.admin.ch/eli/cc/2015/892/de) Header 1..1 Element Document information DocumentIdentifier 1..1 Identifier Persistent, unique identifier for the document DocumentTimestamp 1..1 dateTime Timestamp of the document DocumentLanguage 1..1 code Language of the document content DocumentTitle 1..1 string Human Readable name/title of the document DocumentSectionTitle 1..1 string Human Readable name/title of the section Author 1..1 Element Author of the document (may be identical with Lab) OrganizationGLN 1..1 Identifier Global location number (GLN) of the authoring/sending organization Art. 4 Abs. 2 (Meldepflichtiges Laboratorium)">Lab 1..1 Element Notifiable laboratory that performed the laboratory test -> Art. 4 Abs. 2 (Meldepflichtiges Laboratorium) OrganizationGLN 1..1 Identifier Global location number (GLN) of the laboratory organization OrganizationName 1..1 string Name of the laboratory organization OrderIdentifier 1..1 Identifier Identifier assigned to this order by the testing laboratory Art. 4 Abs. 3 (Auftraggebende Ärztin oder auftraggebender Arzt und Betrieb in dem sie oder er tätig ist)">Orderer 1..1 Element Orderer of the laboratory test -> Art. 4 Abs. 3 (Auftraggebende Ärztin oder auftraggebender Arzt und Betrieb in dem sie oder er tätig ist) OrganizationBER 0..1 Identifier Business and Enterprise Register (BER) of the ordering organization OrganizationUIDB 0..1 Identifier Unique Identification Business (UIDB) of the ordering organization OrganizationName 1..1 string Name of the ordering organization OrganizationDepartment 1..1 string Department where the laboratory test is ordered Physician 1..1 Element Ordering physician GLN 1..1 Identifier Global location number (GLN) of the physician ZSR 0..1 Identifier Unique Identification (ZSR/RCC) of the ordering physician Surname 1..1 string Surname physician Givenname 1..1 string Given name physician Phone 1..1 string Phone number physician Email 1..1 string Email address physician OrganizationAddress 1..1 Element Address of the ordering organization StreetLine 1..1 string Street name, house number PostBox 1..1 string P.O. Box number ZipCode 1..1 string Zip code City 1..1 string City Anhang 3 (Angaben zur betrofenen Person)">Patient 1..1 Element Patient -> Anhang 3 (Angaben zur betrofenen Person) Identifier 1..1 Identifier Identifier OASI 0..1 Identifier Switzerland: Old-age and survivors's insurance (OASI) number IDN 0..1 Identifier Liechtenstein: Identification number (IDN) Surname 1..1 string Surname (or initials) Givenname 1..1 string Given name (or initials) Gender 1..1 code Gender DateOfBirth 1..1 date Date of birth Phone 1..1 string Phone number Address 1..1 Element Residence address StreetLine 1..1 string Street name, house number ZipCode 1..1 string Zip code City 1..1 string City Canton 1..1 code Canton Country 1..1 code Country Art. 4 Abs. 1 (Die zu meldenden laboranalytischen Befunde) - Anhang 3 (Angaben zum laboranalytischen Befund)">TestResult 1..1 Element Laboratory result -> Art. 4 Abs. 1 (Die zu meldenden laboranalytischen Befunde) - Anhang 3 (Angaben zum laboranalytischen Befund) StudyType 1..1 code Laboratory study type ExecutionDateTime 1..1 dateTime Date (-time) of test Type 1..1 Element Type of test Code 1..1 code Coded data CodeSystem 1..1 uri Identity fo the terminology system Specimen 1..1 Element Test sample CollectionDateTime 1..1 dateTime Date (-time) of sample collection Type 1..1 code Collection material Code 0..1 code Coded data CodeSystem 0..1 uri Identity fo the terminology system Value 1..1 Element Acutal test result Code 1..1 code Coded data CodeSystem 1..1 uri Identity fo the terminology system Interpretation 1..1 Element Interpretation of the test result Code 1..1 code Coded data CodeSystem 1..1 uri Identity fo the terminology system (HL7 ObservationInterpretation) <img src="[binary]" alt="doco" style="background-color: inherit"/> Documentation for this format
The logical model represents the CH ELM laboratory report as an abstract data model. This data elements are defined by the ordinance of the Federal Office of Public Health (FOPH) and are then mapped to the FHIR document structure. Cardinalities: - The cardinalities in the logical model show the so-called 'best case'. This means that if these data are available, they must be submitted to the FOPH. - Since in reality the data is not always available, the CH ELM profiles define which elements are required or optional. - See also the concept 'Must Support', which is described on the 'Home' page of this implementation guide
Laborbericht basierend auf der SR 818.101.126 Verordnung des EDI über die Meldung von Beobachtungen übertragbarer Krankheiten des Menschen (https://www.fedlex.admin.ch/eli/cc/2015/892/de)
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
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.
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Persistent, unique identifier for the document
Human Readable name/title of the document
Human Readable name/title of the section
Author of the document (may be identical with Lab)
Global location number (GLN) of the authoring/sending organization
Notifiable laboratory that performed the laboratory test -> Art. 4 Abs. 2 (Meldepflichtiges Laboratorium)
Global location number (GLN) of the laboratory organization
Identifier assigned to this order by the testing laboratory
Orderer of the laboratory test -> Art. 4 Abs. 3 (Auftraggebende Ärztin oder auftraggebender Arzt und Betrieb in dem sie oder er tätig ist)
Business and Enterprise Register (BER) of the ordering organization
Unique Identification Business (UIDB) of the ordering organization
Department where the laboratory test is ordered
Global location number (GLN) of the physician
Unique Identification (ZSR/RCC) of the ordering physician
Patient -> Anhang 3 (Angaben zur betrofenen Person)
usual | official | temp | secondary | old (If known)
Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.
Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.
This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one.
Identifies the purpose for this identifier, if known .
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
Allows users to make use of identifiers when the identifier system is not known.
A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
Identifier.system is always case sensitive.
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
Time period when id is/was valid for use
Time period during which identifier is/was valid for use.
Role.effectiveTime or implied by context
Organization that issued id (may be just text)
Organization that issued/manages the identifier.
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
Switzerland: Old-age and survivors's insurance (OASI) number
Liechtenstein: Identification number (IDN)
Laboratory result -> Art. 4 Abs. 1 (Die zu meldenden laboranalytischen Befunde) - Anhang 3 (Angaben zum laboranalytischen Befund)
unique id for the element within a resource (for internal references)
May be used to represent additional information that is not part of the basic definition of the resource. 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.
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
Identity fo the terminology system (HL7 ObservationInterpretation)