Naam |
Details [‑] |
|
Patient
vl-dataelement101-7360
|
|
|
Id |
vl-dataelement101-7360 (2020‑02‑02 22:40:38)
|
Concept erft van |
NL-CM-0.1.1 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de bouwsteen Patiënt. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Patiënt.
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Naamgegevens
vl-dataelement101-8062
|
|
|
Id |
vl-dataelement101-8062 (2020‑02‑04 00:22:37)
|
Concept erft van |
NL-CM-0.1.6 (2017‑12‑31)
|
Omschrijving |
De naamgegevens van de patiënt.
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Naamgegevens
vl-dataelement101-8063
|
|
|
Id |
vl-dataelement101-8063 (2020‑02‑04 00:22:37)
|
Concept erft van |
NL-CM-2017-152 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de subbouwsteen Naamgegevens. Dit rootconcept bevat alle gegevenselementen
van de subbouwsteen Naamgegevens.
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Adresgegevens
vl-dataelement101-8064
|
|
|
|
|
Adresgegevens
vl-dataelement101-8065
|
|
|
Id |
vl-dataelement101-8065 (2020‑02‑04 00:22:37)
|
Concept erft van |
NL-CM-2017-153 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de subbouwsteen Adresgegevens. Dit rootconcept bevat alle gegevenselementen
van de subbouwsteen Adresgegevens.
|
|
|
Contactgegevens
vl-dataelement101-8066
|
|
|
|
|
Contactgegevens
vl-dataelement101-8067
|
|
|
Id |
vl-dataelement101-8067 (2020‑02‑04 00:22:37)
|
Concept erft van |
NL-CM-2017-154 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de sub-bouwsteen Contactgegevens. Dit rootconcept bevat alle gegevenselementen
van de sub-bouwsteen Contactgegevens.
|
|
|
Identificatienummer
vl-dataelement101-8068
|
|
|
Id |
vl-dataelement101-8068 (2020‑02‑04 00:22:37)
|
Concept erft van |
NL-CM-0.1.7 (2017‑12‑31)
|
Omschrijving |
Identificatienummer van de patiënt. Bij overdrachtsituaties dient het gebruik van
het burgerservicenummer (BSN) in overeenstemming te zijn met de 'Wet gebruik burgerservicenummer
in de zorg (Wbsn-z)'. In andere situaties kunnen andere nummersystemen gebruikt worden,
zoals bijv. interne ziekenhuis patiëntnummers.
|
Operationalisatie |
Burgerservicenummer (OID: 2.16.840.1.113883.2.4.6.3) |
Waardendomein |
Identificatie |
Voorbeeld |
111222333 |
|
|
Geboortedatum
vl-dataelement101-8069
|
|
|
Id |
vl-dataelement101-8069 (2020‑02‑04 00:22:37)
|
Concept erft van |
NL-CM-0.1.10 (2017‑12‑31)
|
Omschrijving |
Geboortedatum van de patiënt. Bij een patiënt is de geboortedatum verplicht. Vage
datum (bv. alleen jaar) is toegestaan.
|
Terminologiekoppeling |
Dit concept wordt uitgedrukt door code "21112-8" (Birth date) uit codesysteem 2.16.840.1.113883.6.1
LOINC)
|
Waardendomein |
Datum/tijd |
Voorbeeld |
22-03-1999 |
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Geslacht
vl-dataelement101-8070
|
|
|
Id |
vl-dataelement101-8070 (2020‑02‑04 00:22:37)
|
Concept erft van |
NL-CM-0.1.9 (2017‑12‑31)
|
Omschrijving |
Administratief geslacht van de patiënt. |
Terminologiekoppeling |
Dit concept wordt uitgedrukt door code "46098-0" (Sex) uit codesysteem 2.16.840.1.113883.6.1
LOINC)
|
Waardendomein |
Code |
Keuzelijst |
|
Voorbeeld |
Female |
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
MeerlingIndicator
vl-dataelement101-8071
|
|
|
Id |
vl-dataelement101-8071 (2020‑02‑04 00:22:37)
|
Concept erft van |
NL-CM-0.1.31 (2017‑12‑31)
|
Omschrijving |
Indicator die aangeeft of de patiënt één van een meerling is. |
Waardendomein |
Boolean |
Voorbeeld |
Nee |
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
OverlijdensIndicator
vl-dataelement101-8072
|
|
|
Id |
vl-dataelement101-8072 (2020‑02‑04 00:22:37)
|
Concept erft van |
NL-CM-0.1.32 (2017‑12‑31)
|
Omschrijving |
Indicator die aangeeft of de patiënt overleden is. |
Terminologiekoppeling |
Dit concept wordt uitgedrukt door code "397709008" (Patient died (finding)) uit codesysteem 2.16.840.1.113883.6.96
SNOMED CT)
|
Waardendomein |
Boolean |
Voorbeeld |
Nee |
|
|
DatumOverlijden
vl-dataelement101-8073
|
|
|
Id |
vl-dataelement101-8073 (2020‑02‑04 00:22:37)
|
Concept erft van |
NL-CM-0.1.33 (2017‑12‑31)
|
Omschrijving |
De datum waarop de patiënt overleden is. Een vage datum, b.v. alleen jaartal is toegestaan. |
Terminologiekoppeling |
Dit concept wordt uitgedrukt door code "81954-0" (Date of death [Date]) uit codesysteem 2.16.840.1.113883.6.1
LOINC)
|
Waardendomein |
Datum/tijd |
|
|
Questionnaire
vl-dataelement101-5296
|
|
|
Id |
vl-dataelement101-5296 (2019‑03‑29)
|
Omschrijving |
A structured set of questions
Sets minimum expectations for questionnaire support for the Netherlands SDC-conformant
systems, including a number of extensions around display and behavior.
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
url
vl-dataelement101-5335
|
|
|
Id |
vl-dataelement101-5335 (2019‑03‑29)
|
Omschrijving |
Logical URI to reference this questionnaire (globally unique)
An absolute URI that is used to identify this questionnaire when it is referenced
in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally
unique, and SHOULD be an address at which this questionnaire is (or will be) published.
The URL SHOULD include the major version of the questionnaire. For more information
see [Technical and Business Versions](resource.html#versions).
|
|
Rationale |
… This is the id that will be used to link a QuestionnaireResponse to the Questionnaire
the response is for.
|
Opmerking |
Can be a urn:uuid: or a urn:oid:, but real http: addresses are preferred. Multiple
instances may share the same url if they have a distinct version.
|
Waardendomein |
String |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
identifier
vl-dataelement101-5336
|
|
|
Id |
vl-dataelement101-5336 (2019‑03‑29)
|
Omschrijving |
Additional identifier for the questionnaire
A formal identifier that is used to identify this questionnaire when it is represented
in other formats, or referenced in a specification, model, design or an instance.
|
|
Rationale |
Allows externally provided and/or usable business identifiers to be easily associated
with the module.
|
Opmerking |
Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier)
data type, e.g., to identify this questionnaire outside of FHIR, where it is not possible
to use the logical URI.
|
Waardendomein |
Identificatie |
|
|
version
vl-dataelement101-5337
|
|
|
Id |
vl-dataelement101-5337 (2019‑03‑29)
|
Omschrijving |
Business version of the questionnaire
The identifier that is used to identify this version of the questionnaire when it
is referenced in a specification, model, design or instance. This is an arbitrary
value managed by the questionnaire author and is not expected to be globally unique.
For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available.
There is also no expectation that versions can be placed in a lexicographical sequence.
|
|
Opmerking |
There may be different questionnaire instances that have the same identifier but different
versions. The version can be appended to the url in a reference to allow a refrence
to a particular business version of the questionnaire with the format [url]|[version].
|
Waardendomein |
String |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
name
vl-dataelement101-5338
|
|
|
Id |
vl-dataelement101-5338 (2019‑03‑29)
|
Omschrijving |
Name for this questionnaire (computer friendly)
A natural language name identifying the questionnaire. This name should be usable
as an identifier for the module by machine processing applications such as code generation.
|
|
Rationale |
Support human navigation and code generation. |
Opmerking |
The name is not expected to be globally unique. The name should be a simple alpha-numeric
type name to ensure that it is computable friendly.
|
Waardendomein |
String |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
title
vl-dataelement101-5339
|
|
|
Id |
vl-dataelement101-5339 (2019‑03‑29)
|
Omschrijving |
Name for this questionnaire (human friendly)
A short, descriptive, user-friendly title for the questionnaire.
|
|
Opmerking |
This name does not need to be machine-processing friendly and may contain punctuation,
white-space, etc.
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
title-renderingStyle
vl-dataelement101-5342
|
|
|
Id |
vl-dataelement101-5342 (2019‑03‑29)
|
Omschrijving |
Html style value
Identifies how the specified element should be rendered when displayed.
|
Opmerking |
This extension would be equivalent to setting the HTML "style" attribute on the root
element for the element containing the extension.
|
Waardendomein |
String |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
title-xhtml
vl-dataelement101-5347
|
|
|
Id |
vl-dataelement101-5347 (2019‑03‑29)
|
Omschrijving |
String equivalent with html markup
This is an equivalent of the string on which the extension is sent, but includes additional
XHTML markup, such as bold, italics, styles, tables, etc. Existing [restrictions on
XHTML content](narrative.html#security) apply. Note that using [markdown](extension-rendering-markdown.html)
allows for greater flexibility of display.
|
Waardendomein |
String |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
value
vl-dataelement101-5352
|
|
|
Id |
vl-dataelement101-5352 (2019‑03‑29)
|
Omschrijving |
Primitive value for string
Primitive value for string
|
Waardendomein |
String |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
status
vl-dataelement101-5353
|
|
|
Id |
vl-dataelement101-5353 (2019‑03‑29)
|
Omschrijving |
draft | active | retired | unknown
The status of this questionnaire. Enables tracking the life-cycle of the content.
|
isSummary |
true |
isModifier |
true |
|
Opmerking |
Allows filtering of questionnaires that are appropriate for use vs. not. This is labeled
as "Is Modifier" because applications should not use a retired questionnaire without
due consideration.
|
Waardendomein |
Code |
Keuzelijst |
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
experimental
vl-dataelement101-5354
|
|
|
Id |
vl-dataelement101-5354 (2019‑03‑29)
|
Omschrijving |
For testing purposes, not real usage
A boolean value to indicate that this questionnaire is authored for testing purposes
(or education/evaluation/marketing), and is not intended to be used for genuine usage.
|
isSummary |
true |
isModifier |
true |
|
Rationale |
Enables experimental content to be developed following the same lifecycle that would
be used for a production-level questionnaire.
|
Opmerking |
Allows filtering of questionnaire that are appropriate for use vs. not. This is labeled
as "Is Modifier" because applications should not use an experimental questionnaire
in production.
|
Waardendomein |
Boolean |
|
|
date
vl-dataelement101-5355
|
|
|
Id |
vl-dataelement101-5355 (2019‑03‑29)
|
Omschrijving |
Date this was last changed
Identifies when this version of the form was created. Changes whenever the form is
updated.
|
|
Opmerking |
Note that this is not the same as the resource last-modified-date, since the resource
may be a secondary representation of the questionnaire. Additional specific dates
may be added as extensions or be found by consulting Provenances associated with past
versions of the resource.
|
Waardendomein |
Datum/tijd |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
publisher
vl-dataelement101-5356
|
|
|
Id |
vl-dataelement101-5356 (2019‑03‑29)
|
Omschrijving |
Name of the publisher (organization or individual)
The name of the individual or organization that published the questionnaire.
|
|
Rationale |
Helps establish the "authority/credibility" of the questionnaire. May also allow for
contact.
|
Opmerking |
Usually an organization, but may be an individual. The publisher (or steward) of the
questionnaire is the organization or individual primarily responsible for the maintenance
and upkeep of the questionnaire. This is not necessarily the same individual or organization
that developed and initially authored the content. The publisher is the primary point
of contact for questions or issues with the questionnaire. This item SHOULD be populated
unless the information is available from context.
|
Waardendomein |
String |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
description
vl-dataelement101-5357
|
|
|
Id |
vl-dataelement101-5357 (2019‑03‑29)
|
Omschrijving |
Natural language description of the questionnaire
A free text natural language description of the questionnaire from a consumer's perspective.
|
Opmerking |
This description can be used to capture details such as why the questionnaire was
built, comments about misuse, instructions for clinical use and interpretation, literature
references, examples from the paper world, etc. It is not a rendering of the questionnaire
as conveyed in the 'text' field of the resource itself. This item SHOULD be populated
unless the information is available from context (e.g. the language of the profile
is presumed to be the predominant language in the place the profile was created).
|
Waardendomein |
Tekst |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
purpose
vl-dataelement101-5358
|
|
|
Id |
vl-dataelement101-5358 (2019‑03‑29)
|
Omschrijving |
Why this questionnaire is defined
Explaination of why this questionnaire is needed and why it has been designed as it
has.
|
Opmerking |
This element does not describe the usage of the questionnaire Instead it provides
traceability of ''why'' the resource is either needed or ''why'' it is defined as
it is. This may be used to point to source materials or specifications that drove
the structure of this questionnaire.
|
Waardendomein |
Tekst |
|
|
approvalDate
vl-dataelement101-5359
|
|
|
Id |
vl-dataelement101-5359 (2019‑03‑29)
|
Omschrijving |
When the questionnaire was approved by publisher
The date on which the resource content was approved by the publisher. Approval happens
once when the content is officially approved for usage.
|
Opmerking |
The 'date' element may be more recent than the approval date because of minor changes
/ editorial corrections.
|
Waardendomein |
Datum |
Eigenschap |
Tijdstempelprecisie |
tenminste dag, maand en jaar |
|
|
|
lastReviewDate
vl-dataelement101-5360
|
|
|
Id |
vl-dataelement101-5360 (2019‑03‑29)
|
Omschrijving |
When the questionnaire was last reviewed
The date on which the resource content was last reviewed. Review happens periodically
after approval, but doesn't change the original approval date.
|
Rationale |
Gives a sense of how "current" the content is. Resources that have not been reviewed
in a long time may have a risk of being less appropriate/relevant.
|
Opmerking |
If specified, this is usually after the approval date. |
Waardendomein |
Datum |
Eigenschap |
Tijdstempelprecisie |
tenminste dag, maand en jaar |
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
effectivePeriod
vl-dataelement101-5361
|
|
|
Id |
vl-dataelement101-5361 (2019‑03‑29)
|
Omschrijving |
When the questionnaire is expected to be used
The period during which the questionnaire content was or is planned to be in active
use.
|
Rationale |
Allows establishing a transition before a resource comes into effect and also allows
for a sunsetting process when new versions of a the questionnaire are or are expected
to be used instead.
|
Opmerking |
The effective period for a questionnaire determines when the content is applicable
for usage and is independent of publication and review dates. For example, a measure
intended to be used for the year 2016 might be published in 2015.
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
startDatumTijd
vl-dataelement101-5771
|
|
|
Id |
vl-dataelement101-5771 (2019‑04‑09 10:19:50)
|
Concept erft van |
NL-CM-20.3.2 (2017‑12‑31)
|
Omschrijving |
De begindatum en tijd van het interval |
Waardendomein |
Datum/tijd |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
eindDatumTijd
vl-dataelement101-5772
|
|
|
Id |
vl-dataelement101-5772 (2019‑04‑09 10:19:50)
|
Concept erft van |
NL-CM-20.3.3 (2017‑12‑31)
|
Omschrijving |
De einddatum en tijd van het interval |
Waardendomein |
Datum/tijd |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
useContext
vl-dataelement101-5362
|
|
|
Id |
vl-dataelement101-5362 (2019‑03‑29)
|
Omschrijving |
Context the content is intended to support
The content was developed with a focus and intent of supporting the contexts that
are listed. These terms may be used to assist with indexing and searching for appropriate
questionnaire instances.
|
|
Rationale |
Assist in searching for appropriate content. |
Opmerking |
When multiple useContexts are specified, there is no expectation whether all or any
of the contexts apply.
|
|
|
context-gender
vl-dataelement101-5363
|
|
|
Id |
vl-dataelement101-5363 (2019‑03‑29)
|
Omschrijving |
Gender context
The content was developed with a focus and intent of supporting the contexts that
are listed. These terms may be used to assist with indexing and searching for appropriate
questionnaire instances.
|
|
Rationale |
Assist in searching for appropriate content. |
Opmerking |
When multiple useContexts are specified, there is no expectation whether all or any
of the contexts apply.
|
|
|
code
vl-dataelement101-5366
|
|
|
Id |
vl-dataelement101-5366 (2019‑03‑29)
|
Omschrijving |
Type of context being specified
A code that identifies the type of context being specified by this usage context.
|
|
Opmerking |
Codes may be defined very casually in enumerations or code lists, up to very formal
definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
|
|
|
system
vl-dataelement101-5369
|
|
|
Id |
vl-dataelement101-5369 (2019‑03‑29)
|
Omschrijving |
Identity of the terminology system
The identification of the code system that defines the meaning of the symbol in the
code.
|
|
Rationale |
Need to be unambiguous about the source of the definition of the symbol. |
Opmerking |
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL
be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list
of FHIR defined special URIs or it should de-reference to some definition that establish
the system clearly and unambiguously.
|
Waardendomein |
String |
|
|
version
vl-dataelement101-5370
|
|
|
Id |
vl-dataelement101-5370 (2019‑03‑29)
|
Omschrijving |
Version of the system - if relevant
The version of the code system which was used when choosing this code. Note that a
well-maintained code system does not need the version reported, because the meaning
of codes is consistent across versions. However this cannot consistently be assured.
and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
|
|
Opmerking |
Where the terminology does not clearly define what string should be used to identify
code system versions, the recommendation is to use the date (expressed in FHIR date
format) on which that version was officially published as the version date.
|
Waardendomein |
String |
|
|
code
vl-dataelement101-5371
|
|
|
Id |
vl-dataelement101-5371 (2019‑03‑29)
|
Omschrijving |
Symbol in syntax defined by the system
A symbol in syntax defined by the system. The symbol may be a predefined code or an
expression in a syntax defined by the coding system (e.g. post-coordination).
|
|
Rationale |
Need to refer to a particular code in the system. |
Waardendomein |
Code |
|
|
display
vl-dataelement101-5372
|
|
|
Id |
vl-dataelement101-5372 (2019‑03‑29)
|
Omschrijving |
Representation defined by the system
A representation of the meaning of the code in the system, following the rules of
the system.
|
|
Rationale |
Need to be able to carry a human-readable meaning of the code for readers that do
not know the system.
|
Waardendomein |
String |
|
|
userSelected
vl-dataelement101-5373
|
|
|
Id |
vl-dataelement101-5373 (2019‑03‑29)
|
Omschrijving |
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - i.e. off a pick list of
available items (codes or displays).
|
|
Rationale |
This has been identified as a clinical safety criterium - that this exact system/code
pair was chosen explicitly, rather than inferred by the system based on some rules
or language processing.
|
Opmerking |
Amongst a set of alternatives, a directly chosen code is the most appropriate starting
point for new translations. There is some ambiguity about what exactly 'directly chosen'
implies, and trading partner agreement may be needed to clarify the use of this element
and its consequences more completely.
|
Waardendomein |
Boolean |
|
|
valueCodeableConcept
vl-dataelement101-5374
|
|
|
Id |
vl-dataelement101-5374 (2019‑03‑29)
|
Omschrijving |
Applies to gender
A value that defines the context specified in this context of use. The interpretation
of the value is defined by the code.
|
|
Opmerking |
Not all terminology uses fit this general pattern. In some cases, models should not
use CodeableConcept and use Coding directly and provide their own structure for managing
text, codings, translations and the relationship between elements and pre- and post-coordination.
|
Waardendomein |
Code |
Keuzelijst |
|
|
|
context-age
vl-dataelement101-5375
|
|
|
Id |
vl-dataelement101-5375 (2019‑03‑29)
|
Omschrijving |
Gender context
The content was developed with a focus and intent of supporting the contexts that
are listed. These terms may be used to assist with indexing and searching for appropriate
questionnaire instances.
|
|
Rationale |
Assist in searching for appropriate content. |
Opmerking |
When multiple useContexts are specified, there is no expectation whether all or any
of the contexts apply.
|
|
|
code
vl-dataelement101-5378
|
|
|
Id |
vl-dataelement101-5378 (2019‑03‑29)
|
Omschrijving |
Type of context being specified
A code that identifies the type of context being specified by this usage context.
|
|
Opmerking |
Codes may be defined very casually in enumerations or code lists, up to very formal
definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
|
|
|
system
vl-dataelement101-5381
|
|
|
Id |
vl-dataelement101-5381 (2019‑03‑29)
|
Omschrijving |
Identity of the terminology system
The identification of the code system that defines the meaning of the symbol in the
code.
|
|
Rationale |
Need to be unambiguous about the source of the definition of the symbol. |
Opmerking |
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL
be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list
of FHIR defined special URIs or it should de-reference to some definition that establish
the system clearly and unambiguously.
|
Waardendomein |
String |
|
|
version
vl-dataelement101-5382
|
|
|
Id |
vl-dataelement101-5382 (2019‑03‑29)
|
Omschrijving |
Version of the system - if relevant
The version of the code system which was used when choosing this code. Note that a
well-maintained code system does not need the version reported, because the meaning
of codes is consistent across versions. However this cannot consistently be assured.
and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
|
|
Opmerking |
Where the terminology does not clearly define what string should be used to identify
code system versions, the recommendation is to use the date (expressed in FHIR date
format) on which that version was officially published as the version date.
|
Waardendomein |
String |
|
|
code
vl-dataelement101-5383
|
|
|
Id |
vl-dataelement101-5383 (2019‑03‑29)
|
Omschrijving |
Symbol in syntax defined by the system
A symbol in syntax defined by the system. The symbol may be a predefined code or an
expression in a syntax defined by the coding system (e.g. post-coordination).
|
|
Rationale |
Need to refer to a particular code in the system. |
Waardendomein |
Code |
|
|
display
vl-dataelement101-5384
|
|
|
Id |
vl-dataelement101-5384 (2019‑03‑29)
|
Omschrijving |
Representation defined by the system
A representation of the meaning of the code in the system, following the rules of
the system.
|
|
Rationale |
Need to be able to carry a human-readable meaning of the code for readers that do
not know the system.
|
Waardendomein |
String |
|
|
userSelected
vl-dataelement101-5385
|
|
|
Id |
vl-dataelement101-5385 (2019‑03‑29)
|
Omschrijving |
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - i.e. off a pick list of
available items (codes or displays).
|
|
Rationale |
This has been identified as a clinical safety criterium - that this exact system/code
pair was chosen explicitly, rather than inferred by the system based on some rules
or language processing.
|
Opmerking |
Amongst a set of alternatives, a directly chosen code is the most appropriate starting
point for new translations. There is some ambiguity about what exactly 'directly chosen'
implies, and trading partner agreement may be needed to clarify the use of this element
and its consequences more completely.
|
Waardendomein |
Boolean |
|
|
valueRange
vl-dataelement101-5386
|
|
|
Id |
vl-dataelement101-5386 (2019‑03‑29)
|
Omschrijving |
Applies to gender
A value that defines the context specified in this context of use. The interpretation
of the value is defined by the code.
|
|
Opmerking |
Not all terminology uses fit this general pattern. In some cases, models should not
use CodeableConcept and use Coding directly and provide their own structure for managing
text, codings, translations and the relationship between elements and pre- and post-coordination.
|
Waardendomein |
Samengestelde gegevens |
|
|
context-focus
vl-dataelement101-5387
|
|
|
Id |
vl-dataelement101-5387 (2019‑03‑29)
|
Omschrijving |
Gender context
The content was developed with a focus and intent of supporting the contexts that
are listed. These terms may be used to assist with indexing and searching for appropriate
questionnaire instances.
|
|
Rationale |
Assist in searching for appropriate content. |
Opmerking |
When multiple useContexts are specified, there is no expectation whether all or any
of the contexts apply.
|
|
|
code
vl-dataelement101-5390
|
|
|
Id |
vl-dataelement101-5390 (2019‑03‑29)
|
Omschrijving |
Type of context being specified
A code that identifies the type of context being specified by this usage context.
|
|
Opmerking |
Codes may be defined very casually in enumerations or code lists, up to very formal
definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
|
|
|
system
vl-dataelement101-5393
|
|
|
Id |
vl-dataelement101-5393 (2019‑03‑29)
|
Omschrijving |
Identity of the terminology system
The identification of the code system that defines the meaning of the symbol in the
code.
|
|
Rationale |
Need to be unambiguous about the source of the definition of the symbol. |
Opmerking |
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL
be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list
of FHIR defined special URIs or it should de-reference to some definition that establish
the system clearly and unambiguously.
|
Waardendomein |
String |
|
|
version
vl-dataelement101-5394
|
|
|
Id |
vl-dataelement101-5394 (2019‑03‑29)
|
Omschrijving |
Version of the system - if relevant
The version of the code system which was used when choosing this code. Note that a
well-maintained code system does not need the version reported, because the meaning
of codes is consistent across versions. However this cannot consistently be assured.
and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
|
|
Opmerking |
Where the terminology does not clearly define what string should be used to identify
code system versions, the recommendation is to use the date (expressed in FHIR date
format) on which that version was officially published as the version date.
|
Waardendomein |
String |
|
|
code
vl-dataelement101-5395
|
|
|
Id |
vl-dataelement101-5395 (2019‑03‑29)
|
Omschrijving |
Symbol in syntax defined by the system
A symbol in syntax defined by the system. The symbol may be a predefined code or an
expression in a syntax defined by the coding system (e.g. post-coordination).
|
|
Rationale |
Need to refer to a particular code in the system. |
Waardendomein |
Code |
|
|
display
vl-dataelement101-5396
|
|
|
Id |
vl-dataelement101-5396 (2019‑03‑29)
|
Omschrijving |
Representation defined by the system
A representation of the meaning of the code in the system, following the rules of
the system.
|
|
Rationale |
Need to be able to carry a human-readable meaning of the code for readers that do
not know the system.
|
Waardendomein |
String |
|
|
userSelected
vl-dataelement101-5397
|
|
|
Id |
vl-dataelement101-5397 (2019‑03‑29)
|
Omschrijving |
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - i.e. off a pick list of
available items (codes or displays).
|
|
Rationale |
This has been identified as a clinical safety criterium - that this exact system/code
pair was chosen explicitly, rather than inferred by the system based on some rules
or language processing.
|
Opmerking |
Amongst a set of alternatives, a directly chosen code is the most appropriate starting
point for new translations. There is some ambiguity about what exactly 'directly chosen'
implies, and trading partner agreement may be needed to clarify the use of this element
and its consequences more completely.
|
Waardendomein |
Boolean |
|
|
valueCodeableConcept
vl-dataelement101-5398
|
|
|
Id |
vl-dataelement101-5398 (2019‑03‑29)
|
Omschrijving |
Applies to gender
A value that defines the context specified in this context of use. The interpretation
of the value is defined by the code.
|
|
Opmerking |
Not all terminology uses fit this general pattern. In some cases, models should not
use CodeableConcept and use Coding directly and provide their own structure for managing
text, codings, translations and the relationship between elements and pre- and post-coordination.
|
Waardendomein |
Code |
Keuzelijst |
|
|
|
context-user
vl-dataelement101-5399
|
|
|
Id |
vl-dataelement101-5399 (2019‑03‑29)
|
Omschrijving |
User context
The content was developed with a focus and intent of supporting the contexts that
are listed. These terms may be used to assist with indexing and searching for appropriate
questionnaire instances.
|
|
Rationale |
Assist in searching for appropriate content. |
Opmerking |
When multiple useContexts are specified, there is no expectation whether all or any
of the contexts apply.
|
|
|
code
vl-dataelement101-5402
|
|
|
Id |
vl-dataelement101-5402 (2019‑03‑29)
|
Omschrijving |
Type of context being specified
A code that identifies the type of context being specified by this usage context.
|
|
Opmerking |
Codes may be defined very casually in enumerations or code lists, up to very formal
definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
|
|
|
system
vl-dataelement101-5405
|
|
|
Id |
vl-dataelement101-5405 (2019‑03‑29)
|
Omschrijving |
Identity of the terminology system
The identification of the code system that defines the meaning of the symbol in the
code.
|
|
Rationale |
Need to be unambiguous about the source of the definition of the symbol. |
Opmerking |
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL
be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list
of FHIR defined special URIs or it should de-reference to some definition that establish
the system clearly and unambiguously.
|
Waardendomein |
String |
|
|
version
vl-dataelement101-5406
|
|
|
Id |
vl-dataelement101-5406 (2019‑03‑29)
|
Omschrijving |
Version of the system - if relevant
The version of the code system which was used when choosing this code. Note that a
well-maintained code system does not need the version reported, because the meaning
of codes is consistent across versions. However this cannot consistently be assured.
and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
|
|
Opmerking |
Where the terminology does not clearly define what string should be used to identify
code system versions, the recommendation is to use the date (expressed in FHIR date
format) on which that version was officially published as the version date.
|
Waardendomein |
String |
|
|
code
vl-dataelement101-5407
|
|
|
Id |
vl-dataelement101-5407 (2019‑03‑29)
|
Omschrijving |
Symbol in syntax defined by the system
A symbol in syntax defined by the system. The symbol may be a predefined code or an
expression in a syntax defined by the coding system (e.g. post-coordination).
|
|
Rationale |
Need to refer to a particular code in the system. |
Waardendomein |
Code |
|
|
display
vl-dataelement101-5408
|
|
|
Id |
vl-dataelement101-5408 (2019‑03‑29)
|
Omschrijving |
Representation defined by the system
A representation of the meaning of the code in the system, following the rules of
the system.
|
|
Rationale |
Need to be able to carry a human-readable meaning of the code for readers that do
not know the system.
|
Waardendomein |
String |
|
|
userSelected
vl-dataelement101-5409
|
|
|
Id |
vl-dataelement101-5409 (2019‑03‑29)
|
Omschrijving |
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - i.e. off a pick list of
available items (codes or displays).
|
|
Rationale |
This has been identified as a clinical safety criterium - that this exact system/code
pair was chosen explicitly, rather than inferred by the system based on some rules
or language processing.
|
Opmerking |
Amongst a set of alternatives, a directly chosen code is the most appropriate starting
point for new translations. There is some ambiguity about what exactly 'directly chosen'
implies, and trading partner agreement may be needed to clarify the use of this element
and its consequences more completely.
|
Waardendomein |
Boolean |
|
|
valueCodeableConcept
vl-dataelement101-5410
|
|
|
Id |
vl-dataelement101-5410 (2019‑03‑29)
|
Omschrijving |
Applies to user
A value that defines the context specified in this context of use. The interpretation
of the value is defined by the code.
|
|
Opmerking |
Not all terminology uses fit this general pattern. In some cases, models should not
use CodeableConcept and use Coding directly and provide their own structure for managing
text, codings, translations and the relationship between elements and pre- and post-coordination.
|
Waardendomein |
Code |
|
|
context-workflow
vl-dataelement101-5411
|
|
|
Id |
vl-dataelement101-5411 (2019‑03‑29)
|
Omschrijving |
Workflow context
The content was developed with a focus and intent of supporting the contexts that
are listed. These terms may be used to assist with indexing and searching for appropriate
questionnaire instances.
|
|
Rationale |
Assist in searching for appropriate content. |
Opmerking |
When multiple useContexts are specified, there is no expectation whether all or any
of the contexts apply.
|
|
|
code
vl-dataelement101-5414
|
|
|
Id |
vl-dataelement101-5414 (2019‑03‑29)
|
Omschrijving |
Type of context being specified
A code that identifies the type of context being specified by this usage context.
|
|
Opmerking |
Codes may be defined very casually in enumerations or code lists, up to very formal
definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
|
|
|
system
vl-dataelement101-5417
|
|
|
Id |
vl-dataelement101-5417 (2019‑03‑29)
|
Omschrijving |
Identity of the terminology system
The identification of the code system that defines the meaning of the symbol in the
code.
|
|
Rationale |
Need to be unambiguous about the source of the definition of the symbol. |
Opmerking |
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL
be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list
of FHIR defined special URIs or it should de-reference to some definition that establish
the system clearly and unambiguously.
|
Waardendomein |
String |
|
|
version
vl-dataelement101-5418
|
|
|
Id |
vl-dataelement101-5418 (2019‑03‑29)
|
Omschrijving |
Version of the system - if relevant
The version of the code system which was used when choosing this code. Note that a
well-maintained code system does not need the version reported, because the meaning
of codes is consistent across versions. However this cannot consistently be assured.
and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
|
|
Opmerking |
Where the terminology does not clearly define what string should be used to identify
code system versions, the recommendation is to use the date (expressed in FHIR date
format) on which that version was officially published as the version date.
|
Waardendomein |
String |
|
|
code
vl-dataelement101-5419
|
|
|
Id |
vl-dataelement101-5419 (2019‑03‑29)
|
Omschrijving |
Symbol in syntax defined by the system
A symbol in syntax defined by the system. The symbol may be a predefined code or an
expression in a syntax defined by the coding system (e.g. post-coordination).
|
|
Rationale |
Need to refer to a particular code in the system. |
Waardendomein |
Code |
|
|
display
vl-dataelement101-5420
|
|
|
Id |
vl-dataelement101-5420 (2019‑03‑29)
|
Omschrijving |
Representation defined by the system
A representation of the meaning of the code in the system, following the rules of
the system.
|
|
Rationale |
Need to be able to carry a human-readable meaning of the code for readers that do
not know the system.
|
Waardendomein |
String |
|
|
userSelected
vl-dataelement101-5421
|
|
|
Id |
vl-dataelement101-5421 (2019‑03‑29)
|
Omschrijving |
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - i.e. off a pick list of
available items (codes or displays).
|
|
Rationale |
This has been identified as a clinical safety criterium - that this exact system/code
pair was chosen explicitly, rather than inferred by the system based on some rules
or language processing.
|
Opmerking |
Amongst a set of alternatives, a directly chosen code is the most appropriate starting
point for new translations. There is some ambiguity about what exactly 'directly chosen'
implies, and trading partner agreement may be needed to clarify the use of this element
and its consequences more completely.
|
Waardendomein |
Boolean |
|
|
valueCodeableConcept
vl-dataelement101-5422
|
|
|
Id |
vl-dataelement101-5422 (2019‑03‑29)
|
Omschrijving |
Applies to workflow
A value that defines the context specified in this context of use. The interpretation
of the value is defined by the code.
|
|
Opmerking |
Not all terminology uses fit this general pattern. In some cases, models should not
use CodeableConcept and use Coding directly and provide their own structure for managing
text, codings, translations and the relationship between elements and pre- and post-coordination.
|
Waardendomein |
Code |
Keuzelijst |
|
|
|
context-task
vl-dataelement101-5423
|
|
|
Id |
vl-dataelement101-5423 (2019‑03‑29)
|
Omschrijving |
Gender context
The content was developed with a focus and intent of supporting the contexts that
are listed. These terms may be used to assist with indexing and searching for appropriate
questionnaire instances.
|
|
Rationale |
Assist in searching for appropriate content. |
Opmerking |
When multiple useContexts are specified, there is no expectation whether all or any
of the contexts apply.
|
|
|
code
vl-dataelement101-5426
|
|
|
Id |
vl-dataelement101-5426 (2019‑03‑29)
|
Omschrijving |
Type of context being specified
A code that identifies the type of context being specified by this usage context.
|
|
Opmerking |
Codes may be defined very casually in enumerations or code lists, up to very formal
definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
|
|
|
system
vl-dataelement101-5429
|
|
|
Id |
vl-dataelement101-5429 (2019‑03‑29)
|
Omschrijving |
Identity of the terminology system
The identification of the code system that defines the meaning of the symbol in the
code.
|
|
Rationale |
Need to be unambiguous about the source of the definition of the symbol. |
Opmerking |
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL
be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list
of FHIR defined special URIs or it should de-reference to some definition that establish
the system clearly and unambiguously.
|
Waardendomein |
String |
|
|
version
vl-dataelement101-5430
|
|
|
Id |
vl-dataelement101-5430 (2019‑03‑29)
|
Omschrijving |
Version of the system - if relevant
The version of the code system which was used when choosing this code. Note that a
well-maintained code system does not need the version reported, because the meaning
of codes is consistent across versions. However this cannot consistently be assured.
and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
|
|
Opmerking |
Where the terminology does not clearly define what string should be used to identify
code system versions, the recommendation is to use the date (expressed in FHIR date
format) on which that version was officially published as the version date.
|
Waardendomein |
String |
|
|
code
vl-dataelement101-5431
|
|
|
Id |
vl-dataelement101-5431 (2019‑03‑29)
|
Omschrijving |
Symbol in syntax defined by the system
A symbol in syntax defined by the system. The symbol may be a predefined code or an
expression in a syntax defined by the coding system (e.g. post-coordination).
|
|
Rationale |
Need to refer to a particular code in the system. |
Waardendomein |
Code |
|
|
display
vl-dataelement101-5432
|
|
|
Id |
vl-dataelement101-5432 (2019‑03‑29)
|
Omschrijving |
Representation defined by the system
A representation of the meaning of the code in the system, following the rules of
the system.
|
|
Rationale |
Need to be able to carry a human-readable meaning of the code for readers that do
not know the system.
|
Waardendomein |
String |
|
|
userSelected
vl-dataelement101-5433
|
|
|
Id |
vl-dataelement101-5433 (2019‑03‑29)
|
Omschrijving |
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - i.e. off a pick list of
available items (codes or displays).
|
|
Rationale |
This has been identified as a clinical safety criterium - that this exact system/code
pair was chosen explicitly, rather than inferred by the system based on some rules
or language processing.
|
Opmerking |
Amongst a set of alternatives, a directly chosen code is the most appropriate starting
point for new translations. There is some ambiguity about what exactly 'directly chosen'
implies, and trading partner agreement may be needed to clarify the use of this element
and its consequences more completely.
|
Waardendomein |
Boolean |
|
|
valueCodeableConcept
vl-dataelement101-5434
|
|
|
Id |
vl-dataelement101-5434 (2019‑03‑29)
|
Omschrijving |
Applies to gender
A value that defines the context specified in this context of use. The interpretation
of the value is defined by the code.
|
|
Opmerking |
Not all terminology uses fit this general pattern. In some cases, models should not
use CodeableConcept and use Coding directly and provide their own structure for managing
text, codings, translations and the relationship between elements and pre- and post-coordination.
|
Waardendomein |
Code |
Keuzelijst |
Conceptenlijst |
|
Waardelijst voorbeeld ActTaskCode (versie DYNAMISCH)
|
|
|
|
context-venue
vl-dataelement101-5435
|
|
|
Id |
vl-dataelement101-5435 (2019‑03‑29)
|
Omschrijving |
Venue context
The content was developed with a focus and intent of supporting the contexts that
are listed. These terms may be used to assist with indexing and searching for appropriate
questionnaire instances.
|
|
Rationale |
Assist in searching for appropriate content. |
Opmerking |
When multiple useContexts are specified, there is no expectation whether all or any
of the contexts apply.
|
|
|
code
vl-dataelement101-5438
|
|
|
Id |
vl-dataelement101-5438 (2019‑03‑29)
|
Omschrijving |
Type of context being specified
A code that identifies the type of context being specified by this usage context.
|
|
Opmerking |
Codes may be defined very casually in enumerations or code lists, up to very formal
definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
|
|
|
system
vl-dataelement101-5441
|
|
|
Id |
vl-dataelement101-5441 (2019‑03‑29)
|
Omschrijving |
Identity of the terminology system
The identification of the code system that defines the meaning of the symbol in the
code.
|
|
Rationale |
Need to be unambiguous about the source of the definition of the symbol. |
Opmerking |
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL
be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list
of FHIR defined special URIs or it should de-reference to some definition that establish
the system clearly and unambiguously.
|
Waardendomein |
String |
|
|
version
vl-dataelement101-5442
|
|
|
Id |
vl-dataelement101-5442 (2019‑03‑29)
|
Omschrijving |
Version of the system - if relevant
The version of the code system which was used when choosing this code. Note that a
well-maintained code system does not need the version reported, because the meaning
of codes is consistent across versions. However this cannot consistently be assured.
and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
|
|
Opmerking |
Where the terminology does not clearly define what string should be used to identify
code system versions, the recommendation is to use the date (expressed in FHIR date
format) on which that version was officially published as the version date.
|
Waardendomein |
String |
|
|
code
vl-dataelement101-5443
|
|
|
Id |
vl-dataelement101-5443 (2019‑03‑29)
|
Omschrijving |
Symbol in syntax defined by the system
A symbol in syntax defined by the system. The symbol may be a predefined code or an
expression in a syntax defined by the coding system (e.g. post-coordination).
|
|
Rationale |
Need to refer to a particular code in the system. |
Waardendomein |
Code |
|
|
display
vl-dataelement101-5444
|
|
|
Id |
vl-dataelement101-5444 (2019‑03‑29)
|
Omschrijving |
Representation defined by the system
A representation of the meaning of the code in the system, following the rules of
the system.
|
|
Rationale |
Need to be able to carry a human-readable meaning of the code for readers that do
not know the system.
|
Waardendomein |
String |
|
|
userSelected
vl-dataelement101-5445
|
|
|
Id |
vl-dataelement101-5445 (2019‑03‑29)
|
Omschrijving |
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - i.e. off a pick list of
available items (codes or displays).
|
|
Rationale |
This has been identified as a clinical safety criterium - that this exact system/code
pair was chosen explicitly, rather than inferred by the system based on some rules
or language processing.
|
Opmerking |
Amongst a set of alternatives, a directly chosen code is the most appropriate starting
point for new translations. There is some ambiguity about what exactly 'directly chosen'
implies, and trading partner agreement may be needed to clarify the use of this element
and its consequences more completely.
|
Waardendomein |
Boolean |
|
|
valueCodeableConcept
vl-dataelement101-5446
|
|
|
Id |
vl-dataelement101-5446 (2019‑03‑29)
|
Omschrijving |
Applies to venue
A value that defines the context specified in this context of use. The interpretation
of the value is defined by the code.
|
|
Opmerking |
Not all terminology uses fit this general pattern. In some cases, models should not
use CodeableConcept and use Coding directly and provide their own structure for managing
text, codings, translations and the relationship between elements and pre- and post-coordination.
|
Waardendomein |
Code |
|
|
context-species
vl-dataelement101-5447
|
|
|
Id |
vl-dataelement101-5447 (2019‑03‑29)
|
Omschrijving |
Gender context
The content was developed with a focus and intent of supporting the contexts that
are listed. These terms may be used to assist with indexing and searching for appropriate
questionnaire instances.
|
|
Rationale |
Assist in searching for appropriate content. |
Opmerking |
When multiple useContexts are specified, there is no expectation whether all or any
of the contexts apply.
|
|
|
code
vl-dataelement101-5450
|
|
|
Id |
vl-dataelement101-5450 (2019‑03‑29)
|
Omschrijving |
Type of context being specified
A code that identifies the type of context being specified by this usage context.
|
|
Opmerking |
Codes may be defined very casually in enumerations or code lists, up to very formal
definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
|
|
|
system
vl-dataelement101-5453
|
|
|
Id |
vl-dataelement101-5453 (2019‑03‑29)
|
Omschrijving |
Identity of the terminology system
The identification of the code system that defines the meaning of the symbol in the
code.
|
|
Rationale |
Need to be unambiguous about the source of the definition of the symbol. |
Opmerking |
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL
be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list
of FHIR defined special URIs or it should de-reference to some definition that establish
the system clearly and unambiguously.
|
Waardendomein |
String |
|
|
version
vl-dataelement101-5454
|
|
|
Id |
vl-dataelement101-5454 (2019‑03‑29)
|
Omschrijving |
Version of the system - if relevant
The version of the code system which was used when choosing this code. Note that a
well-maintained code system does not need the version reported, because the meaning
of codes is consistent across versions. However this cannot consistently be assured.
and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
|
|
Opmerking |
Where the terminology does not clearly define what string should be used to identify
code system versions, the recommendation is to use the date (expressed in FHIR date
format) on which that version was officially published as the version date.
|
Waardendomein |
String |
|
|
code
vl-dataelement101-5455
|
|
|
Id |
vl-dataelement101-5455 (2019‑03‑29)
|
Omschrijving |
Symbol in syntax defined by the system
A symbol in syntax defined by the system. The symbol may be a predefined code or an
expression in a syntax defined by the coding system (e.g. post-coordination).
|
|
Rationale |
Need to refer to a particular code in the system. |
Waardendomein |
Code |
|
|
display
vl-dataelement101-5456
|
|
|
Id |
vl-dataelement101-5456 (2019‑03‑29)
|
Omschrijving |
Representation defined by the system
A representation of the meaning of the code in the system, following the rules of
the system.
|
|
Rationale |
Need to be able to carry a human-readable meaning of the code for readers that do
not know the system.
|
Waardendomein |
String |
|
|
userSelected
vl-dataelement101-5457
|
|
|
Id |
vl-dataelement101-5457 (2019‑03‑29)
|
Omschrijving |
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - i.e. off a pick list of
available items (codes or displays).
|
|
Rationale |
This has been identified as a clinical safety criterium - that this exact system/code
pair was chosen explicitly, rather than inferred by the system based on some rules
or language processing.
|
Opmerking |
Amongst a set of alternatives, a directly chosen code is the most appropriate starting
point for new translations. There is some ambiguity about what exactly 'directly chosen'
implies, and trading partner agreement may be needed to clarify the use of this element
and its consequences more completely.
|
Waardendomein |
Boolean |
|
|
valueCodeableConcept
vl-dataelement101-5458
|
|
|
Id |
vl-dataelement101-5458 (2019‑03‑29)
|
Omschrijving |
Applies to gender
A value that defines the context specified in this context of use. The interpretation
of the value is defined by the code.
|
|
Opmerking |
Not all terminology uses fit this general pattern. In some cases, models should not
use CodeableConcept and use Coding directly and provide their own structure for managing
text, codings, translations and the relationship between elements and pre- and post-coordination.
|
Waardendomein |
Code |
|
|
contextUser
vl-dataelement101-5459
|
|
|
Id |
vl-dataelement101-5459 (2019‑03‑29)
|
Omschrijving |
Gender context
The content was developed with a focus and intent of supporting the contexts that
are listed. These terms may be used to assist with indexing and searching for appropriate
questionnaire instances.
|
|
Rationale |
Assist in searching for appropriate content. |
Opmerking |
When multiple useContexts are specified, there is no expectation whether all or any
of the contexts apply.
|
|
|
code
vl-dataelement101-5462
|
|
|
Id |
vl-dataelement101-5462 (2019‑03‑29)
|
Omschrijving |
Type of context being specified
A code that identifies the type of context being specified by this usage context.
|
|
Opmerking |
Codes may be defined very casually in enumerations or code lists, up to very formal
definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
|
|
|
system
vl-dataelement101-5465
|
|
|
Id |
vl-dataelement101-5465 (2019‑03‑29)
|
Omschrijving |
Identity of the terminology system
The identification of the code system that defines the meaning of the symbol in the
code.
|
|
Rationale |
Need to be unambiguous about the source of the definition of the symbol. |
Opmerking |
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL
be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list
of FHIR defined special URIs or it should de-reference to some definition that establish
the system clearly and unambiguously.
|
Waardendomein |
String |
|
|
version
vl-dataelement101-5466
|
|
|
Id |
vl-dataelement101-5466 (2019‑03‑29)
|
Omschrijving |
Version of the system - if relevant
The version of the code system which was used when choosing this code. Note that a
well-maintained code system does not need the version reported, because the meaning
of codes is consistent across versions. However this cannot consistently be assured.
and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
|
|
Opmerking |
Where the terminology does not clearly define what string should be used to identify
code system versions, the recommendation is to use the date (expressed in FHIR date
format) on which that version was officially published as the version date.
|
Waardendomein |
String |
|
|
code
vl-dataelement101-5467
|
|
|
Id |
vl-dataelement101-5467 (2019‑03‑29)
|
Omschrijving |
Symbol in syntax defined by the system
A symbol in syntax defined by the system. The symbol may be a predefined code or an
expression in a syntax defined by the coding system (e.g. post-coordination).
|
|
Rationale |
Need to refer to a particular code in the system. |
Waardendomein |
Code |
|
|
display
vl-dataelement101-5468
|
|
|
Id |
vl-dataelement101-5468 (2019‑03‑29)
|
Omschrijving |
Representation defined by the system
A representation of the meaning of the code in the system, following the rules of
the system.
|
|
Rationale |
Need to be able to carry a human-readable meaning of the code for readers that do
not know the system.
|
Waardendomein |
String |
|
|
userSelected
vl-dataelement101-5469
|
|
|
Id |
vl-dataelement101-5469 (2019‑03‑29)
|
Omschrijving |
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - i.e. off a pick list of
available items (codes or displays).
|
|
Rationale |
This has been identified as a clinical safety criterium - that this exact system/code
pair was chosen explicitly, rather than inferred by the system based on some rules
or language processing.
|
Opmerking |
Amongst a set of alternatives, a directly chosen code is the most appropriate starting
point for new translations. There is some ambiguity about what exactly 'directly chosen'
implies, and trading partner agreement may be needed to clarify the use of this element
and its consequences more completely.
|
Waardendomein |
Boolean |
|
|
valueCodeableConcept
vl-dataelement101-5470
|
|
|
Id |
vl-dataelement101-5470 (2019‑03‑29)
|
Omschrijving |
Applies to user
A value that defines the context specified in this context of use. The interpretation
of the value is defined by the code.
|
|
Opmerking |
Not all terminology uses fit this general pattern. In some cases, models should not
use CodeableConcept and use Coding directly and provide their own structure for managing
text, codings, translations and the relationship between elements and pre- and post-coordination.
|
Waardendomein |
Code |
|
|
contextWorkflow
vl-dataelement101-5471
|
|
|
Id |
vl-dataelement101-5471 (2019‑03‑29)
|
Omschrijving |
Gender context
The content was developed with a focus and intent of supporting the contexts that
are listed. These terms may be used to assist with indexing and searching for appropriate
questionnaire instances.
|
|
Rationale |
Assist in searching for appropriate content. |
Opmerking |
When multiple useContexts are specified, there is no expectation whether all or any
of the contexts apply.
|
|
|
code
vl-dataelement101-5474
|
|
|
Id |
vl-dataelement101-5474 (2019‑03‑29)
|
Omschrijving |
Type of context being specified
A code that identifies the type of context being specified by this usage context.
|
|
Opmerking |
Codes may be defined very casually in enumerations or code lists, up to very formal
definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
|
|
|
system
vl-dataelement101-5477
|
|
|
Id |
vl-dataelement101-5477 (2019‑03‑29)
|
Omschrijving |
Identity of the terminology system
The identification of the code system that defines the meaning of the symbol in the
code.
|
|
Rationale |
Need to be unambiguous about the source of the definition of the symbol. |
Opmerking |
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL
be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list
of FHIR defined special URIs or it should de-reference to some definition that establish
the system clearly and unambiguously.
|
Waardendomein |
String |
|
|
version
vl-dataelement101-5478
|
|
|
Id |
vl-dataelement101-5478 (2019‑03‑29)
|
Omschrijving |
Version of the system - if relevant
The version of the code system which was used when choosing this code. Note that a
well-maintained code system does not need the version reported, because the meaning
of codes is consistent across versions. However this cannot consistently be assured.
and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
|
|
Opmerking |
Where the terminology does not clearly define what string should be used to identify
code system versions, the recommendation is to use the date (expressed in FHIR date
format) on which that version was officially published as the version date.
|
Waardendomein |
String |
|
|
code
vl-dataelement101-5479
|
|
|
Id |
vl-dataelement101-5479 (2019‑03‑29)
|
Omschrijving |
Symbol in syntax defined by the system
A symbol in syntax defined by the system. The symbol may be a predefined code or an
expression in a syntax defined by the coding system (e.g. post-coordination).
|
|
Rationale |
Need to refer to a particular code in the system. |
Waardendomein |
Code |
|
|
display
vl-dataelement101-5480
|
|
|
Id |
vl-dataelement101-5480 (2019‑03‑29)
|
Omschrijving |
Representation defined by the system
A representation of the meaning of the code in the system, following the rules of
the system.
|
|
Rationale |
Need to be able to carry a human-readable meaning of the code for readers that do
not know the system.
|
Waardendomein |
String |
|
|
userSelected
vl-dataelement101-5481
|
|
|
Id |
vl-dataelement101-5481 (2019‑03‑29)
|
Omschrijving |
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - i.e. off a pick list of
available items (codes or displays).
|
|
Rationale |
This has been identified as a clinical safety criterium - that this exact system/code
pair was chosen explicitly, rather than inferred by the system based on some rules
or language processing.
|
Opmerking |
Amongst a set of alternatives, a directly chosen code is the most appropriate starting
point for new translations. There is some ambiguity about what exactly 'directly chosen'
implies, and trading partner agreement may be needed to clarify the use of this element
and its consequences more completely.
|
Waardendomein |
Boolean |
|
|
valueCodeableConcept
vl-dataelement101-5482
|
|
|
Id |
vl-dataelement101-5482 (2019‑03‑29)
|
Omschrijving |
Applies to workflow
A value that defines the context specified in this context of use. The interpretation
of the value is defined by the code.
|
|
Opmerking |
Not all terminology uses fit this general pattern. In some cases, models should not
use CodeableConcept and use Coding directly and provide their own structure for managing
text, codings, translations and the relationship between elements and pre- and post-coordination.
|
Waardendomein |
Code |
|
|
contextVenue
vl-dataelement101-5483
|
|
|
Id |
vl-dataelement101-5483 (2019‑03‑29)
|
Omschrijving |
Gender context
The content was developed with a focus and intent of supporting the contexts that
are listed. These terms may be used to assist with indexing and searching for appropriate
questionnaire instances.
|
|
Rationale |
Assist in searching for appropriate content. |
Opmerking |
When multiple useContexts are specified, there is no expectation whether all or any
of the contexts apply.
|
|
|
code
vl-dataelement101-5486
|
|
|
Id |
vl-dataelement101-5486 (2019‑03‑29)
|
Omschrijving |
Type of context being specified
A code that identifies the type of context being specified by this usage context.
|
|
Opmerking |
Codes may be defined very casually in enumerations or code lists, up to very formal
definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
|
|
|
system
vl-dataelement101-5489
|
|
|
Id |
vl-dataelement101-5489 (2019‑03‑29)
|
Omschrijving |
Identity of the terminology system
The identification of the code system that defines the meaning of the symbol in the
code.
|
|
Rationale |
Need to be unambiguous about the source of the definition of the symbol. |
Opmerking |
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL
be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list
of FHIR defined special URIs or it should de-reference to some definition that establish
the system clearly and unambiguously.
|
Waardendomein |
String |
|
|
version
vl-dataelement101-5490
|
|
|
Id |
vl-dataelement101-5490 (2019‑03‑29)
|
Omschrijving |
Version of the system - if relevant
The version of the code system which was used when choosing this code. Note that a
well-maintained code system does not need the version reported, because the meaning
of codes is consistent across versions. However this cannot consistently be assured.
and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
|
|
Opmerking |
Where the terminology does not clearly define what string should be used to identify
code system versions, the recommendation is to use the date (expressed in FHIR date
format) on which that version was officially published as the version date.
|
Waardendomein |
String |
|
|
code
vl-dataelement101-5491
|
|
|
Id |
vl-dataelement101-5491 (2019‑03‑29)
|
Omschrijving |
Symbol in syntax defined by the system
A symbol in syntax defined by the system. The symbol may be a predefined code or an
expression in a syntax defined by the coding system (e.g. post-coordination).
|
|
Rationale |
Need to refer to a particular code in the system. |
Waardendomein |
Code |
|
|
display
vl-dataelement101-5492
|
|
|
Id |
vl-dataelement101-5492 (2019‑03‑29)
|
Omschrijving |
Representation defined by the system
A representation of the meaning of the code in the system, following the rules of
the system.
|
|
Rationale |
Need to be able to carry a human-readable meaning of the code for readers that do
not know the system.
|
Waardendomein |
String |
|
|
userSelected
vl-dataelement101-5493
|
|
|
Id |
vl-dataelement101-5493 (2019‑03‑29)
|
Omschrijving |
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - i.e. off a pick list of
available items (codes or displays).
|
|
Rationale |
This has been identified as a clinical safety criterium - that this exact system/code
pair was chosen explicitly, rather than inferred by the system based on some rules
or language processing.
|
Opmerking |
Amongst a set of alternatives, a directly chosen code is the most appropriate starting
point for new translations. There is some ambiguity about what exactly 'directly chosen'
implies, and trading partner agreement may be needed to clarify the use of this element
and its consequences more completely.
|
Waardendomein |
Boolean |
|
|
valueCodeableConcept
vl-dataelement101-5494
|
|
|
Id |
vl-dataelement101-5494 (2019‑03‑29)
|
Omschrijving |
Applies to venue
A value that defines the context specified in this context of use. The interpretation
of the value is defined by the code.
|
|
Opmerking |
Not all terminology uses fit this general pattern. In some cases, models should not
use CodeableConcept and use Coding directly and provide their own structure for managing
text, codings, translations and the relationship between elements and pre- and post-coordination.
|
Waardendomein |
Code |
|
|
contact
vl-dataelement101-5508
|
|
|
Id |
vl-dataelement101-5508 (2019‑03‑29)
|
Omschrijving |
Contact details for the publisher
Contact details to assist a user in finding and communicating with the publisher.
|
|
Opmerking |
May be a web site, an email address, a telephone number, etc. |
|
|
Zorgverlener
vl-dataelement101-8001
|
|
|
Id |
vl-dataelement101-8001 (2020‑02‑03 22:39:41)
|
Concept verwijst naar |
vl-dataelement101-7335 (2020‑02‑02 22:32:48)
|
Omschrijving |
Rootconcept van de bouwsteen Zorgverlener. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Zorgverlener. Bij verwijzing naar deze bouwsteen kan tevens de rol die de zorgverlener in het zorgproces
vervult, worden meegegeven. Voor zorgverleners kan dit bijvoorbeeld hoofdbehandelaar
of verwijzer zijn
|
|
|
Zorgaanbieder
vl-dataelement101-7957
|
|
|
Id |
vl-dataelement101-7957 (2020‑02‑03 22:18:36)
|
Concept verwijst naar |
vl-dataelement101-7299 (2020‑02‑02 22:24:44)
|
Omschrijving |
Rootconcept van de bouwsteen Zorgaanbieder. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Zorgaanbieder.
|
|
|
copyright
vl-dataelement101-5509
|
|
|
Id |
vl-dataelement101-5509 (2019‑03‑29)
|
Omschrijving |
Use and/or publishing restrictions
A copyright statement relating to the questionnaire and/or its contents. Copyright
statements are generally legal restrictions on the use and publishing of the questionnaire.
|
Rationale |
Consumers must be able to determine any legal restrictions on the use of the questionnaire
and/or its content.
|
Opmerking |
Systems are not required to have markdown support, and there is considerable variation
in markdown syntax, so the text should be readable without markdown processing. The
preferred markdown syntax is described here: http://daringfireball.net/projects/markdown/syntax
(and tests here: http://daringfireball.net/projects/downloads/MarkdownTest_1.0.zip)
|
Waardendomein |
Tekst |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
code
vl-dataelement101-5510
|
|
|
Id |
vl-dataelement101-5510 (2019‑03‑29)
|
Omschrijving |
Concept that represents the overall questionnaire
An identifier for this question or group of questions in a particular terminology
such as LOINC.
|
|
Rationale |
Allows linking of the complete Questionnaire resources to formal terminologies. It's
common for "panels" of questions to be identified by a code.
|
Opmerking |
Codes may be defined very casually in enumerations or code lists, up to very formal
definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.
|
Waardendomein |
Code |
Keuzelijst |
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
subjectType
vl-dataelement101-5511
|
|
|
Id |
vl-dataelement101-5511 (2019‑03‑29)
|
Omschrijving |
Resource that can be subject of QuestionnaireResponse
The types of subjects that can be the subject of responses created for the questionnaire.
|
|
Opmerking |
If none are specified, then the subject is unlimited. |
Waardendomein |
Code |
Keuzelijst |
Conceptenlijst |
|
Waardelijst required ResourceType (versie DYNAMISCH)
|
|
|
|
QuestionnaireItem
vl-dataelement101-7934
|
|
|
Id |
vl-dataelement101-7934 (2020‑02‑03 17:42:34)
|
Concept verwijst naar |
vl-dataelement101-5512 (2019‑03‑29)
|
Omschrijving |
Questions and sections within the Questionnaire
A particular question, question grouping or display text that is part of the questionnaire.
|
Opmerking |
The content of the questionnaire is constructed from an ordered, hierarchical collection
of items.
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
QuestionnaireItem
vl-dataelement101-5512
|
|
|
Id |
vl-dataelement101-5512 (2019‑03‑29)
|
Omschrijving |
Questions and sections within the Questionnaire
A particular question, question grouping or display text that is part of the questionnaire.
|
Opmerking |
The content of the questionnaire is constructed from an ordered, hierarchical collection
of items.
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
extension
vl-dataelement101-8060
|
|
|
|
|
itemMinOccurs
vl-dataelement101-5515
|
|
|
Id |
vl-dataelement101-5515 (2019‑03‑29)
|
Omschrijving |
Minimum repetitions
The minimum number of times the group must appear, or the minimum number of answers
for a question - when greater than 1.
|
Opmerking |
Default assumption for "required" elements is minOccurs=1. |
Waardendomein |
Aantal |
|
|
itemMaxOccurs
vl-dataelement101-5520
|
|
|
Id |
vl-dataelement101-5520 (2019‑03‑29)
|
Omschrijving |
Maximum repetitions
The maximum number of times the group must appear, or the minimum number of answers
for a question - when greater than 1 and not unlimited.
|
Opmerking |
Only relevant if the element has repeats=true and there's a need to constrain the
number of allowed repetitions.
|
Waardendomein |
Aantal |
|
|
itemOptionalDisplay
vl-dataelement101-5525
|
|
|
Id |
vl-dataelement101-5525 (2019‑03‑29)
|
Omschrijving |
Can suppress from display to user
If set to true, it means that the system displaying the form (or the individual encoding
the form for data capture) can choose to omit the item from display to the user.
|
Opmerking |
If a group or question that contains other groups or questions is marked as "optional",
all of its contents are automatically also treated as optional.
|
Waardendomein |
Boolean |
|
|
itemHidden
vl-dataelement101-5530
|
|
|
Id |
vl-dataelement101-5530 (2019‑03‑29)
|
Omschrijving |
Don't display to user
If true, indicates that the extended item should not be displayed to the user.
|
Opmerking |
If an item is hidden, all descendant items are hidden as well. |
Waardendomein |
Boolean |
|
|
usageMode
vl-dataelement101-5535
|
|
|
Id |
vl-dataelement101-5535 (2019‑03‑29)
|
Omschrijving |
capture | display | display-non-empty | capture-display | capture-display-non-empty
Identifies that the specified element should only appear in certain "modes" of operation.
|
|
Operationalisatie |
|
Waardendomein |
Code |
Keuzelijst |
|
|
|
itemControl
vl-dataelement101-5540
|
|
|
Id |
vl-dataelement101-5540 (2019‑03‑29)
|
Omschrijving |
E.g. Fly-over, Table, Checkbox, Combo-box, Lookup, etc.
The type of data entry control or structure that should be used to render the item.
|
Opmerking |
Different controls may be appropriate for different item types. It is up to the system
rendering a questionnaire as to what controls it will support and for which data types.
|
Operationalisatie |
|
Waardendomein |
Code |
Keuzelijst |
|
|
|
choiceOrientation
vl-dataelement101-5545
|
|
|
Id |
vl-dataelement101-5545 (2019‑03‑29)
|
Omschrijving |
horizontal | vertical
Identifies the desired orientation when rendering a list of choices (typically radio-box
or check-box lists).
|
Opmerking |
Systems may choose to wrap answers rather than attempting to display them all in one
row or column. Language conventions may determine the order in which the choices are
listed (left-to-right or right-to-left, etc.).
|
Waardendomein |
Code |
Keuzelijst |
|
|
|
minLength
vl-dataelement101-5550
|
|
|
Id |
vl-dataelement101-5550 (2019‑03‑29)
|
Omschrijving |
At least this many characters
The minimum number of characters that must be present in the simple data type to be
considered a "valid" instance.
|
Opmerking |
For base64binary, reflects the number of characters representing the encoded data,
not the number of bytes of the binary data.
|
Waardendomein |
Aantal |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
regex
vl-dataelement101-5555
|
|
|
Id |
vl-dataelement101-5555 (2019‑03‑29)
|
Omschrijving |
Regular expression pattern
A regular expression that defines the syntax for the data element to be considered
valid.
|
Waardendomein |
String |
|
|
entryFormat
vl-dataelement101-5560
|
|
|
Id |
vl-dataelement101-5560 (2019‑03‑29)
|
Omschrijving |
User prompt for format
Additional instructions for the user to guide their input (i.e. a human readable version
of a regular expression like "nnn-nnn-nnn"). In most UIs this is the placeholder (or
'ghost') text placed directly inside the edit controls and that disappear when the
control gets the focus.
|
Waardendomein |
String |
|
|
minValue
vl-dataelement101-5565
|
|
|
Id |
vl-dataelement101-5565 (2019‑03‑29)
|
Omschrijving |
Must be >= this value
The inclusive lower bound on the range of allowed values for the data element.
|
Opmerking |
Data type specified must be the same as the data type for the data element. |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
datum
vl-dataelement101-6593
|
|
|
Id |
vl-dataelement101-6593 (2019‑05‑02 18:33:31)
|
Omschrijving |
datum
|
Waardendomein |
Datum |
Eigenschap |
Tijdstempelprecisie |
tenminste dag, maand en jaar |
|
Gebruikt door
|
2 transacties, 0 templates, één maal geërfd |
|
Dit concept wordt geërfd door concept
datum in dataset vl-dataelement101-6599
|
|
|
datumTijd
vl-dataelement101-6594
|
|
|
Id |
vl-dataelement101-6594 (2019‑05‑02 18:34:04)
|
Omschrijving |
datumTijd
|
Waardendomein |
Datum/tijd |
Eigenschap |
Tijdstempelprecisie |
tenminste dag, maand en jaar, uur en minuut |
|
Gebruikt door
|
2 transacties, 0 templates, één maal geërfd |
|
Dit concept wordt geërfd door concept
datumTijd in dataset vl-dataelement101-6600
|
|
|
tijd
vl-dataelement101-6595
|
|
|
Id |
vl-dataelement101-6595 (2019‑05‑02 18:34:36)
|
Omschrijving |
tijd
|
Waardendomein |
Datum/tijd |
Eigenschap |
Tijdstempelprecisie |
tenminste dag, maand en jaar, uur en minuut |
|
Gebruikt door
|
2 transacties, 0 templates, één maal geërfd |
|
Dit concept wordt geërfd door concept
tijd in dataset vl-dataelement101-6601
|
|
|
moment
vl-dataelement101-6596
|
|
|
Id |
vl-dataelement101-6596 (2019‑05‑02 18:36:03)
|
Omschrijving |
moment, precies tot op minimaal seconden - typisch systeemgegenereerde tijd (in tegenstelling
tot tijden gebruikt in menselijke communicatie)
|
Waardendomein |
Datum/tijd |
Eigenschap |
Tijdstempelprecisie |
tenminste dag, maand en jaar, uur en minuut |
|
Gebruikt door
|
2 transacties, 0 templates, één maal geërfd |
|
Dit concept wordt geërfd door concept
moment in dataset vl-dataelement101-6602
|
|
|
integer
vl-dataelement101-6597
|
|
|
Id |
vl-dataelement101-6597 (2019‑05‑02 18:37:36)
|
Omschrijving |
integer
|
Waardendomein |
Aantal |
Gebruikt door
|
2 transacties, 0 templates, één maal geërfd |
|
Dit concept wordt geërfd door concept
integer in dataset vl-dataelement101-6603
|
|
|
decimaalGetal
vl-dataelement101-6598
|
|
|
Id |
vl-dataelement101-6598 (2019‑05‑02 18:38:00)
|
Omschrijving |
decimaal getal
|
Waardendomein |
Decimaal getal |
Gebruikt door
|
2 transacties, 0 templates, één maal geërfd |
|
Dit concept wordt geërfd door concept
decimaalGetal in dataset vl-dataelement101-6604
|
|
|
maxValue
vl-dataelement101-5566
|
|
|
Id |
vl-dataelement101-5566 (2019‑03‑29)
|
Omschrijving |
Must be <= this value
The inclusive upper bound on the range of allowed values for the data element.
|
Relatie |
|
Opmerking |
Data type specified must be the same as the data type for the data element. |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
datum
vl-dataelement101-6599
|
|
|
Id |
vl-dataelement101-6599 (2019‑05‑02 18:39:22)
|
Concept erft van |
vl-dataelement101-6593 (2019‑05‑02 18:33:31)
|
Omschrijving |
datum
|
Waardendomein |
Datum |
Eigenschap |
Tijdstempelprecisie |
tenminste dag, maand en jaar |
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
datumTijd
vl-dataelement101-6600
|
|
|
Id |
vl-dataelement101-6600 (2019‑05‑02 18:39:22)
|
Concept erft van |
vl-dataelement101-6594 (2019‑05‑02 18:34:04)
|
Omschrijving |
datumTijd
|
Waardendomein |
Datum/tijd |
Eigenschap |
Tijdstempelprecisie |
tenminste dag, maand en jaar, uur en minuut |
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
tijd
vl-dataelement101-6601
|
|
|
Id |
vl-dataelement101-6601 (2019‑05‑02 18:39:22)
|
Concept erft van |
vl-dataelement101-6595 (2019‑05‑02 18:34:36)
|
Omschrijving |
tijd
|
Waardendomein |
Datum/tijd |
Eigenschap |
Tijdstempelprecisie |
tenminste dag, maand en jaar, uur en minuut |
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
moment
vl-dataelement101-6602
|
|
|
Id |
vl-dataelement101-6602 (2019‑05‑02 18:39:22)
|
Concept erft van |
vl-dataelement101-6596 (2019‑05‑02 18:36:03)
|
Omschrijving |
moment, precies tot op minimaal seconden - typisch systeemgegenereerde tijd (in tegenstelling
tot tijden gebruikt in menselijke communicatie)
|
Waardendomein |
Datum/tijd |
Eigenschap |
Tijdstempelprecisie |
tenminste dag, maand en jaar, uur en minuut |
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
integer
vl-dataelement101-6603
|
|
|
|
|
decimaalGetal
vl-dataelement101-6604
|
|
|
|
|
maxDecimalPlaces
vl-dataelement101-5567
|
|
|
Id |
vl-dataelement101-5567 (2019‑03‑29)
|
Omschrijving |
Maximum digits after decimal
Identifies the maximum number of decimal places that may be specified for the data
element.
|
Waardendomein |
Aantal |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
mimeType
vl-dataelement101-5572
|
|
|
Id |
vl-dataelement101-5572 (2019‑03‑29)
|
Omschrijving |
Type of attachment
Identifies the kind(s) of attachment allowed to be sent for an element.
|
Opmerking |
This extension only has meaning if the element has a type of Attachment. |
Operationalisatie |
|
Waardendomein |
Code |
|
|
maxSize
vl-dataelement101-5577
|
|
|
Id |
vl-dataelement101-5577 (2019‑03‑29)
|
Omschrijving |
Max size in MB
For attachment answers, indicates the maximum size an attachment can be.
|
Opmerking |
This extension only has meaning if the element has a type of Attachment. |
Waardendomein |
Decimaal getal |
|
|
unit
vl-dataelement101-5582
|
|
|
Id |
vl-dataelement101-5582 (2019‑03‑29)
|
Omschrijving |
Unit for numeric answer
Provides a computable unit of measure associated with numeric questions to support
subsequent computation on responses.
|
Opmerking |
The human-readable unit is conveyed as a display element. This element is for computation
purposes.
|
Waardendomein |
Code |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
allowedResource
vl-dataelement101-5587
|
|
|
Id |
vl-dataelement101-5587 (2019‑03‑29)
|
Omschrijving |
Allowed resource for reference
Where the type for a question is "Reference", indicates a type of resource that is
permitted.
|
Opmerking |
This extension only has meaning if the question.type = Reference. If no allowedResource
extensions are present, the presumption is that any type of resource is permitted.
If multiple are present, then any of the specified types are permitted.
|
Waardendomein |
Code |
|
|
allowedProfile
vl-dataelement101-5592
|
|
|
Id |
vl-dataelement101-5592 (2019‑03‑29)
|
Omschrijving |
Allowed profile for reference
Where the type for a question is "Reference", indicates a profile that the resource
instances pointed to in answers to this question must be valid against.
|
Opmerking |
If multiple profiles are present, then the resource must be valid against at least
one of them.
|
|
|
verwijzing
vl-dataelement101-5595
|
|
|
Id |
vl-dataelement101-5595 (2019‑03‑29)
|
Omschrijving |
Exacte verwijzing, Relatieve, interne of absolute URL
|
Waardendomein |
String |
Gebruikt door
|
0 transacties, 0 templates, 3 maal geërfd |
|
Dit concept wordt geërfd door concept
verwijzing in dataset vl-dataelement101-5651.15
Dit concept wordt geërfd door concept
verwijzing in dataset vl-dataelement101-6614
Dit concept wordt geërfd door concept
verwijzing in dataset vl-dataelement101-5667.15
|
|
|
identificatie
vl-dataelement101-5596
|
|
|
Id |
vl-dataelement101-5596 (2019‑03‑29)
|
Omschrijving |
Logische referentie, als de exacte referentie niet bekend is.
|
Waardendomein |
Identificatie |
Gebruikt door
|
0 transacties, 0 templates, 3 maal geërfd |
|
Dit concept wordt geërfd door concept
identificatie in dataset vl-dataelement101-5651.16
Dit concept wordt geërfd door concept
identificatie in dataset vl-dataelement101-6615
Dit concept wordt geërfd door concept
identificatie in dataset vl-dataelement101-5667.16
|
|
|
weergaveTekst
vl-dataelement101-6605
|
|
|
Id |
vl-dataelement101-6605 (2019‑05‑02 18:52:02)
|
Omschrijving |
weergave tekst alternatief - leesbaar voor mensen
|
Waardendomein |
String |
Gebruikt door
|
0 transacties, 0 templates, 3 maal geërfd |
|
Dit concept wordt geërfd door concept
weergaveTekst in dataset vl-dataelement101-5651.17
Dit concept wordt geërfd door concept
weergaveTekst in dataset vl-dataelement101-6616
Dit concept wordt geërfd door concept
weergaveTekst in dataset vl-dataelement101-5667.17
|
|
|
referenceFilter
vl-dataelement101-5597
|
|
|
Id |
vl-dataelement101-5597 (2019‑03‑29)
|
Omschrijving |
Filter to apply when looking up references
Identifies a filter to apply when looking up candidate answers for the question.
|
Opmerking |
The filter may include $subj and/or $encounter which should be substituted by the
implementer with the subject and/or encounter id relevant in the context in which
the questionnaire is being populated.
|
Waardendomein |
String |
|
|
displayCategory
vl-dataelement101-5602
|
|
|
Id |
vl-dataelement101-5602 (2019‑03‑29)
|
Omschrijving |
Purpose of rendered text
Describes the intended purpose of the rendered text. For example - instructions, guidance
on access control, maintenance information, etc.
|
Operationalisatie |
|
Waardendomein |
Code |
Keuzelijst |
|
|
|
supportLink
vl-dataelement101-5607
|
|
|
Id |
vl-dataelement101-5607 (2019‑03‑29)
|
Omschrijving |
Supporting information
A URL that resolves to additional supporting information or guidance related to the
question.
|
Waardendomein |
String |
|
|
enableBehavior
vl-dataelement101-5971
|
|
|
Id |
vl-dataelement101-5971 (2019‑03‑29)
|
Omschrijving |
Optional Extensions Element
Determine if all or any of enableWhen need to be true
|
|
Waardendomein |
Code |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
linkId
vl-dataelement101-5613
|
|
|
Id |
vl-dataelement101-5613 (2019‑03‑29)
|
Omschrijving |
Unique id for item in questionnaire
An identifier that is unique within the Questionnaire allowing linkage to the equivalent
item in a QuestionnaireResponse resource.
|
Rationale |
[QuestionnaireResponse](questionnaireresponse.html#) does not require omitted items
to be included and may have some items that repeat, so linkage based on position alone
is not sufficient.
|
Opmerking |
This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to
have any meaning. GUIDs or sequential numbers are appropriate here.
|
Waardendomein |
String |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
definition
vl-dataelement101-5614
|
|
|
Id |
vl-dataelement101-5614 (2019‑03‑29)
|
Omschrijving |
ElementDefinition - details for the item
A reference to an [ElementDefinition](elementdefinition.html) that provides the details
for the item. If a definition is provided, then the following element values can be
inferred from the definition:
* code (ElementDefinition.code)
* type (ElementDefinition.type)
* required (ElementDefinition.min)
* repeats (ElementDefinition.max)
* maxLength (ElementDefinition.maxLength)
* options (ElementDefinition.binding)
Any information provided in these elements on a Questionnaire Item overrides the information
from the definition.
|
Rationale |
A common pattern is to define a set of data elements and then build multiple questionnaires
for different circumstances to gather the data. This element provides traceability
to the common definition and allows the content for the question to come from the
underlying definition.
|
Opmerking |
the URI refers to an ElementDefinition in either a [StructureDefinition](structuredefinition.html#)
or a [DataElement](dataelement.html#), and always starts with the canonical URL for
the target resource. When referring to a StructureDefinition, a fragment identifier
is used to specify the element definition by its id [Element.id](element-definitions.html#Element.id).
E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In
the absence of a fragment identifier, the first/root element definition in the target
is the
matching element definition. Note that [LOINC codes](loinc.html#dataelements) implicitly
define DataElement resources.
|
Waardendomein |
String |
|
|
code
vl-dataelement101-5615
|
|
|
Id |
vl-dataelement101-5615 (2019‑03‑29)
|
Omschrijving |
Corresponding concept for this item in a terminology
A terminology code that corresponds to this group or question (e.g. a code from LOINC,
which defines many questions and answers).
|
|
Rationale |
Allows linking of groups of questions to formal terminologies. |
Opmerking |
The value may come from the ElementDefinition referred to by .definition. |
Waardendomein |
Code |
Keuzelijst |
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
prefix
vl-dataelement101-5616
|
|
|
Id |
vl-dataelement101-5616 (2019‑03‑29)
|
Omschrijving |
E.g. "1(a)", "2.5.3"
A short label for a particular group, question or set of display text within the questionnaire
used for reference by the individual completing the questionnaire.
|
Rationale |
Separating the label from the question text allows improved rendering. Also, instructions
will often refer to specific prefixes, so there's a need for the questionnaire design
to have control over what labels are used.
|
Opmerking |
These are generally unique within a questionnaire, though this is not guaranteed.
Some questionnaires may have multiple questions with the same label with logic to
control which gets exposed. Typically these won't be used for "display" items, though
such use is not prohibited. Systems SHOULD NOT generate their own prefixes if prefixes
are defined for any items within a Questionnaire.
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
itemLabel-renderingStyle
vl-dataelement101-5619
|
|
|
Id |
vl-dataelement101-5619 (2019‑03‑29)
|
Omschrijving |
Html style value
Identifies how the specified element should be rendered when displayed.
|
Opmerking |
This extension would be equivalent to setting the HTML "style" attribute on the root
element for the element containing the extension.
|
Waardendomein |
String |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
itemLabel-xhtml
vl-dataelement101-5624
|
|
|
Id |
vl-dataelement101-5624 (2019‑03‑29)
|
Omschrijving |
String equivalent with html markup
This is an equivalent of the string on which the extension is sent, but includes additional
XHTML markup, such as bold, italics, styles, tables, etc. Existing [restrictions on
XHTML content](narrative.html#security) apply. Note that using [markdown](extension-rendering-markdown.html)
allows for greater flexibility of display.
|
Waardendomein |
String |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
value
vl-dataelement101-5629
|
|
|
Id |
vl-dataelement101-5629 (2019‑03‑29)
|
Omschrijving |
Primitive value for string
|
Waardendomein |
String |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
text
vl-dataelement101-5630
|
|
|
Id |
vl-dataelement101-5630 (2019‑03‑29)
|
Omschrijving |
Primary text for the item
The name of a section, the text of a question or text content for a display item.
|
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
groupText-renderingStyle
vl-dataelement101-5633
|
|
|
Id |
vl-dataelement101-5633 (2019‑03‑29)
|
Omschrijving |
Html style value
Identifies how the specified element should be rendered when displayed.
|
Opmerking |
This extension would be equivalent to setting the HTML "style" attribute on the root
element for the element containing the extension.
|
Waardendomein |
String |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
groupText-xhtml
vl-dataelement101-5638
|
|
|
Id |
vl-dataelement101-5638 (2019‑03‑29)
|
Omschrijving |
String equivalent with html markup
This is an equivalent of the string on which the extension is sent, but includes additional
XHTML markup, such as bold, italics, styles, tables, etc. Existing [restrictions on
XHTML content](narrative.html#security) apply. Note that using [markdown](extension-rendering-markdown.html)
allows for greater flexibility of display.
|
Waardendomein |
String |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
value
vl-dataelement101-5643
|
|
|
Id |
vl-dataelement101-5643 (2019‑03‑29)
|
Omschrijving |
Primitive value for string
|
Waardendomein |
String |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
type
vl-dataelement101-5644
|
|
|
Id |
vl-dataelement101-5644 (2019‑03‑29)
|
Omschrijving |
group | display | boolean | decimal | integer | date | dateTime +
The type of questionnaire item this is - whether text for display, a grouping of other
items or a particular type of data to be captured (string, integer, coded choice,
etc.).
|
Rationale |
Defines the format in which the user is to be prompted for the answer. |
Opmerking |
Time is handled using "string". File is handled using Attachment. (Content can be
sent as a contained binary).
|
Operationalisatie |
|
Waardendomein |
Code |
Keuzelijst |
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
enableWhen
vl-dataelement101-5645
|
|
|
Id |
vl-dataelement101-5645 (2019‑03‑29)
|
Omschrijving |
Only allow data when
A constraint indicating that this item should only be enabled (displayed/allow answers
to be captured) when the specified condition is true.
|
isSummary |
true |
isModifier |
true |
|
Rationale |
Allows questionnaires to adapt based on answers to other questions. E.g. If physical
gender is specified as a male, no need to capture pregnancy history. Also allows
conditional display of instructions or groups of questions.
|
Opmerking |
If multiple repetitions of this extension are present, the item should be enabled
when the condition for *any* of the repetitions is true. I.e. treat "enableWhen"s
as being joined by an "or" clause. This element is a modifier because if enableWhen
is present for an item, "required" is ignored unless one of the enableWhen conditions
is met.
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
enableOperator
vl-dataelement101-6008
|
|
|
Id |
vl-dataelement101-6008 (2019‑03‑29)
|
Omschrijving |
Optional Extensions Element
Specifies the criteria by which the question is enabled.
|
|
Waardendomein |
Code |
Keuzelijst |
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
question
vl-dataelement101-5649
|
|
|
Id |
vl-dataelement101-5649 (2019‑03‑29)
|
Omschrijving |
Question that determines whether item is enabled
The linkId for the question whose answer (or lack of answer) governs whether this
item is enabled.
|
Opmerking |
If multiple question occurrences are present for the same question (same linkId),
then this refers to the nearest question occurrence reachable by tracing first the
"ancestor" axis and then the "preceding" axis and then the "following" axis.
|
Waardendomein |
Identificatie |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
hasAnswer
vl-dataelement101-5650
|
|
|
Id |
vl-dataelement101-5650 (2019‑03‑29)
|
Omschrijving |
Enable when answered or not
An indication that this item should be enabled only if the specified question is answered
(hasAnswer=true) or not answered (hasAnswer=false).
|
Opmerking |
If answered=false and answer values are also provided, then they are treated as "or".
I.e. "Enable if the question is unanswered or the answer is one of the specified values".
If answered=true and answers are present, one of the specified answers must be met.
(So there's little reason to specify answered=true if answers are present.).
|
Waardendomein |
Boolean |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
answer
vl-dataelement101-5651
|
|
|
Id |
vl-dataelement101-5651 (2019‑03‑29)
|
Omschrijving |
Value question must have
An answer that the referenced question must match in order for the item to be enabled.
|
Opmerking |
Multiple answers are treated as "or". E.g. Enable if question 1 = A, C or E. Components
not specified in the answer do not need to match. For example, if enableWhen specifies
code + system for a Coding, it is ok if the answer has a "display" element. I.e. treat
the answer as a 'pattern'. The dataType of this element must be the same as the data
type of the question being referenced.
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
answer boolean
vl-dataelement101-5651.1
|
|
|
|
|
answer decimal
vl-dataelement101-5651.2
|
|
|
|
|
answer integer
vl-dataelement101-5651.3
|
|
|
|
|
answer date
vl-dataelement101-5651.4
|
|
|
|
|
answer dateTime
vl-dataelement101-5651.5
|
|
|
|
|
answer time
vl-dataelement101-5651.6
|
|
|
|
|
answer string
vl-dataelement101-5651.7
|
|
|
|
|
answer uri
vl-dataelement101-5651.8
|
|
|
|
|
answer Attachment
vl-dataelement101-5651.9
|
|
|
|
|
answer Coding
vl-dataelement101-5651.10
|
|
|
|
|
answer Quantity
vl-dataelement101-5651.11
|
|
|
Id |
vl-dataelement101-5651.11 (2019‑03‑29)
|
Omschrijving |
- |
Waardendomein |
Hoeveelheid |
Voorbeeld |
bloedverlies bij bevalling 500 ml
|
Voorbeeld |
lengte 168 cm
|
Voorbeeld |
gewicht 70 kg
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
antwoordVerwijzing
vl-dataelement101-5651.12
|
|
|
Id |
vl-dataelement101-5651.12 (2019‑03‑29)
|
Omschrijving |
antwoord verwijzing
|
Relatie |
|
Opmerking |
If multiple profiles are present, then the resource must be valid against at least
one of them.
|
|
|
verwijzing
vl-dataelement101-5651.15
|
|
|
|
|
identificatie
vl-dataelement101-5651.16
|
|
|
|
|
weergaveTekst
vl-dataelement101-5651.17
|
|
|
|
|
required
vl-dataelement101-5652
|
|
|
Id |
vl-dataelement101-5652 (2019‑03‑29)
|
Omschrijving |
Whether the item must be included in data results
An indication, if true, that the item must be present in a "completed" QuestionnaireResponse.
If false, the item may be skipped when answering the questionnaire.
|
Opmerking |
Questionnaire.item.required only has meaning for elements that are conditionally enabled
with enableWhen if the condition evaluates to true. If an item that contains other
items is marked as required, that does not automatically make the contained elements
required (though required groups must contain at least one child element). The value
may come from the ElementDefinition referred to by .definition.
|
Waardendomein |
Boolean |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
repeats
vl-dataelement101-5653
|
|
|
Id |
vl-dataelement101-5653 (2019‑03‑29)
|
Omschrijving |
Whether the item may repeat
An indication, if true, that the item may occur multiple times in the response, collecting
multiple answers answers for questions or multiple sets of answers for groups.
|
Rationale |
Items may be used to create set of (related) questions that can be repeated to give
multiple answers to such a set.
|
Opmerking |
If a question is marked as repeats=true, then multiple answers can be provided for
the question in the corresponding QuestionnaireResponse. When rendering the questionnaire,
it is up to the rendering software whether to render the question text for each answer
repetition or to simply list each of the answers beneath the question. (Which is most
appropriate visually may depend on the type of answer as well as whether there are
nested items.). The value may come from the ElementDefinition referred to by .definition.
|
Waardendomein |
Boolean |
|
|
readOnly
vl-dataelement101-5654
|
|
|
Id |
vl-dataelement101-5654 (2019‑03‑29)
|
Omschrijving |
Don't allow human editing
An indication, when true, that the value cannot be changed by a human respondent to
the Questionnaire.
|
Rationale |
Allows certain information to be phrased (and rendered) as a question and an answer,
while keeping users from changing it. May also be useful for preventing changes to
pre-populated portions of a questionnaire, for calculated values, etc.
|
Opmerking |
The value of readOnly elements can be established by asserting extensions for defaultValues,
linkages that support pre-population and/or extensions that support calculation based
on other answers.
|
Waardendomein |
Boolean |
|
|
maxLength
vl-dataelement101-5655
|
|
|
Id |
vl-dataelement101-5655 (2019‑03‑29)
|
Omschrijving |
No more than this many characters
The maximum number of characters that are permitted in the answer to be considered
a "valid" QuestionnaireResponse.
|
Opmerking |
For base64binary, reflects the number of characters representing the encoded data,
not the number of bytes of the binary data. The value may come from the ElementDefinition
referred to by .definition.
|
Waardendomein |
Aantal |
|
|
options
vl-dataelement101-5656
|
|
|
Id |
vl-dataelement101-5656 (2019‑03‑29)
|
Omschrijving |
Valueset containing permitted answers A reference to a value set containing a list of codes representing permitted answers
for a "choice" or "open-choice" question.
|
Relatie |
|
Opmerking |
LOINC defines many useful value sets for questionnaire responses. See [LOINC Answer
Lists](loinc.html#alist). The value may come from the ElementDefinition referred to
by .definition.
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
verwijzing
vl-dataelement101-6614
|
|
|
|
|
identificatie
vl-dataelement101-6615
|
|
|
|
|
weergaveTekst
vl-dataelement101-6616
|
|
|
|
|
option
vl-dataelement101-5657
|
|
|
Id |
vl-dataelement101-5657 (2019‑03‑29)
|
Omschrijving |
Permitted answer
One of the permitted answers for a "choice" or "open-choice" question.
|
Opmerking |
This element can be used when the value set machinery of options is deemed too cumbersome
or when there's a need to capture options that are not codes.
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
value
vl-dataelement101-5666
|
|
|
Id |
vl-dataelement101-5666 (2019‑03‑29)
|
Omschrijving |
Answer value
A potential answer that's allowed as the answer to this question.
|
Opmerking |
The data type of the value must agree with the item.type. |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
value Coding
vl-dataelement101-5666.5
|
|
|
Id |
vl-dataelement101-5666.5 (2019‑03‑29)
|
Omschrijving |
- |
Waardendomein |
Code |
Keuzelijst |
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
initial
vl-dataelement101-5667
|
|
|
Id |
vl-dataelement101-5667 (2019‑03‑29)
|
Omschrijving |
Default value when item is first rendered
The value that should be defaulted when initially rendering the questionnaire for
user input.
|
Rationale |
In some workflows, having defaults saves time. |
Opmerking |
The user is allowed to change the value and override the default (unless marked as
read-only). If the user doesn't change the value, then this initial value will be
persisted when the QuestionnaireResponse is initially created. Note that default values
can influence results. The data type of initial[x] must agree with the item.type.
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
initial boolean
vl-dataelement101-5667.1
|
|
|
|
|
initial decimal
vl-dataelement101-5667.2
|
|
|
|
|
initial integer
vl-dataelement101-5667.3
|
|
|
|
|
initial date
vl-dataelement101-5667.4
|
|
|
|
|
initial dateTime
vl-dataelement101-5667.5
|
|
|
|
|
initial time
vl-dataelement101-5667.6
|
|
|
|
|
initial string
vl-dataelement101-5667.7
|
|
|
|
|
initial uri
vl-dataelement101-5667.8
|
|
|
|
|
initial Attachment
vl-dataelement101-5667.9
|
|
|
|
|
initial Coding
vl-dataelement101-5667.10
|
|
|
|
|
initial Quantity
vl-dataelement101-5667.11
|
|
|
|
|
verwijzing
vl-dataelement101-5667.12
|
|
|
Id |
vl-dataelement101-5667.12 (2019‑03‑29)
|
Omschrijving |
Verwijzing
|
Relatie |
|
Opmerking |
If multiple profiles are present, then the resource must be valid against at least
one of them.
|
|
|
verwijzing
vl-dataelement101-5667.15
|
|
|
|
|
identificatie
vl-dataelement101-5667.16
|
|
|
|
|
weergaveTekst
vl-dataelement101-5667.17
|
|
|
|
|
QuestionnaireItem
vl-dataelement101-7935
|
|
|
Id |
vl-dataelement101-7935 (2020‑02‑03 17:44:10)
|
Concept verwijst naar |
vl-dataelement101-5512 (2019‑03‑29)
|
Omschrijving |
Questions and sections within the Questionnaire
A particular question, question grouping or display text that is part of the questionnaire.
|
Opmerking |
The content of the questionnaire is constructed from an ordered, hierarchical collection
of items.
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
QuestionnaireResponse
vl-dataelement101-5669
|
|
|
Id |
vl-dataelement101-5669 (2019‑03‑29)
|
Omschrijving |
A structured set of questions and their answers
Sets expectations for supported capabilities for questionnaire responses for the Netherlands
SDC-conformant systems.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
identifier
vl-dataelement101-5678
|
|
|
Id |
vl-dataelement101-5678 (2019‑03‑29)
|
Omschrijving |
Unique id for this set of answers
A business identifier assigned to a particular completed (or partially completed)
questionnaire.
|
|
Rationale |
Used for tracking, registration and other business purposes. |
Waardendomein |
Identificatie |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
basedOn
vl-dataelement101-5679
|
|
|
Id |
vl-dataelement101-5679 (2019‑03‑29)
|
Omschrijving |
Request fulfilled by this QuestionnaireResponse
The order, proposal or plan that is fulfilled in whole or in part by this QuestionnaireResponse.
For example, a ProcedureRequest seeking an intake assessment or a decision support
recommendation to assess for post-partum depression.
|
|
Rationale |
Supports traceability of responsibility for the action and allows linkage of an action
to the recommendations acted upon.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
basedOn Reference (ReferralRequest)
vl-dataelement101-5679.1
|
|
|
|
|
basedOn Reference (CarePlan)
vl-dataelement101-5679.2
|
|
|
|
|
basedOn Reference (ProcedureRequest)
vl-dataelement101-5679.3
|
|
|
|
|
parent
vl-dataelement101-5680
|
|
|
Id |
vl-dataelement101-5680 (2019‑03‑29)
|
Omschrijving |
Part of this action
A procedure or observation that this questionnaire was performed as part of the execution
of. For example, the surgery a checklist was executed as part of.
|
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
parent Reference (Observation)
vl-dataelement101-5680.1
|
|
|
|
|
parent Reference (Procedure)
vl-dataelement101-5680.2
|
|
|
|
|
questionnaire
vl-dataelement101-5681
|
|
|
Id |
vl-dataelement101-5681 (2019‑03‑29)
|
Omschrijving |
Verwijzing naar vragenlijst
|
Relatie |
|
Opmerking |
If multiple profiles are present, then the resource must be valid against at least
one of them.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Questionnaire
vl-dataelement101-7933
|
|
|
Id |
vl-dataelement101-7933 (2020‑02‑03 12:19:23)
|
Concept verwijst naar |
vl-dataelement101-5296 (2019‑03‑29)
|
Omschrijving |
A structured set of questions
Sets minimum expectations for questionnaire support for the Netherlands SDC-conformant
systems, including a number of extensions around display and behavior.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
status
vl-dataelement101-5682
|
|
|
Id |
vl-dataelement101-5682 (2019‑03‑29)
|
Omschrijving |
in-progress | completed | amended | entered-in-error | stopped
The position of the questionnaire response within its overall lifecycle.
|
isSummary |
true |
isModifier |
true |
|
Rationale |
The information on Questionnaire resources may possibly be gathered during multiple
sessions and altered after considered being finished.
|
Waardendomein |
Code |
Keuzelijst |
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
subject
vl-dataelement101-5683
|
|
|
Id |
vl-dataelement101-5683 (2019‑03‑29)
|
Omschrijving |
The subject of the questions
The subject of the questionnaire response. This could be a patient, organization,
practitioner, device, etc. This is who/what the answers apply to, but is not necessarily
the source of information.
|
|
Rationale |
Allows linking the answers to the individual the answers describe. May also affect
access control.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Patient
vl-dataelement101-7952
|
|
|
Id |
vl-dataelement101-7952 (2020‑02‑03 22:09:12)
|
Concept verwijst naar |
vl-dataelement101-7360 (2020‑02‑02 22:40:38)
|
Omschrijving |
Rootconcept van de bouwsteen Patiënt. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Patiënt.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Zorgverlener
vl-dataelement101-7954
|
|
|
Id |
vl-dataelement101-7954 (2020‑02‑03 22:11:59)
|
Concept verwijst naar |
vl-dataelement101-7335 (2020‑02‑02 22:32:48)
|
Omschrijving |
Rootconcept van de bouwsteen Zorgverlener. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Zorgverlener. Bij verwijzing naar deze bouwsteen kan tevens de rol die de zorgverlener in het zorgproces
vervult, worden meegegeven. Voor zorgverleners kan dit bijvoorbeeld hoofdbehandelaar
of verwijzer zijn
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Zorgaanbieder
vl-dataelement101-7953
|
|
|
Id |
vl-dataelement101-7953 (2020‑02‑03 22:10:11)
|
Concept verwijst naar |
vl-dataelement101-7299 (2020‑02‑02 22:24:44)
|
Omschrijving |
Rootconcept van de bouwsteen Zorgaanbieder. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Zorgaanbieder.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Betaler
vl-dataelement101-7955
|
|
|
Id |
vl-dataelement101-7955 (2020‑02‑03 22:13:37)
|
Concept verwijst naar |
vl-dataelement101-6620 (2019‑05‑05 17:06:22)
|
Omschrijving |
Rootconcept van de bouwsteen Betaler. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Betaler.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
MedischHulpmiddel
vl-dataelement101-7956
|
|
|
Id |
vl-dataelement101-7956 (2020‑02‑03 22:15:37)
|
Concept verwijst naar |
vl-dataelement101-5683.4 (2019‑03‑29)
|
Omschrijving |
Rootconcept van de bouwsteen MedischHulpmiddel. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen MedischHulpmiddel.
|
Terminologiekoppeling |
Dit concept wordt uitgedrukt door code "49062001" (Device (physical object)) uit codesysteem 2.16.840.1.113883.6.96
SNOMED CT)
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
context
vl-dataelement101-5684
|
|
|
Id |
vl-dataelement101-5684 (2019‑03‑29)
|
Omschrijving |
Encounter or Episode during which questionnaire was completed
The encounter or episode of care with primary association to the questionnaire response.
|
|
Rationale |
Provides context for the information that was captured. May also affect access control. |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
context Reference (Encounter)
vl-dataelement101-5684.1
|
|
|
|
|
context Reference (EpisodeOfCare)
vl-dataelement101-5684.2
|
|
|
|
|
authored
vl-dataelement101-5685
|
|
|
Id |
vl-dataelement101-5685 (2019‑03‑29)
|
Omschrijving |
Date the answers were gathered
Identifies when this version of the answer set was created. Changes whenever the answers
are updated.
|
|
Rationale |
Clinicians need to be able to check the date that the information in the questionnaire
was collected, to derive the context of the answers.
|
Waardendomein |
Datum/tijd |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
author
vl-dataelement101-5686
|
|
|
Id |
vl-dataelement101-5686 (2019‑03‑29)
|
Omschrijving |
Person who received and recorded the answers
Person who received the answers to the questions in the QuestionnaireResponse and
recorded them in the system.
|
|
Rationale |
Need to know who interpreted the subject's answers to the questions in the questionnaire,
and selected the appropriate options for answers.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Patient
vl-dataelement101-7347
|
|
|
Id |
vl-dataelement101-7347 (2020‑02‑02 22:34:56)
|
Concept verwijst naar |
vl-dataelement101-7360 (2020‑02‑02 22:40:38)
|
Omschrijving |
Rootconcept van de bouwsteen Patiënt. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Patiënt.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
source
vl-dataelement101-5687
|
|
|
Id |
vl-dataelement101-5687 (2019‑03‑29)
|
Omschrijving |
The person who answered the questions
The person who answered the questions about the subject.
|
|
Rationale |
When answering questions about a subject that is minor, incapable of answering or
an animal, another human source may answer the questions.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Patient
vl-dataelement101-7322
|
|
|
Id |
vl-dataelement101-7322 (2020‑02‑02 22:32:00)
|
Concept verwijst naar |
vl-dataelement101-7360 (2020‑02‑02 22:40:38)
|
Omschrijving |
Rootconcept van de bouwsteen Patiënt. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Patiënt.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Zorgverlener
vl-dataelement101-7936
|
|
|
Id |
vl-dataelement101-7936 (2020‑02‑03 18:01:03)
|
Concept verwijst naar |
NL-CM-17.1.1 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de bouwsteen Zorgverlener. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Zorgverlener. Bij verwijzing naar deze bouwsteen kan tevens de rol die de zorgverlener in het zorgproces
vervult, worden meegegeven. Voor zorgverleners kan dit bijvoorbeeld hoofdbehandelaar
of verwijzer zijn
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
QuestionnaireResponseItem
vl-dataelement101-7948
|
|
|
Id |
vl-dataelement101-7948 (2020‑02‑03 18:11:51)
|
Concept verwijst naar |
vl-dataelement101-5688 (2019‑03‑29)
|
Omschrijving |
Groups and questions
A group or question item from the original questionnaire for which answers are provided.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
QuestionnaireResponseItem
vl-dataelement101-5688
|
|
|
Id |
vl-dataelement101-5688 (2019‑03‑29)
|
Omschrijving |
Groups and questions
A group or question item from the original questionnaire for which answers are provided.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
linkId
vl-dataelement101-5692
|
|
|
Id |
vl-dataelement101-5692 (2019‑03‑29)
|
Omschrijving |
Pointer to specific item from Questionnaire
The item from the Questionnaire that corresponds to this item in the QuestionnaireResponse
resource.
|
Rationale |
Items can repeat in the answers, so a direct 1..1 correspondence by position may not
exist - requiring correspondence by identifier.
|
Waardendomein |
String |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
definition
vl-dataelement101-5693
|
|
|
Id |
vl-dataelement101-5693 (2019‑03‑29)
|
Omschrijving |
ElementDefinition - details for the item
A reference to an [ElementDefinition](elementdefinition.html) that provides the details
for the item.
|
Rationale |
A common pattern is to define a set of data elements, and then build multiple different
questionnaires for different circumstances to gather the data. This element provides
traceability to the common definition.
|
Waardendomein |
String |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
text
vl-dataelement101-5694
|
|
|
Id |
vl-dataelement101-5694 (2019‑03‑29)
|
Omschrijving |
Name for group or question text
Text that is displayed above the contents of the group or as the text of the question
being answered.
|
Rationale |
Allows the questionnaire response to be read without access to the questionnaire. |
Waardendomein |
String |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
subject
vl-dataelement101-5695
|
|
|
Id |
vl-dataelement101-5695 (2019‑03‑29)
|
Omschrijving |
Patient for this answer/group of answers
Identifies the patient this particular group or question is describing if different
from the patient for the overall response.
|
Rationale |
Non-patient questionnaires are outside the scope. |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Patient
vl-dataelement101-8061
|
|
|
Id |
vl-dataelement101-8061 (2020‑02‑04 00:21:07)
|
Concept verwijst naar |
vl-dataelement101-7360 (2020‑02‑02 22:40:38)
|
Omschrijving |
Rootconcept van de bouwsteen Patiënt. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Patiënt.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
answer
vl-dataelement101-5696
|
|
|
Id |
vl-dataelement101-5696 (2019‑03‑29)
|
Omschrijving |
The response(s) to the question
The respondent's answer(s) to the question.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
value
vl-dataelement101-5700
|
|
|
Id |
vl-dataelement101-5700 (2019‑03‑29)
|
Omschrijving |
Single-valued answer to the question
The answer (or one of the answers) provided by the respondent to the question.
|
Rationale |
Ability to retain a single-valued answer to a question. |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
value boolean
vl-dataelement101-5700.1
|
|
|
|
|
value date
vl-dataelement101-5700.2
|
|
|
|
|
value dateTime
vl-dataelement101-5700.3
|
|
|
|
|
value time
vl-dataelement101-5700.4
|
|
|
|
|
value decimal
vl-dataelement101-5700.5
|
|
|
|
|
value integer
vl-dataelement101-5700.6
|
|
|
|
|
value string
vl-dataelement101-5700.7
|
|
|
|
|
value Coding
vl-dataelement101-5700.8
|
|
|
Id |
vl-dataelement101-5700.8 (2019‑03‑29)
|
Omschrijving |
- |
Waardendomein |
Code |
Keuzelijst |
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
value uri
vl-dataelement101-5700.9
|
|
|
|
|
value Quantity
vl-dataelement101-5700.10
|
|
|
|
|
value Attachment
vl-dataelement101-5700.11
|
|
|
|
|
value Reference
vl-dataelement101-5700.12
|
|
|
|
|
QuestionnaireResponseItem
vl-dataelement101-5701
|
|
|
Id |
vl-dataelement101-5701 (2019‑03‑29)
|
Concept verwijst naar |
vl-dataelement101-5688 (2019‑03‑29)
|
Omschrijving |
Groups and questions
A group or question item from the original questionnaire for which answers are provided.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
QuestionnaireResponseItem
vl-dataelement101-5702
|
|
|
Id |
vl-dataelement101-5702 (2019‑03‑29)
|
Concept verwijst naar |
vl-dataelement101-5688 (2019‑03‑29)
|
Omschrijving |
Groups and questions
A group or question item from the original questionnaire for which answers are provided.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
QuestionnaireProvisioningTask
vl-dataelement101-5703
|
|
|
Id |
vl-dataelement101-5703 (2019‑03‑29)
|
Omschrijving |
A task to be performed.
|
Terminologiekoppeling |
Dit concept wordt uitgedrukt door code "74468-0" (Questionnaire form definition Document) uit codesysteem 2.16.840.1.113883.6.1
LOINC)
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
identifier
vl-dataelement101-5712
|
|
|
|
|
status
vl-dataelement101-5717
|
|
|
Id |
vl-dataelement101-5717 (2019‑03‑29)
|
Omschrijving |
Short description
draft | requested | received | accepted | +
Definition
The current status of the task:
- initially: requested
- when the PHR system has retrieved the Questionnaire resource and is able to present
it to the user: accepted
- when the PHR system has retrieved the Questionnaire resource and is unable to present
it to the user: rejected
- when the PHR system completes the task by attaching a QuestionnaireResponse resource
to Task.output:QuestionnaireResponse: completed
- when the PHR system is unable to complete the assigned task: failed
Requirements
These states enable coordination of task status with off-the-shelf workflow solutions
that support automation of tasks.
Comments
Note that FHIR strings may not exceed 1MB in size
|
|
Rationale |
These states enable coordination of task status with off-the-shelf workflow solutions
that support automation of tasks.
|
Waardendomein |
Code |
Keuzelijst |
Conceptenlijst |
|
Waardelijst required TaskStatus (versie DYNAMISCH)
|
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
statusReason
vl-dataelement101-8621
|
|
|
Id |
vl-dataelement101-8621 (2020‑04‑02 10:37:16)
|
Omschrijving |
Short description
Reason for current status
Definition
An explanation as to why this task is held, failed, was refused, etc.
Comments
This applies to the current status. Look at the history of the task to see reasons
for past statuses.
|
Waardendomein |
Code |
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
description
vl-dataelement101-5734
|
|
|
Id |
vl-dataelement101-5734 (2019‑03‑29)
|
Omschrijving |
Human-readable explanation of task
A free-text description of what is to be performed.
|
|
Waardendomein |
String |
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
for
vl-dataelement101-7285
|
|
|
|
|
Patient
vl-dataelement101-7286
|
|
|
Id |
vl-dataelement101-7286 (2020‑02‑02 22:23:10)
|
Concept verwijst naar |
vl-dataelement101-7360 (2020‑02‑02 22:40:38)
|
Omschrijving |
Rootconcept van de bouwsteen Patiënt. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Patiënt.
|
|
|
authoredOn
vl-dataelement101-5739
|
|
|
Id |
vl-dataelement101-5739 (2019‑03‑29)
|
Omschrijving |
Task Creation Date
The date and time this task was created.
|
Rationale |
Most often used along with lastUpdated to track duration of task to supporting monitoring
and management.
|
Waardendomein |
Datum/tijd |
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
lastModified
vl-dataelement101-5740
|
|
|
Id |
vl-dataelement101-5740 (2019‑03‑29)
|
Omschrijving |
Task Last Modified Date
The date and time of last modification to this task.
|
|
Rationale |
Used along with history to track task activity and time in a particular task state.
This enables monitoring and management.
|
Waardendomein |
Datum/tijd |
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
requester
vl-dataelement101-5741
|
|
|
Id |
vl-dataelement101-5741 (2019‑03‑29)
|
Omschrijving |
Degene die vraagt om uitvoering van de taak
Degene die de taak heeft gemaakt.
|
|
Rationale |
Identifies who created this task. May be used by access control mechanisms (e.g.,
to ensure that only the creator can cancel a task).
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Zorgverlener
vl-dataelement101-7261
|
|
|
Id |
vl-dataelement101-7261 (2020‑02‑02 22:08:07)
|
Concept verwijst naar |
vl-dataelement101-7335 (2020‑02‑02 22:32:48)
|
Omschrijving |
Rootconcept van de bouwsteen Zorgverlener. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Zorgverlener. Bij verwijzing naar deze bouwsteen kan tevens de rol die de zorgverlener in het zorgproces
vervult, worden meegegeven. Voor zorgverleners kan dit bijvoorbeeld hoofdbehandelaar
of verwijzer zijn
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Zorgaanbieder
vl-dataelement101-7950
|
|
|
Id |
vl-dataelement101-7950 (2020‑02‑03 22:03:42)
|
Concept verwijst naar |
vl-dataelement101-7299 (2020‑02‑02 22:24:44)
|
Omschrijving |
Rootconcept van de bouwsteen Zorgaanbieder. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Zorgaanbieder.
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
owner
vl-dataelement101-8622
|
|
|
Id |
vl-dataelement101-8622 (2020‑04‑02 11:26:54)
|
Omschrijving |
Short description
Responsible individual
Alternate names
Performer, Executer
Definition
Individual organization or Device currently responsible for task execution. This will
most likely be the patient in MedMij context.
Requirements
Identifies who is expected to perform this task.
Comments
Tasks may be created with an owner not yet identified.
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Patient
vl-dataelement101-8887
|
|
|
Id |
vl-dataelement101-8887 (2020‑04‑02 22:13:32)
|
Concept verwijst naar |
NL-CM-0.1.1 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de bouwsteen Patiënt. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Patiënt.
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
restriction
vl-dataelement101-5752
|
|
|
Id |
vl-dataelement101-5752 (2019‑03‑29)
|
Omschrijving |
Constraints on fulfillment tasks
If the Task.focus is a request resource and the task is seeking fulfillment (i.e is
asking for the request to be actioned), this element identifies any limitations on
what parts of the referenced request should be actioned.
|
Rationale |
Sometimes when fulfillment is sought, you don't want full fulfillment. |
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
repetitions
vl-dataelement101-5756
|
|
|
Id |
vl-dataelement101-5756 (2019‑03‑29)
|
Omschrijving |
How many times to repeat
Indicates the number of times the requested action should occur.
|
Rationale |
E.g. order that requests monthly lab tests, fulfillment is sought for 1. |
Waardendomein |
Aantal |
Eigenschap |
|
|
|
period
vl-dataelement101-5757
|
|
|
Id |
vl-dataelement101-5757 (2019‑03‑29)
|
Omschrijving |
When fulfillment sought
Over what time-period is fulfillment sought.
|
Relatie |
Specialisatie NL-CM-20.3.1 - 2017‑12‑31
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
startDatumTijd
vl-dataelement101-5811
|
|
|
Id |
vl-dataelement101-5811 (2019‑04‑11 15:37:11)
|
Concept erft van |
NL-CM-20.3.2 (2017‑12‑31)
|
Omschrijving |
De begindatum en tijd van het interval |
Waardendomein |
Datum/tijd |
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
eindDatumTijd
vl-dataelement101-5812
|
|
|
Id |
vl-dataelement101-5812 (2019‑04‑11 15:37:11)
|
Concept erft van |
NL-CM-20.3.3 (2017‑12‑31)
|
Omschrijving |
De einddatum en tijd van het interval |
Waardendomein |
Datum/tijd |
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
recipient
vl-dataelement101-5758
|
|
|
Id |
vl-dataelement101-5758 (2019‑03‑29)
|
Omschrijving |
For whom is fulfillment sought?
For requests that are targeted to more than on potential recipient/target, for whom
is fulfillment sought?
|
|
|
Patient
vl-dataelement101-7951
|
|
|
Id |
vl-dataelement101-7951 (2020‑02‑03 22:04:56)
|
Concept verwijst naar |
vl-dataelement101-7360 (2020‑02‑02 22:40:38)
|
Omschrijving |
Rootconcept van de bouwsteen Patiënt. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Patiënt.
|
|
|
Zorgverlener
vl-dataelement101-7958
|
|
|
Id |
vl-dataelement101-7958 (2020‑02‑03 22:22:50)
|
Concept verwijst naar |
vl-dataelement101-7335 (2020‑02‑02 22:32:48)
|
Omschrijving |
Rootconcept van de bouwsteen Zorgverlener. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Zorgverlener. Bij verwijzing naar deze bouwsteen kan tevens de rol die de zorgverlener in het zorgproces
vervult, worden meegegeven. Voor zorgverleners kan dit bijvoorbeeld hoofdbehandelaar
of verwijzer zijn
|
|
|
Zorgaanbieder
vl-dataelement101-7959
|
|
|
Id |
vl-dataelement101-7959 (2020‑02‑03 22:23:30)
|
Concept verwijst naar |
vl-dataelement101-7299 (2020‑02‑02 22:24:44)
|
Omschrijving |
Rootconcept van de bouwsteen Zorgaanbieder. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Zorgaanbieder.
|
|
|
Contactpersoon
vl-dataelement101-8000
|
|
|
Id |
vl-dataelement101-8000 (2020‑02‑03 22:31:19)
|
Concept verwijst naar |
vl-dataelement101-7991 (2020‑02‑03 22:30:06)
|
Omschrijving |
Rootconcept van de bouwsteen Contactpersoon. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Contactpersoon.
|
|
|
input
vl-dataelement101-8074
|
|
|
Id |
vl-dataelement101-8074 (2020‑03‑04 21:03:52)
|
Omschrijving |
Information used to perform task
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Subject
vl-dataelement101-8883
|
|
|
|
|
Patient
vl-dataelement101-8886
|
|
|
Id |
vl-dataelement101-8886 (2020‑04‑02 22:12:11)
|
Concept verwijst naar |
NL-CM-0.1.1 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de bouwsteen Patiënt. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Patiënt.
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Zorgverlener
vl-dataelement101-8885
|
|
|
Id |
vl-dataelement101-8885 (2020‑04‑02 22:10:24)
|
Concept verwijst naar |
vl-dataelement101-7335 (2020‑02‑02 22:32:48)
|
Omschrijving |
Rootconcept van de bouwsteen Zorgverlener. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Zorgverlener. Bij verwijzing naar deze bouwsteen kan tevens de rol die de zorgverlener in het zorgproces
vervult, worden meegegeven. Voor zorgverleners kan dit bijvoorbeeld hoofdbehandelaar
of verwijzer zijn
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Zorgaanbieder
vl-dataelement101-8884
|
|
|
Id |
vl-dataelement101-8884 (2020‑04‑02 22:09:23)
|
Concept verwijst naar |
vl-dataelement101-7299 (2020‑02‑02 22:24:44)
|
Omschrijving |
Rootconcept van de bouwsteen Zorgaanbieder. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Zorgaanbieder.
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Questionnaire
vl-dataelement101-8077
|
|
|
Id |
vl-dataelement101-8077 (2020‑03‑04 21:09:31)
|
Concept verwijst naar |
vl-dataelement101-5296 (2019‑03‑29)
|
Omschrijving |
A structured set of questions
Sets minimum expectations for questionnaire support for the Netherlands SDC-conformant
systems, including a number of extensions around display and behavior.
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
output
vl-dataelement101-8075
|
|
|
Id |
vl-dataelement101-8075 (2020‑03‑04 21:05:18)
|
Omschrijving |
Information produced as part of task
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
QuestionnaireResponse
vl-dataelement101-8076
|
|
|
Id |
vl-dataelement101-8076 (2020‑03‑04 21:07:41)
|
Concept verwijst naar |
vl-dataelement101-5669 (2019‑03‑29)
|
Omschrijving |
A structured set of questions and their answers
Sets expectations for supported capabilities for questionnaire responses for the Netherlands
SDC-conformant systems.
|
Gebruikt door
|
3 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Bouwstenen
vl-dataelement101-7949
|
|
|
|
|
Zorgverlener
vl-dataelement101-7335
|
|
|
Id |
vl-dataelement101-7335 (2020‑02‑02 22:32:48)
|
Concept erft van |
NL-CM-17.1.1 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de bouwsteen Zorgverlener. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Zorgverlener. Bij verwijzing naar deze bouwsteen kan tevens de rol die de zorgverlener in het zorgproces
vervult, worden meegegeven. Voor zorgverleners kan dit bijvoorbeeld hoofdbehandelaar
of verwijzer zijn
|
Gebruikt door
|
5 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
ZorgverlenerIdentificatienummer
vl-dataelement101-8014
|
|
|
Id |
vl-dataelement101-8014 (2020‑02‑03 22:49:05)
|
Concept erft van |
NL-CM-17.1.2 (2017‑12‑31)
|
Omschrijving |
Het zorgverleneridentificatienummer is een nummer dat de zorgverlener uniek identificeert.
In de Nederlandse situatie worden de volgende nummers gebruikt: 1. Zorgverlener UZI. Identificatie van zorgverleners (natuurlijke personen) in de
Nederlandse zorgsector. 2. VEKTIS AGB-Z. Dient ter identificatie van zorgverleners en zorgverlenende organisaties 3. BIG-ID. Het ID van de in het BIG Register opgenomen zorgverlener.
Voor buitenlandse zorgverleners zijn deze gegevens niet voorhanden.
|
Operationalisatie |
- BIG register inschrijvingsnummer (OID: 2.16.528.1.1007.5.1)
- UZI nummer natuurlijke personen (OID: 2.16.528.1.1007.3.1)
- Vektis AGB-zorgverlener tabel (OID: 2.16.840.1.113883.2.4.6.1)
|
Waardendomein |
Identificatie |
Voorbeeld |
21870932 |
Gebruikt door
|
5 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Naamgegevens
vl-dataelement101-8015
|
|
|
Id |
vl-dataelement101-8015 (2020‑02‑03 22:49:05)
|
Concept erft van |
NL-CM-17.1.3 (2017‑12‑31)
|
Omschrijving |
De naamgegevens van de zorgverlener. Indien een zorgverleneridentificatienummer wordt
opgegeven, is dit de naam zoals vermeld in UZI, AGB of in de instelling.
|
Gebruikt door
|
5 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Naamgegevens
vl-dataelement101-8016
|
|
|
Id |
vl-dataelement101-8016 (2020‑02‑03 22:49:05)
|
Concept erft van |
NL-CM-2017-235 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de subbouwsteen Naamgegevens. Dit rootconcept bevat alle gegevenselementen
van de subbouwsteen Naamgegevens.
|
Gebruikt door
|
5 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Specialisme
vl-dataelement101-8017
|
|
|
Id |
vl-dataelement101-8017 (2020‑02‑03 22:49:05)
|
Concept erft van |
NL-CM-17.1.4 (2017‑12‑31)
|
Omschrijving |
Medisch specialisme van de zorgverlener. Het betreft hierbij de erkende medische specialismen
zoals vermeld in de wet BIG. Bijvoorbeeld huisarts of cardioloog.
|
Terminologiekoppeling |
Dit concept wordt uitgedrukt door code "394658006" (clinical speciality) uit codesysteem 2.16.840.1.113883.6.96
SNOMED CT)
|
Waardendomein |
Code |
Keuzelijst |
|
Voorbeeld |
Cardioloog |
|
|
Adresgegevens
vl-dataelement101-8018
|
|
|
|
|
Adresgegevens
vl-dataelement101-8019
|
|
|
Id |
vl-dataelement101-8019 (2020‑02‑03 22:49:05)
|
Concept erft van |
NL-CM-2017-236 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de subbouwsteen Adresgegevens. Dit rootconcept bevat alle gegevenselementen
van de subbouwsteen Adresgegevens.
|
|
|
Contactgegevens
vl-dataelement101-8020
|
|
|
Id |
vl-dataelement101-8020 (2020‑02‑03 22:49:05)
|
Concept erft van |
NL-CM-17.1.8 (2017‑12‑31)
|
Omschrijving |
Telefoonnummer(s) of e-mailadres(sen) van de zorgverlener. |
Gebruikt door
|
5 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Contactgegevens
vl-dataelement101-8021
|
|
|
Id |
vl-dataelement101-8021 (2020‑02‑03 22:49:05)
|
Concept erft van |
NL-CM-2017-237 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de sub-bouwsteen Contactgegevens. Dit rootconcept bevat alle gegevenselementen
van de sub-bouwsteen Contactgegevens.
|
Gebruikt door
|
5 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Zorgaanbieder
vl-dataelement101-8022
|
|
|
Id |
vl-dataelement101-8022 (2020‑02‑03 22:49:05)
|
Concept erft van |
NL-CM-17.1.6 (2017‑12‑31)
|
Omschrijving |
De organisatie waarbij de zorgverlener werkzaam is. |
Gebruikt door
|
5 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Zorgaanbieder
vl-dataelement101-8023
|
|
|
Id |
vl-dataelement101-8023 (2020‑02‑03 22:49:05)
|
Concept erft van |
NL-CM-2017-238 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de bouwsteen Zorgaanbieder. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Zorgaanbieder.
|
Gebruikt door
|
5 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
ZorgverlenersRol
vl-dataelement101-8024
|
|
|
Id |
vl-dataelement101-8024 (2020‑02‑03 22:49:05)
|
Concept erft van |
NL-CM-17.1.5 (2017‑12‑31)
|
Omschrijving |
De rol die de zorgverlener in het zorgproces vervult. Voor zorgverleners kan dit bijvoorbeeld
behandelaar, verwijzer of uitvoerder zijn.
|
Waardendomein |
Code |
Keuzelijst |
|
Voorbeeld |
Hoofdbehandelaar |
|
|
Zorgaanbieder
vl-dataelement101-7299
|
|
|
Id |
vl-dataelement101-7299 (2020‑02‑02 22:24:44)
|
Concept erft van |
NL-CM-17.2.1 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de bouwsteen Zorgaanbieder. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Zorgaanbieder.
|
Gebruikt door
|
5 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
ZorgaanbiederIdentificatienummer
vl-dataelement101-8025
|
|
|
Id |
vl-dataelement101-8025 (2020‑02‑03 22:49:38)
|
Concept erft van |
NL-CM-17.2.2 (2017‑12‑31)
|
Omschrijving |
Identificerend nummer van de organisatie. Voor Nederlandse zorgaanbieders wordt hiervoor,
indien mogelijk, het URA nummer of het AGB nummer gebruikt. Afhankelijk van de context
zijn ook andere ID's mogelijk. Voor buitenlandse of niet aangesloten zorgaanbieders
kan een ander uniek identificerend nummer gebruikt worden. Dit moet vergezeld gaan
met de naam en/of code van de uitgevende organisatie.
|
Operationalisatie |
- UZI register abonneenummer (URA) (OID: 2.16.528.1.1007.3.3)
- Vektis AGB-zorgverlener tabel (OID: 2.16.840.1.113883.2.4.6.1)
|
Waardendomein |
Identificatie |
Voorbeeld |
21870932 |
Gebruikt door
|
5 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
OrganisatieNaam
vl-dataelement101-8026
|
|
|
Id |
vl-dataelement101-8026 (2020‑02‑03 22:49:38)
|
Concept erft van |
NL-CM-17.2.3 (2017‑12‑31)
|
Omschrijving |
Naam van de organisatie. Indien een identificatienummer meegegeven wordt, moet de
naam overeenkomen met de naam die bij het identificatienummer hoort.
|
Waardendomein |
String |
Voorbeeld |
Erasmus Universitair Medisch Centrum |
Gebruikt door
|
5 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
OrganisatieLocatie
vl-dataelement101-8027
|
|
|
Id |
vl-dataelement101-8027 (2020‑02‑03 22:49:38)
|
Concept erft van |
NL-CM-17.2.8 (2017‑12‑31)
|
Omschrijving |
Naam van de locatie, indien een zorgorganisatie meer dan één locatie heeft. |
Waardendomein |
String |
Voorbeeld |
Sophia |
Gebruikt door
|
5 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
AfdelingSpecialisme
vl-dataelement101-8028
|
|
|
Id |
vl-dataelement101-8028 (2020‑02‑03 22:49:38)
|
Concept erft van |
NL-CM-17.2.7 (2017‑12‑31)
|
Omschrijving |
Het specialisme van de betrokken afdeling van de zorgaanbieder. Het afdelingsspecialisme
kan gevuld worden indien bij het vermelden van een zorgaanbieder een nadere aanduiding
gewenst is. Het betreft hierbij de erkende medische specialismen zoals vermeld in
de wet BIG.
|
Waardendomein |
Code |
Keuzelijst |
|
Voorbeeld |
Cardiologie |
|
|
Contactgegevens
vl-dataelement101-8029
|
|
|
Id |
vl-dataelement101-8029 (2020‑02‑03 22:49:38)
|
Concept erft van |
NL-CM-17.2.6 (2017‑12‑31)
|
Omschrijving |
De gegevens noodzakelijk om via telefoon en/of e-mail met de zorgaanbiedende organisatie
contact op te nemen.
|
Gebruikt door
|
5 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Contactgegevens
vl-dataelement101-8030
|
|
|
Id |
vl-dataelement101-8030 (2020‑02‑03 22:49:38)
|
Concept erft van |
NL-CM-2017-233 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de sub-bouwsteen Contactgegevens. Dit rootconcept bevat alle gegevenselementen
van de sub-bouwsteen Contactgegevens.
|
Gebruikt door
|
5 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Adresgegevens
vl-dataelement101-8031
|
|
|
|
|
Adresgegevens
vl-dataelement101-8032
|
|
|
Id |
vl-dataelement101-8032 (2020‑02‑03 22:49:38)
|
Concept erft van |
NL-CM-2017-234 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de subbouwsteen Adresgegevens. Dit rootconcept bevat alle gegevenselementen
van de subbouwsteen Adresgegevens.
|
|
|
OrganisatieType
vl-dataelement101-8033
|
|
|
Id |
vl-dataelement101-8033 (2020‑02‑03 22:49:38)
|
Concept erft van |
NL-CM-17.2.4 (2017‑12‑31)
|
Omschrijving |
De type zorgaanbieder, bijvoorbeeld algemeen ziekenhuis en verpleeghuis. Indien dit
veld gevuld is en voor het ZorgaanbiederIdentificatieNummer een AGB code gebruikt
wordt dient het type overeen te komen met het type dat impliciet in de AGB code opgenomen
is.
|
Waardendomein |
Code |
Keuzelijst |
|
Voorbeeld |
Zelfstandig behandelcentrum |
Gebruikt door
|
5 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
MedischHulpmiddel
vl-dataelement101-5683.4
|
|
|
Id |
vl-dataelement101-5683.4 (2019‑03‑29)
|
Concept erft van |
NL-CM-10.1.1 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de bouwsteen MedischHulpmiddel. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen MedischHulpmiddel.
|
Terminologiekoppeling |
Dit concept wordt uitgedrukt door code "49062001" (Device (physical object)) uit codesysteem 2.16.840.1.113883.6.96
SNOMED CT)
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Product
vl-dataelement101-5683.51
|
|
|
Id |
vl-dataelement101-5683.51 (2020‑02‑03 22:50:13)
|
Concept erft van |
NL-CM-10.1.2 (2017‑12‑31)
|
Omschrijving |
Het medische hulpmiddel dat wordt gebruikt (inwendig of uitwendig). |
Terminologiekoppeling |
Dit concept wordt uitgedrukt door code "405815000" (Procedure device) uit codesysteem 2.16.840.1.113883.6.96
SNOMED CT)
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
ProductID
vl-dataelement101-5683.52
|
|
|
Id |
vl-dataelement101-5683.52 (2020‑02‑03 22:50:13)
|
Concept erft van |
NL-CM-10.1.4 (2017‑12‑31)
|
Omschrijving |
Unieke identificatie van het product, bijvoorbeeld het serienummer. Veel gebruikte coderingen zijn HIBC en GTIN. Indien de wet verplicht stelt dat deze geregistreerd wordt op basis van een UDI (Unique
Device Identifier), dient de unieke identificatie opgebouwd te zijn uit een UDI-DI
(Device Identifier) en een UDI-PI (Production Identifier(s)). Voor meer informatie,
zie: http://www.gs1.org/healthcare/udi .
De UDI-DI dient m.b.t. GS1 GTIN (01) coderingen worden vastgelegd, waarmee o.a. een
firma aan het producttype wordt gekoppeld. De UDI-PI dient te bestaan uit de volgende
application identifier (AI); vervaldatum (17) en serienummer (21) en/of batch- of
lotnummer (10).
|
Waardendomein |
Code |
Keuzelijst |
|
Voorbeeld |
(01)08712345000004(17)160131(10)200652 |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
ProductType
vl-dataelement101-5683.53
|
|
|
Id |
vl-dataelement101-5683.53 (2020‑02‑03 22:50:13)
|
Concept erft van |
NL-CM-10.1.3 (2017‑12‑31)
|
Omschrijving |
De code van het type product. |
Waardendomein |
Code |
Keuzelijst |
|
Voorbeeld |
58938008 Wheelchair |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
ProductOmschrijving
vl-dataelement101-5683.54
|
|
|
Id |
vl-dataelement101-5683.54 (2020‑02‑03 22:50:13)
|
Concept erft van |
NL-CM-10.1.13 (2017‑12‑31)
|
Omschrijving |
Tekstuele beschrijving van het product. |
Waardendomein |
String |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
BeginDatum
vl-dataelement101-5683.55
|
|
|
Id |
vl-dataelement101-5683.55 (2020‑02‑03 22:50:13)
|
Concept erft van |
NL-CM-10.1.11 (2017‑12‑31)
|
Omschrijving |
De startdatum van eerste toepassing of implantatie het medische hulpmiddel. Een vage
datum, bijv. alleen een jaartal, is toegestaan.
|
Waardendomein |
Datum/tijd |
Voorbeeld |
24-02-2003 |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Indicatie
vl-dataelement101-5683.56
|
|
|
Id |
vl-dataelement101-5683.56 (2020‑02‑03 22:50:13)
|
Concept erft van |
NL-CM-10.1.7 (2017‑12‑31)
|
Omschrijving |
De medische reden voor het gebruik van het medisch hulpmiddel. |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Probleem
vl-dataelement101-5683.57
|
|
|
Id |
vl-dataelement101-5683.57 (2020‑02‑03 22:50:13)
|
Concept erft van |
NL-CM-2017-130 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de bouwsteen Probleem. Een probleem beschrijft een toestand met betrekking tot de gezondheid en/of het welzijn
van een individu. Deze toestand kan zijn benoemd door de patiënt zelf (een klacht),
of door zijn of haar zorgverlener (onder andere een diagnose).
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Toelichting
vl-dataelement101-5683.58
|
|
|
Id |
vl-dataelement101-5683.58 (2020‑02‑03 22:50:13)
|
Concept erft van |
NL-CM-10.1.10 (2017‑12‑31)
|
Omschrijving |
Opmerking bij de toepassing of informatie over het gebruikte hulpmiddel. |
Terminologiekoppeling |
Dit concept wordt uitgedrukt door code "48767-8" (Annotation comment) uit codesysteem 2.16.840.1.113883.6.1
LOINC)
|
Waardendomein |
String |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
AnatomischeLocatie
vl-dataelement101-5683.59
|
|
|
Id |
vl-dataelement101-5683.59 (2020‑02‑03 22:50:13)
|
Concept erft van |
NL-CM-10.1.6 (2017‑12‑31)
|
Omschrijving |
Anatomische locatie van het gebruikte hulpmiddel bij de patiënt. |
Terminologiekoppeling |
Dit concept wordt uitgedrukt door code "363698007" (Finding site) uit codesysteem 2.16.840.1.113883.6.96
SNOMED CT)
|
Waardendomein |
Code |
Keuzelijst |
|
Voorbeeld |
Oor |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Lateraliteit
vl-dataelement101-5683.60
|
|
|
Id |
vl-dataelement101-5683.60 (2020‑02‑03 22:50:13)
|
Concept erft van |
NL-CM-10.1.12 (2017‑12‑31)
|
Omschrijving |
Lateraliteit verbijzondert de anatomische locatie door, indien van toepassing, de
zijdigheid vast te leggen, bijvoorbeeld links.
|
Terminologiekoppeling |
Dit concept wordt uitgedrukt door code "272741003" (Laterality) uit codesysteem 2.16.840.1.113883.6.96
SNOMED CT)
|
Waardendomein |
Code |
Keuzelijst |
|
Voorbeeld |
Links |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Locatie
vl-dataelement101-5683.61
|
|
|
Id |
vl-dataelement101-5683.61 (2020‑02‑03 22:50:13)
|
Concept erft van |
NL-CM-10.1.8 (2017‑12‑31)
|
Omschrijving |
De zorgaanbieder waar het gebruik van het hulpmiddel geïnitieerd werd of waar het
hulpmiddel gïmplanteerd werd.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Zorgaanbieder
vl-dataelement101-5683.62
|
|
|
Id |
vl-dataelement101-5683.62 (2020‑02‑03 22:50:13)
|
Concept erft van |
NL-CM-2017-131 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de bouwsteen Zorgaanbieder. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Zorgaanbieder.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Zorgverlener
vl-dataelement101-5683.63
|
|
|
Id |
vl-dataelement101-5683.63 (2020‑02‑03 22:50:13)
|
Concept erft van |
NL-CM-10.1.9 (2017‑12‑31)
|
Omschrijving |
De zorgverlener betrokken bij de indicatiestelling voor het gebruik of de implantatie
van het hulpmiddel.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Zorgverlener
vl-dataelement101-5683.64
|
|
|
Id |
vl-dataelement101-5683.64 (2020‑02‑03 22:50:13)
|
Concept erft van |
NL-CM-2017-132 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de bouwsteen Zorgverlener. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Zorgverlener. Bij verwijzing naar deze bouwsteen kan tevens de rol die de zorgverlener in het zorgproces
vervult, worden meegegeven. Voor zorgverleners kan dit bijvoorbeeld hoofdbehandelaar
of verwijzer zijn
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Betaler
vl-dataelement101-6620
|
|
|
Id |
vl-dataelement101-6620 (2019‑05‑05 17:06:22)
|
Concept erft van |
NL-CM-1.1.1 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de bouwsteen Betaler. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Betaler.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
BetalerPersoon
vl-dataelement101-8034
|
|
|
Id |
vl-dataelement101-8034 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-1.1.2 (2017‑12‑31)
|
Omschrijving |
Container van het concept BetalerPersoon. Deze container bevat alle gegevenselementen
van het concept BetalerPersoon.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
BetalerNaam
vl-dataelement101-8035
|
|
|
Id |
vl-dataelement101-8035 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-1.1.5 (2017‑12‑31)
|
Omschrijving |
Naamgegevens van de betalende persoon of organisatie (rechtspersoon). |
Waardendomein |
String |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Bankgegevens
vl-dataelement101-8036
|
|
|
Id |
vl-dataelement101-8036 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-1.1.4 (2017‑12‑31)
|
Omschrijving |
Container van het concept Bankgegevens. Deze container bevat alle gegevenselementen
van het concept Bankgegevens.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
BankNaam
vl-dataelement101-8037
|
|
|
Id |
vl-dataelement101-8037 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-1.1.9 (2017‑12‑31)
|
Omschrijving |
Naam van de financiële instelling. |
Waardendomein |
String |
Voorbeeld |
ING |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Bankcode
vl-dataelement101-8038
|
|
|
Id |
vl-dataelement101-8038 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-1.1.10 (2017‑12‑31)
|
Omschrijving |
Code die de bank en het filiaal aangeven. Voor Europese landen is dat de BIC of SWIFT
code van de instelling.
|
Waardendomein |
String |
Voorbeeld |
INGBNL2A |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Rekeningnummer
vl-dataelement101-8039
|
|
|
Id |
vl-dataelement101-8039 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-1.1.11 (2017‑12‑31)
|
Omschrijving |
Rekeningnummer van de betaler bij de genoemde instelling. Voor Europese landen is
dit het IBAN nummer.
|
Waardendomein |
String |
Voorbeeld |
NL85INGB0001234567 |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Verzekeraar
vl-dataelement101-8040
|
|
|
Id |
vl-dataelement101-8040 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-1.1.3 (2017‑12‑31)
|
Omschrijving |
Container van het concept Verzekeraar. Deze container bevat alle gegevenselementen
van het concept Verzekeraar.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Verzekering
vl-dataelement101-8041
|
|
|
Id |
vl-dataelement101-8041 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-1.1.8 (2017‑12‑31)
|
Omschrijving |
Container van het concept Verzekering. Deze container bevat alle gegevenselementen
van het concept Verzekering.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
BeginDatumTijd
vl-dataelement101-8042
|
|
|
Id |
vl-dataelement101-8042 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-1.1.13 (2017‑12‑31)
|
Omschrijving |
Datum vanaf wanneer de dekking van de verzekering geldt. |
Waardendomein |
Datum/tijd |
Voorbeeld |
01-01-2012 |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
EindDatumTijd
vl-dataelement101-8043
|
|
|
Id |
vl-dataelement101-8043 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-1.1.14 (2017‑12‑31)
|
Omschrijving |
Datum tot wanneer de dekking van de verzekering geldt. Dit item mapt op het EHIC veld 9 'Expiry date'.
|
Waardendomein |
Datum/tijd |
Voorbeeld |
31-01-2013 |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Verzekeringssoort
vl-dataelement101-8044
|
|
|
Id |
vl-dataelement101-8044 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-1.1.15 (2017‑12‑31)
|
Omschrijving |
Soort verzekering. Codes zoals geretourneerd bij de controle op verzekeringsrecht |
Waardendomein |
Code |
Keuzelijst |
|
Voorbeeld |
Basis verzekerd |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
IdentificatieNummer
vl-dataelement101-8045
|
|
|
Id |
vl-dataelement101-8045 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-1.1.7 (2017‑12‑31)
|
Omschrijving |
Unieke zorgverzekeraarsidentificatie (het UZOVI-nummer). |
Operationalisatie |
UZOVI (OID: 2.16.840.1.113883.2.4.6.4) |
Waardendomein |
Identificatie |
Voorbeeld |
3312 |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
OrganisatieNaam
vl-dataelement101-8046
|
|
|
Id |
vl-dataelement101-8046 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-1.1.16 (2017‑12‑31)
|
Omschrijving |
De naamgegevens van de zorgverzekeraar. Indien het UZOVI nummer als identificatienummer
wordt opgegeven, is dit de naam zoals vermeld in het UZOVI register en ook bij de
controle op verzekeringsrecht (COV) wordt teruggegeven.
|
Waardendomein |
String |
Voorbeeld |
MijnZorgverzekering N.V. |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
VerzekerdeNummer
vl-dataelement101-8047
|
|
|
Id |
vl-dataelement101-8047 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-1.1.6 (2017‑12‑31)
|
Omschrijving |
Nummer waaronder de verzekerde bekend is bij de verzekeraar Dit item mapt op het EHIC veld 8 'Identification number of the card'
|
Waardendomein |
String |
Voorbeeld |
992298765 |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Adresgegevens
vl-dataelement101-8048
|
|
|
Id |
vl-dataelement101-8048 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-1.1.17 (2017‑12‑31)
|
Omschrijving |
Adresgegevens van betaler. |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Adresgegevens
vl-dataelement101-8049
|
|
|
Id |
vl-dataelement101-8049 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-2017-21 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de subbouwsteen Adresgegevens. Dit rootconcept bevat alle gegevenselementen
van de subbouwsteen Adresgegevens.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Contactgegevens
vl-dataelement101-8050
|
|
|
Id |
vl-dataelement101-8050 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-1.1.12 (2017‑12‑31)
|
Omschrijving |
Telefoonnummer en/of e-mailadres van betaler. |
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Contactgegevens
vl-dataelement101-8051
|
|
|
Id |
vl-dataelement101-8051 (2020‑02‑03 22:50:39)
|
Concept erft van |
NL-CM-2017-22 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de sub-bouwsteen Contactgegevens. Dit rootconcept bevat alle gegevenselementen
van de sub-bouwsteen Contactgegevens.
|
Gebruikt door
|
één transactie, 0 templates, 0 maal geërfd |
|
|
|
|
Contactpersoon
vl-dataelement101-7991
|
|
|
Id |
vl-dataelement101-7991 (2020‑02‑03 22:30:06)
|
Concept erft van |
NL-CM-3.1.1 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de bouwsteen Contactpersoon. Dit rootconcept bevat alle gegevenselementen
van de bouwsteen Contactpersoon.
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Naamgegevens
vl-dataelement101-8052
|
|
|
Id |
vl-dataelement101-8052 (2020‑02‑03 22:51:08)
|
Concept erft van |
NL-CM-3.1.4 (2017‑12‑31)
|
Omschrijving |
Naamgegevens van contactpersoon. |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Naamgegevens
vl-dataelement101-8053
|
|
|
Id |
vl-dataelement101-8053 (2020‑02‑03 22:51:08)
|
Concept erft van |
NL-CM-2017-44 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de subbouwsteen Naamgegevens. Dit rootconcept bevat alle gegevenselementen
van de subbouwsteen Naamgegevens.
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Contactgegevens
vl-dataelement101-8054
|
|
|
Id |
vl-dataelement101-8054 (2020‑02‑03 22:51:08)
|
Concept erft van |
NL-CM-3.1.6 (2017‑12‑31)
|
Omschrijving |
Telefoonnummer en/of e-mailadres van contactpersoon. |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Contactgegevens
vl-dataelement101-8055
|
|
|
Id |
vl-dataelement101-8055 (2020‑02‑03 22:51:08)
|
Concept erft van |
NL-CM-2017-45 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de sub-bouwsteen Contactgegevens. Dit rootconcept bevat alle gegevenselementen
van de sub-bouwsteen Contactgegevens.
|
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Adresgegevens
vl-dataelement101-8056
|
|
|
|
|
Adresgegevens
vl-dataelement101-8057
|
|
|
Id |
vl-dataelement101-8057 (2020‑02‑03 22:51:08)
|
Concept erft van |
NL-CM-2017-46 (2017‑12‑31)
|
Omschrijving |
Rootconcept van de subbouwsteen Adresgegevens. Dit rootconcept bevat alle gegevenselementen
van de subbouwsteen Adresgegevens.
|
|
|
Rol
vl-dataelement101-8058
|
|
|
Id |
vl-dataelement101-8058 (2020‑02‑03 22:51:08)
|
Concept erft van |
NL-CM-3.1.2 (2017‑12‑31)
|
Omschrijving |
Definieert de rol van de contactpersoon in relatie tot de patiënt. |
Waardendomein |
Code |
Keuzelijst |
|
Voorbeeld |
Eerste contactpersoon |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|
Relatie
vl-dataelement101-8059
|
|
|
Id |
vl-dataelement101-8059 (2020‑02‑03 22:51:08)
|
Concept erft van |
NL-CM-3.1.3 (2017‑12‑31)
|
Omschrijving |
Definieert de familiaire relatie van de contactpersoon tot de patiënt. |
Waardendomein |
Code |
Keuzelijst |
|
Voorbeeld |
Dochter |
Gebruikt door
|
2 transacties, 0 templates, 0 maal geërfd |
|
|
|
|