Projectinformatie Project Information Informationen zum Projekt Projectinformatie Project Information Informationen zum Projekt Datasetdefinitie Data Set Definition Data Set Definition Data Set Definitie Data Set Definition Data Set Definition Scenariodefinitie Scenario Definition Szenario Definition Scenariodefinitie, inclusief actoren, transacties, modellen, cardinaliteiten en conformancestatements Scenario Definition, with actors, transactions, models, cardinalities, conformance statements Szenario Definition, mit Aktoren, Transaktionen, Modellem, Kardinalitäten, Konformitätsangaben Gebruikte identificaties Identifiers used Benutzte Identifikatoren Gebruikte identificaties, bedoeld voor weergavedoeleinden Identifiers used, rendering only Benutzte Identifikatoren, nur zur Anzeige Terminologiedefinities Terminology definitions Terminologische Definitionen Terminologiedefinities Terminology definitions Terminologische Definitionen Regeldefinities Rules definitions Regeldefinitionen Regeldefinities Rules definitions Regeldefinitionen Issuelijst Issue list Problemliste Issuelijst Issue list Problemliste DECOR-project is een (building block) repository (BBR) DECOR project is a (building block) repository (BBR) DECOR-Projekt ist ein (Building Block) Repository (BBR) Indication whether this DECOR project is a (building block) repository (BBR) DECOR-project is privé DECOR project is private DECOR-Projekt ist privat Indication whether this DECOR project is private, i.e. should NOT be included in searches from external. DECOR-project release nummer DECOR project release number DECOR-Projekt Release Nummer Release number (dddd) of the DECOR project file, for conversion detection beteeen releases later Contains dummy attributes that force xmlns declarations for templates author's id, shall be a shorthand id per project, e.g. "1" username, must be the same as the corresponding Exist-DB login name User's email address Specifies whether the automatic notifier system (if activated) should notify this author about changes of any project issue. Default is "on" Date the author became effective. On a project author this the date he became a project author. On an issue event it is the date he became author of this event. Adds expiration/inactive data to author. If false, the author is no longer considered active. Default is true. Note: for performance reasons you MUST set active to false explicitly when applicable, even though property active may be inferred from the expirationDate. Date the author is no longer considered active. Structured Copyright type. Determines the way that the copyright holder contributed to the project/building block repository contents Auteur Author Autor Contributor Contributor Mitwirkender Reviewer Reviewer Rezensent RESTful service RESTful Service RESTful Service End Point for RESTful services. Examples are FHIR End Points, and DECOR services Standaard template-element namespace Default Template Element Namespace Default Template Element Namespace The default namespace prefix for all template element name definitions Repository referentie Repository reference Repository Referenz ART-DECOR repository reference ART-DECOR repository URI directly pointing to the services, e.g. "http://art-decor.org/decor/services/"; ends with "/" ART-DECOR repository identification string (prefix), e.g. "ad1bbr-"; ends with "-" For future use Determines the format of building blocks on the end point A human-friendly name of the repository. Decor Object Types. Note: should you ever change list, please also see schematron check with name="Validate Ids". DECOR DECOR DECOR DECOR building blocks DECOR building blocks DECOR building blocks HL7 FHIR HL7 FHIR HL7 FHIR HL7 FHIR® bouwstenen, compatibiliteit met versie en andere capaciteiten zoals welke resources deze levert, vast te stellen op basis van de Conformance profile op het endpoint HL7 FHIR® building blocks, compatibility with version and other capabilities such as which resources it serves to be determined based on the Conformance profile on the endpoint HL7 FHIR® building blocks, compatibility with version and other capabilities such as which resources it serves to be determined based on the Conformance profile on the endpoint HL7 FHIR®© Object Types. Note: should you ever change list, please also see schematron check with name="Validate Ids". http://hl7.org/fhir/ FHIR FHIR FHIR FHIR FHIR FHIR Decor Object Types. Note: should you ever change list, please also see schematron check with name="Validate Ids". Dataset Data set Datensatz Dataset Data set Datensatz Datasetconcept Data Element Datenelement datasetconcept data element Datenelement Scenario Scenario Szenario scenario scenario Szenario Transactie Transaction Transaktion transactie transaction Transaktion Actoren Actors Akteure actoren actors Aktoren Waardelijst Value Set Value Set value set waardelijst Value Set Issue Issue Vorgang issue issue Vorgang Regel Rule Regel regel (intern) rule (internal) Regel (intern) Template Template Template template template Template Conceptenlijst Concept list Konzeptliste conceptenlijst concept list Konzeptliste Template-element Template Element Template-Element template-element template element Template-Element Testscenario Test Scenario Test-Szenario testscenario test scenario Testszenario Test datasetconcept Test Data Element Test Data Element test datasetconcept test data element Testdaten-Element Voorbeeldtransactie Example transaction Beispiel-Transaktion Example transaction Voorbeeldtransactie Beispiel-Transaktion Testeisen Test requirements Test-Anorderung Test profile Test requirements Test-Anorderung Community Community Community Community. Expectation is that the DECOR-project assigns ids to communities under this base id, and communities branch under this base Community. Verwachting is dat het DECOR-project id's toekent aan communities en dat zij verder vertakken onder deze basis Community. Expectation is that the DECOR-project assigns ids to communities under this base id, and communities branch under this base Codesysteem Code system Codesystem Code system Codesysteem Codesystem Concept Map Concept Map Concept Map Concept Map Concept Map Concept Map StructureDefinition StructureDefinition StructureDefinition HL7 FHIR StructureDefinition HL7 FHIR StructureDefinition HL7 FHIR StructureDefinition Questionnaire Questionnaire Questionnaire HL7 FHIR Questionnaire HL7 FHIR Questionnaire HL7 FHIR Questionnaire QuestionnaireResponse QuestionnaireResponse QuestionnaireResponse HL7 FHIR QuestionnaireResponse HL7 FHIR QuestionnaireResponse HL7 FHIR QuestionnaireResponse Questionnaire (enriched) Questionnaire (enriched) Questionnaire (enriched) HL7 FHIR Questionnaire (enriched) HL7 FHIR Questionnaire (enriched) HL7 FHIR Questionnaire (enriched) Browser Code System Browser Codesysteem Browser Codesystem Browser Code System. Contains de-normalized items for speedy browsing Browser Codesysteem. Bevat gedenormaliseerde items voor snel browsen Browser Codesystem. Enthält denormalisierte Elemente für schnelles Browsen Implementation Guide Implementation Guide Implementation Guide Implementation Guide (ART-DECOR) Implementation Guide (ART-DECOR) Implementation Guide (ART-DECOR) HL7 FHIR®© Object Formats. Actually matching HL7 FHIR Server package versions. http://hl7.org/fhir/ dstu2 dstu2 dstu2 DSTU2 otherwise known as 1.0.2 DSTU2 otherwise known as 1.0.2 DSTU2 otherwise known as 1.0.2 stu3 stu3 stu3 r4 r4 r4 HL7 CDA®© Object Formats. http://hl7.org/fhir/ CDA R1 CDA R1 CDA R1 CDA R2 CDA R2 CDA R2 CDA R2.1 CDA R2.1 CDA R2.1 Allows both OIDs for codesystems or special 'nullFlavor' Decor Object Formats. HTML HTML HTML HTML HTML HTML XML XML XML XML XML XML JSON JSON JSON JSON JSON JSON CSV CSV CSV CSV CSV CSV SQL SQL SQL SQL SQL SQL SVS SVS SVS SVS SVS SVS A human readable release note for convenient human rendition; not used by an application. A human readable version number or version label for convenient human rendition; not used by an application. Whether this release bears an implementation guide. The authoritative body who has reviewed the Dataset for (clinical) accuracy and relevance, and authorized it for publication. Registries may require this element to be valued Dataset properties A copyright statement relating to the dataset and/or its contents. The relationships of the current object to another object. Objects MAY have one or more relationships. Each relationship SHALL point to an object of the same nature. Examples include: datasets can relate to datasets, concepts can relate to concepts, value sets can relate to value sets. Note that relationships are implicit, and unchecked. They are a hint to the reader. Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains name and description of the referred object in relationship The @type of the relationship, at this point in time something like "SPEC", "GEN", "EQUIV", "VERSION", etc. Reference to the objects id or name. Note that while reference by name is supported, it is also discouraged and should only be used when the object is not a DECOR object, but still needs referencing. Reference to the objects @effectiveDate. Default is unspecified which means 'latest available version'. The relationships of the a questionnaire or questionnaire response to another object which might be an transaction (type=DRIV) or a answer to questionnaire (type=ANSW). Note that relationships are implicit, and unchecked. They are a hint to the reader. The @type of the relationship, at this point in time something like "DRIV" etc. Reference to the objects id or name. Note that while reference by name is supported, it is also discouraged and should only be used when the object is not a DECOR object, but still needs referencing. Reference to the objects @effectiveDate. Default is unspecified which means 'latest available version'. Adds an arbitrary property as name/value pair to its parent. This property SHALL NOT signify/trigger any specific ART-DECOR behavior. This is useful for storing specific information that has no other obvious place and needs to be in a computable place. Examples include external ids, keywords, review status etc. These properties are not meant to be displayed in all contexts, but only in user defined reports/overviews. The 'value' is mixed XHTML compatible content Name of the property. Eenheid Unit Einheit unit for quantities Valuta Currency Währung unit for monetary quantities Minimum Minimum Minimum range min include for quantities Maximum Maximum Maximum range max include for quantities Decimalen Digits Ziffern fraction digits for quantities, e.g. "1" for at least 1 or "1!" for exactly 1 or "3." for maximum 3 Tijdstempelprecisie Timestamp precision Genauigkeit Zeitangabe precisions for timing specs Standard Default Standard default value Vast Fixed Fest fixed value Minimumlengte Minimum length Minimale Länge min length for strings Maximumlengte Maximum length Maximale Länge max length for strings Data Set Value Domain DateTime, Date and Time Precision Data Set Value Domain Date Precision tenminste jaar (JJJJ) at least year (YYYY) mindestens Jahr (JJJJ) at least year (YYYY) jaar (JJJJ) year (YYYY) Jahr (JJJJ) year (YYYY) tenminste maand (MM) en jaar (JJJJ) at least month (MM) and year (YYYY) mindestens Jahr (JJJJ) und Monat (MM) at least month (MM) and year (YYYY) maand (MM) en jaar (JJJJ) month (MM) and year (YYYY) Monat (MM) und Jahr (JJJJ) month (MM) and year (YYYY) dag (DD), maand (MM) en jaar (JJJJ) day (DD), month (MM) and year (YYYY) Tag (TT), Monat (MM) und Jahr (JJJJ) day (DD), month (MM) and year (YYYY) Data Set Value Domain Date Time Stamp Precision tenminste jaar (JJJJ) at least year (YYYY) mindestens Jahr (JJJJ) at least year (YYYY) jaar (JJJJ) year (YYYY) Jahr (JJJJ) year (YYYY) tenminste maand (MM) en jaar (JJJJ) at least month (MM) and year (YYYY) mindestens Jahr (JJJJ) und Monat (MM) at least month (MM) and year (YYYY) maand (MM) en jaar (JJJJ) month (MM) and year (YYYY) Monat (MM) und Jahr (JJJJ) month (MM) and year (YYYY) tenminste dag (DD), maand (MM) en jaar (JJJJ) at least day (DD), month (MM) and year (YYYY) mindestens Tag (TT), Monat (MM) und Jahr (JJJJ) at least day (DD), month (MM) and year (YYYY) dag (DD), maand (MM) en jaar (JJJJ) day (DD), month (MM) and year (YYYY) Tag (TT), Monat (MM) und Jahr (JJJJ) day (DD), month (MM) and year (YYYY) tenminste dag (DD), maand (MM) en jaar (JJJJ), uur (uu) en minuut (mm) at least day (DD), month (MM) and year (YYYY), hour (hh) and minute (mm) mindestens Tag (TT), Monat (MM) und Jahr (JJJJ), Stunde (ss) und Minute (mm) at least day (DD), month (MM) and year (YYYY), hour (hh) and minute (mm) Data Set Value Domain Time Precision tenminste uren (HH) at least hours (HH) mindestens Stunden (HH) at least year (YYYY) uren (HH) hours (HH) Stunden (HH) hours (HH) tenminste uren (HH) en minuten (MM) at least hours (HH) and minuten (MM) mindestens Stunden (HH) und Minuten (MM) at least hours (HH) and minuten (MM) uren (HH) en minuten (MM) hours (HH) and minuten (MM) Stunden (HH) und Minuten (MM) hours (HH) and minuten (MM) uren (HH), minuten (MM) en seconden (SS) hours (HH), minutes (MM) and seconds (SS) Stunden (HH), Minuten (MM) and seconds (SS) hours (HH), minutes (MM) and seconds (SS) Data Set Concept Type for the Value Domain String String Zeichenkette Represents any text item, without visual formatting. Code Code Kode A system of valid symbols/codes, that substitute for specified concepts e.g. alpha, numeric, symbols and/or combinations, usually defined by a formal reference to a terminology or ontology, but may also be defined by the provision of text. Typically a symbol/code is expressed with a value for code, an identifier for the terminology or ontology it belongs to and at least one textual representation (display name). Identificatie Identifier Identifikator Type for representing identifiers of real-world entities. Typical identifiers include drivers licence number, social security number, prescription id, order id, and so on. Datum Date Datum Represents an absolute point in time, as measured on the Gregorian calendar, and specified only to the day. Semantics defined by ISO 8601. Used for recording dates in real world time. The partial form is used for approximate birth dates, dates of death, etc. Datum/tijd Date/time Datum/Zeit Represents an absolute point in time, specified to the second. Semantics defined by ISO 8601. Used for recording a precise point in real world time, e.g. the exact date and time of the birth of a baby, and for approximate time stamps, e.g. the origin of an history observation which is only partially known. Tijd Time Zeit Represents an point in time on the 24 hour clock without specifying the date, specified to the second. Semantics defined by ISO 8601. Used for recording a point in real world time, e.g. the hours to take medication (08, 12, 18 o'clock), exact time a baby was born, time of stopping CPR. Hoeveelheid Quantity Quantität Quantitified type representing "scientific" quantities, i.e. quantities expressed as a magnitude and units. If not further specified with fractionDigits, a decimal number with optional decimal point (i.e. '3.14159265359'). There are some "special" quantities (used in healthcare), explained later: for time durations duration shall be used; for monetary amounts currency shall be used Tijdsduur Duration Dauer Is a quantity, represents a period of time with respect to a notional point in time, which is not specified. A sign may be used to indicate the duration is “backwards” in time rather than forwards. Boolean Boolean Boolescher Wert Items which are truly boolean data, such as true/false or yes/no answers. Aantal Count Zähler Countable (non-monetary) quantities. Used for countable types such as pregnancies, steps (taken by a physiotherapy patient), number of cigarettes smoked in a day. Ordinaal Ordinal Ordinalzahl Models rankings and scores, e.g. pain, Apgar, reflex, ASA, Tanner values, etc, where there is a) implied ordering, b) no implication that the distance between each value is con- stant, and c) the total number of values is finite. Note that although the term ‘ordinal’ in mathematics means natural numbers only, here any integer is allowed, since negative and zero values are often used by medical professionals for values around a neutral point. Examples of sets of ordinal values: -3, -2, -1, 0, 1, 2, 3 (reflex response values); 0, 1, 2 (Apgar score values); 1, 2, 3, 4,... (ASA classification); I, II, III, IV, ... (Tanner scale) Tekst Text Text Represents a text item, which may contain any amount of legal characters arranged as e.g. words, sentences etc. Visual formatting and hyperlinks may be included. Decimaal getal Decimal number Dezimalzahl Decimal number (rarely used, in most cases a decimal number is actually a quantity). Binair Binary Binärinformation Things that are typically stored as binary objects in the computer world and need to be rendered appropriately, e.g. images: like X-rays, computertomographic images and scans. Samengestelde gegevens Collection of data Zusammenstellung von Daten Non-atomic datatypes which are not explictly further defined in the dataset itself. Example: 'address' or 'person name'. Usually complex types are assumed to be well-known enough not to warrant further decomposition in the dataset itself. Data Set Concept, is either a group or an item. A group may contain other groups or items and does not contain a operationalizations or value domain definitions An item typically has operationalizations and value domain definitions and may not contain a concept Data Set Concept inherits properties from another concept. Inherit is pulled into the current structure and will fail on circular references Data Set Concept references properties from another concept. Contains is not pulled into the current structure and is suited for circular references Data Set Concept Name (short). One name per language. Synonym for a Data Set Concept Name (short). Can have multiple synonyms per language. Data Set Concept Description (long). One to many descriptions per language Data Set Concept Source, human readable hint where this data element originally comes from Data Set rationale, human readable justification or explanation why this concept is present Data Set Concept comments Data Set Concept properties Data Set Concept relationship to another data set concept. Data Set Concept Operationalization, e.g. how to measure, obtain, specify the value of an observation Data Set Concept Value Domain, properties of the value in an instance Data Set Concept History Prohibited when concept is a reference through inherit or contains. Required in all other cases. Data Set Concept History of either a group or an item. A Concept History may not contain nested history items The time that the given information ceased to be correct. Data Set Concept Type Groep Group Gruppe group of data set items groep van data set items Gruppe von Dataset-Items Item Item Item data set item datasetitem Dataset-Item Type of processing Strikt Strict Strikt Los Lax Locker Defines the globally unique identifier for this conceptList and may be used to reference it. Concept lists SHOULD carry either @id or @ref Reference to a conceptList/@id. Concept lists SHOULD carry either @id or @ref Synonym for a Data Set Concept List Item Name (short). Can have multiple synonyms per language. indicates whether this is an exceptional concept (for example: unknown) Scenario that describes a business process The authoritative body who has reviewed the Scenario for (clinical) accuracy and relevance, and authorized it for publication. Registries may require this element to be valued Scenario properties A copyright statement relating to the scenario and/or its contents. Transaction group or singular transaction Transactiegroep of enkelvoudige transactie The authoritative body who has reviewed the Transaction for (clinical) accuracy and relevance, and authorized it for publication. Registries may require this element to be valued Transaction properties A copyright statement relating to the transaction and/or its contents. Globally and persistently unique identifier Root element name for the XML structure without namespace prefix that represents this transaction. For HL7 V3 messaging this could be REPC_IN004410UV, for HL7 V2 messaging this could be ADT_A01 Constitutes the value for the schematron file with the project prefix (//project/@prefix) Questionnaire wrapper: wraps FHIR Questionnaire either as the source or as a reference, and holds enough information to manage it. Questionnaire Wrapper Questionnaire Wrapper Questionnaire Wrapper The tag elements could be incorporated to specify any number of tags for search purposes The authoritative body who has reviewed the Questionnaire for (clinical) accuracy and relevance, and authorized it for publication. Registries may require this element to be valued The authoritative body who has reviewed the Questionnaire for (clinical) accuracy and relevance, and authorized it for publication. Registries may require this element to be valued A list of bodies who have reviewed the Questionnaire for (clinical) accuracy and relevance, and endorsed it for use Concept that represents the overall questionnaire A copyright statement relating to the Questionnaire and/or its contents. Intended jurisdiction for questionnaire (if applicable) Questions and sections within the Questionnaire The identifying OID of the Questionnaire Wrapper Not in use yet: Reference to a Questionnaire Wrapper @id. Questionnaire Wrappers SHALL carry either @id or @ref If the FHIR Questionnaire is contained as a reference, this link points to the source Not in use yet: Reference to a Questionnaire Wrapper. Default is unspecified which means 'latest available version'. Identifying the Questionnaire as Enhanced (type is QE), thus edited, modified, enriched. FHIR Resource type. Questions and sections within the Questionnaire The name of a section, the text of a question or text content for a display item. A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). Design comments. A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). A unit that the user may choose when providing a quantity value. Valueset containing permitted answers. Valueset containing permitted answers. Preferred terminology server. Preferred terminology server. Questions and sections within the Questionnaire An identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource. This element is a URI that refers to an Element Definition that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. 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. 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.). 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. An indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items) An indication, when true, that the value cannot be changed by a human respondent to the Questionnaire. The maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse. The inclusive lower bound on the range of allowed values for the data element. The inclusive upper bound on the range of allowed values for the data element. Indicates the terminology server(s) that are known to be capable of returning and potentially expanding the value set(s) associated with the whole questionnaire or a particular group or question within the questionnaire (depending on where the extension appears). Indicates a value set(s). Establishes mapping context for a Questionnaire item Questions and sections within the Questionnaire QuestionnaireResponse wrapper: wraps FHIR QuestionnaireResponse either as the source or as a reference, and holds enough information to manage it. QuestionnaireResponse Wrapper QuestionnaireResponse Wrapper QuestionnaireResponse Wrapper The tag elements could be incorporated to specify any number of tags for search purposes If the FHIR QuestionnaireResponse is contained as the source it goes here The identifying OID of the QuestionnaireResponse Wrapper Not in use yet: Reference to a QuestionnaireResponse Wrapper @id. Questionnaire Wrappers SHALL carry either @id or @ref If the FHIR QuestionnaireResponse is contained as a reference, this link points to the source Not in use yet: Reference to a QuestionnaireResponse Wrapper. Default is unspecified which means 'latest available version'. Copyright statement or a reference copyright statement. Allows specification of the type of a transaction. Groep Group Gruppe A transaction of type 'group' groups transactions of other types Initieel Initial Initial A transaction of type 'initial' says that this is the transaction that is initially sent, and usually invokes a response. This transaction type requires at least a 'sender' and a 'receiver' actor. Terug Back Zurück A transaction of type 'back' says that this transaction is sent in response to another transaction that preceded this one. Transactions of type 'back' may invoke a new transaction, but this is again of type initial. This transaction type requires at least a 'sender' and a 'receiver' actor. Registratie Stationary Stationär A transaction of type 'stationary' says that this transaction does not involve communication, but rather the local registration/administration of data. Transactions of type 'stationary' do not invoke new transaction. This transaction type requires exactly one 'sender' actor. Actor type for use in scenarios and transactions Persoon Person Person Person Organisatie Organization Organisation Organization Systeem Device Gerät Device Actor reference references an actor that is defined in the main list of actors for all scenarios Type of role the actor plays in a transaction Zender Sender Sender This actor is the sender of the transaction Ontvanger Receiver Empfänger This actor is the receiver of the transaction Registratie Stationary Stationär This actor is the person or device responsible for persisting the data Reference to a template/@id that sets the structure and rules for the concepts in this representingTemplate. Reference to a template/@effectiveDate. Default is unspecified which means 'latest available version'. Display name for this representingTemplate Reference to a dataset/@id that holds the concept definitions for the concepts in this representingTemplate. Reference to a dataset/@effectiveDate that holds the concept definitions for the concepts in this representingTemplate. Textual information related to the concept in the context of this transaction. This could be used for example to give more guidance around applied association overrides or conditions. Reference to a concept/@id that is not in history or in a concept list, and is in the dataset that the representing template refers to. Reference to a concept/@effectiveDate that is not in history or in a concept list, and is in the dataset that the representing template refers to. Note: optional for now, but will be required once the conversion for existing projects is in place. Default is unspecified which in practice comes down to 'false' Default is unspecified which in practice comes down to 'false' baseId stelt een OID branch voor en koppelt een type en weergavenaam aan die branch. Er MOGEN meerdere verschillende baseId's per type zijn. Een OID kan slechts voor één type worden gebruikt. Verdere toelichting op de branch kan door een id met toelichting te creëren. baseId represents an OID branch and associates a type and a display name to that branch. There MAY be multiple different baseId's per type. An OID can only be used for één type. Further explanation for the branch can be added by adding an id with descriptive text. baseId represents an OID branch and associates a type and a display name to that branch. There MAY be multiple different baseId's per type. An OID can only be used for één type. Further explanation for the branch can be added by adding an id with descriptive text. Determines whether or not this baseId is the default for its @type. There SHALL be exactly only one per type with @default='true' defaultBaseId stelt de standaard OID branch voor, voor een bepaalde type. Bij het toekennen van id's aan DECOR objecten wordt deze branch gebruikt als identificatiesysteem. Er MOET exact één defaultBaseId per type zijn. Voor iedere defaultBaseId MOET ook een baseId met hetzelfde type bestaan. Verdere toelichting op de branch kan door een id met toelichting te creëren. defaultBaseId represents the default OID branch for a given type. This branch is used as identifier system in assigning ids to DECOR objects. There SHALL be exactly one defaultBaseId per type. For every defaultBaseId there SHALL also be a baseId with a mtching type. Further explanation for the branch can be added by adding an id with descriptive text. defaultBaseId represents the default OID branch for a given type. This branch is used as identifier system in assigning ids to DECOR objects. There SHALL be exactly one defaultBaseId per type. For every defaultBaseId there SHALL also be a baseId with a mtching type. Further explanation for the branch can be added by adding an id with descriptive text. Met id geeft u toelichting op diverse ID's in relatie tot het project. Meestal tenminste een betekenis (designation), maar mogelijk ook alleen een koppeling met een bepaalde eigenschap zoals een FHIR URI. With id you give more information about ID related to the project. Usually at least a designation, but potentially also just an association with a property such as a FHIR URI With id you give more information about ID related to the project. Usually at least a designation, but potentially also just an association with a property such as a FHIR URI Id eigenschappen bijvoorbeeld voor het verbinden van dit id met andere typen identificatie (bijv. HL7 FHIR Systeem URI) voor hetzelfde object (codesysteem, OID-tak, identificatiesysteem). Als u van plan bent een HL7 FHIR System URI te verbinden die de voorkeur heeft boven de OID, gebruikt u dan @name='HL7-FHIR-System-URI-Preferred'. Als er wel een HL7 FHIR System URI bestaat maar deze niet de voorkeur heeft boven de OID, gebruikt u dan 'HL7-FHIR-System-URI'. Op deze manier herkent ART-DECOR deze indien van toepassing. Id properties for example to connect this id to other types of identifiers (e.g. HL7 FHIR System URI) for the same object (code system, OID branch, identification system) If you intend to connect an HL7 FHIR System URI that is preferred over the OID, please use @name='HL7-FHIR-System-URI-Preferred'. When you connect an HL7 FHIR System URI that exists but is not preferred over the OID, please use 'HL7-FHIR-System-URI'. This way ART-DECOR can pick it up if appropriate. identifierAssociation links a dataset concept to an identifier scheme. Any concept may have multiple of these associations concept id this assocication is associated with concept effectiveDate this assocication is associated with Object Identifier (OID) of the identification scheme this assocication is associated with. Example: '2.16.840.1.113883.4.1' for US Social Security Numbers Specifies whether the automatic notifier system (if activated) should notify all authors of the project about changes of any project issue. Default is "on" Automatic notifier system (if activated) notifies all authors of the project about changes of any project issue on/off Notificaties aan Notifier on Notifier on Notifier on Notificaties uit Notifier off Notifier off Notifier off Contains definition of labels specific to this DECOR instance. A DECOR instance does require labeling of issues. However once a label is used you SHOULD NOT alter/remove the label. Describes what the label is meant to represent/do Contains an HTML compatible reference to a color. Examples for the color red: red, #ff0000, rgb(255,0,0) Contains a code that may be used to refer to this label. Contains a descriptive name for this label. The list of historic events in terms of comments tracking and assignments The unique id of this issue The type of this issue The priority level of this issue, defaults to normal A short text to describe the issue (headline) Kind of issue Storing Incident Störung Incident Wijzigingsverzoek Change Request Änderungswunsch Change Request Voor de toekomst For future consideration Zur zukünftigen Berücksichtigung For future consideration Verduidelijking/toelichting noodzakelijk Request for Information/Education Bitte um Information/Aufklärung Request for Information/Education Priority of issue Hoogste Highest Höchste Highest Hoog High Hoch High Normaal Normal Normal Normal Laag Low Niedrig Low Laagst Lowest Niedrigste Lowest The object(s) that are subject to the issue The id of the object that is subject to the issue; either id or name of the object should be given The name of the object that is subject to the issue; either name or id of the object should be given The type of the object that is subject to the issue The optional effectiveDate of the object that is subject to the issue The type of the object that is subject to an issue Waardelijst Value Set Value Set Object with issues is a value set Object met de issues is een value set Objekt mit dem Problem ist ein Value Set Datasetconcept Data Element Datenelement Object with issues is a data element Object met de issues is een data element Objekt mit dem Problem ist ein Datenelement Template Template Template Object with issues is a template Object met de issues is een template Objekt mit dem Problem ist ein Template Transactie Transaction Transaktion Object with issues is a transaction Object met de issues is een transactie Objekt mit dem Problem ist eine Transaktion Dataset Data Set Datensatz Object with issues is a data set Object met de issues is een data set Objekt mit dem Problem ist ein Datensatz Scenario Scenario Szenario Object with issues is a scenario Object met de issues is een scenario Objekt mit dem Problem ist ein Szenario Issue Issue Issue Object with reference to another issue Object met een relatie naar een ander issue Objekt relatiert mit ein Issue Code system Codesysteem Codesystem Code system Codesysteem Codesystem Concept Map Concept Map Concept Map Concept Map Concept Map Concept Map StructureDefinition StructureDefinition StructureDefinition HL7 FHIR StructureDefinition HL7 FHIR StructureDefinition HL7 FHIR StructureDefinition Questionnaire Questionnaire Questionnaire HL7 FHIR Questionnaire HL7 FHIR Questionnaire HL7 FHIR Questionnaire QuestionnaireResponse QuestionnaireResponse QuestionnaireResponse HL7 FHIR QuestionnaireResponse HL7 FHIR QuestionnaireResponse HL7 FHIR QuestionnaireResponse Questionnaire (enriched) Questionnaire (enriched) Questionnaire (enriched) HL7 FHIR Questionnaire (enriched) HL7 FHIR Questionnaire (enriched) HL7 FHIR Questionnaire (enriched) Implementation Guide Implementation Guide Implementation Guide Implementation Guide (ART-DECOR) Implementation Guide (ART-DECOR) Implementation Guide (ART-DECOR) The author of this tracking. Every update to a tracking adds a new author marked with an effectiveDate. What is the description or question associated with this tracking Identifies the effective date and time of the tracking. References one or multiple label codes as defined in issues/labels The assignment of an issue to a person or group The author of this assignment. Every update to an assignment adds a new author marked with an effectiveDate. What is the description or question associated with this assignment Identifier of the person or group where this issue has been assigned to Name / label of the person or group where this issue has been assigned to Identifies the effective date and time of the assignment of the issue. References one or multiple label codes as defined in issues/labels Null Flavor NullFlavor NullFlavor NullFlavor Null Flavor Vocab Type Leaf Leaf Leaf L Leaf; a term that has no children in the specialization hierarchy, and is selectable, and therefore deemed to be a leaf. Abstract Abstract Abstract A Abstract; a term that has children in the specialization hierarchy, but is not, itself, selectable and therefore deemed abstract. Specializable Specializable Specializable S Specializable; a term that has children in the specialization hierarchy, and is also selectable and therefore deemed specializable. Deprecated Deprecated Deprecated D Deprecated; a term that should not be used any longer Conformancetype Conformance Type Conformance Typ Conformance Type Required Required Required R required. Implies max != 0, usually implies min > 0. If min > 0 then 'required' is implied unless 'mandatory' is stated. Conditioneel Conditional Conditional C conditional. Implies max != 0. Conditions SHALL be stated. Niet toegestaan Not permitted Nicht erlaubt NP not permitted. Implies min = 0 and max = 0. Condition Operator Type Condition Operator Type Condition Operator Type Condition Operator Type less-than-or-equal less-than-or-equal less-than-or-equal greater-than-or-equal greater-than-or-equal greater-than-or-equal less less less greater greater greater equal equal equal not-equal not-equal not-equal Allows both OIDs for codesystems or special 'nullFlavor' terminologyAssociation links a concept to a code or a concept list to a value set Refers to the concept/@effectiveDate if conceptId points to a real concept and not to conceptList or a concept under a conceptList. A displayname for the code, only for human readablility here Reference to a valueSet/@id or @name. References to @name are discouraged because they become ambiguous quickly. Reference to a valueSet/@effectiveDate. Default is unspecified which means 'latest available version'. Rating of mapping between the concept to the associated code or a concept list to an associated value set Concept association documents for mapping between coded concepts in two value sets (or between concepts in two datasets) The authoritative body who has reviewed the Concept Map for (clinical) accuracy and relevance, and authorized it for publication. Registries may require this element to be valued A list of bodies who have reviewed the Concept Map for (clinical) accuracy and relevance, and endorsed it for use A statement about the purpose of the Concept Map A copyright statement relating to the template and/or its contents. Defines the globally unique identifier for this concept map. Reference to a valueSet/@effectiveDate. Default is unspecified which means 'latest available version'. A displayname for the object, only for human readablility here Value Set. A DECOR valueSet can take different forms. It may be a simple value set reference (@ref) to a value set from a repository without any contents, id, effectiveDate or statusCode, but with a name and a displayName. The other option is a valueSet with contents, id, effectiveDate, statusCode, name and displayName. The authoritative body who has reviewed the Value set for (clinical) accuracy and relevance, and authorized it for publication. Registries may require this element to be valued A list of bodies who have reviewed the Value set for (clinical) accuracy and relevance, and endorsed it for use A statement about the purpose of the value set A copyright statement relating to the template and/or its contents. The free text description describing the changes in this version of the Value set as compared to the previous version. Since Value set versions are built off of previous versions, the net effect of this field is to function as a comprehensive historical reference of the Value set. Defines the globally unique identifier for this value set and may be used to reference it. Value sets SHOULD carry either @id or @ref Defines the canonical uir for this value set and may be used to reference it. Reference to a valueSet/@id. Value sets SHALL carry either @id or @ref Reference to a valueSet/@effectiveDate. Default is unspecified which means 'latest available version'. Display name for the code system as it is known in your context. This may or may not be the official name for the code system. Version string for the code system. This is only relevant for code systems with incompatible versions. If specified, than your instances will need to carry this information exactly as-is. Reference to a codeSystem/@codeSystemVersion. Default is unspecified which means 'latest available version'. Signals deprecation of the codeSystem in the context of this value set definition. This does not imply any status change in the code system itself. You may add a description for convenience, but should note that most of the time the description here overlaps with the designation/description of the coded concept Display name for the code system as it is known in your context. This may or may not be the official name for the code system. Version string for the code system. This is only relevant for code systems with incompatible versions. If specified, than your instances will need to carry this information exactly as-is. Either a value set ref or an operator op with code, codeSystem and displayName. Include is of another valueSet, typically from a repository, but potentially within the same DECOR definition. You may add a description for convenience, but should note that most of the time the description here overlaps with the description of the referenced value set / intensional definition Reference to a valueSet/@id. Reference to a valueSet/@effectiveDate. Default is unspecified which means 'latest available version'. Indicates whether the valueSet contents should be treated as exceptions. Default is 'false' meaning that the contents are included as concepts. Intensional Definition An identifier that uniquely names the class or "concept" within the context of the defining Code System An identifier that uniquely names the Code System Display name for the code system as it is known in your context. This may or may not be the official name for the code system. Version string for the code system. This is only relevant for code systems with incompatible versions. If specified, than your instances will need to carry this information exactly as-is. is-a is-a is-a is-a or << :: includes all concept ids that have a transitive is-a relationship with the concept Id provided as the value, including the provided concept itself (i.e. include child codes) is-a of << :: bevat alle concepten met een transitieve is-a relatie met het concept, inclusief het concept zelf (dus bevat onderliggende concepten) is-a oder < < :: enthält alle Konzept-IDs, die eine transitive is-a-Beziehung zu der als Wert bereitgestellten Konzept-ID haben, einschließlich des bereitgestellten Konzepts selbst (d.h. untergeordnete Codes einschließen). descendant-of descendant-of descendant-of descendant-of or < :: includes all concept ids that have a transitive is-a relationship with the concept Id provided as the value, excluding the provided concept itself (i.e. include child codes) descendant-of of < :: bevat alle concepten met een transitieve is-a relatie met het concept, exclusief het concept zelf (dus bevat onderliggende concepten) descendant-of oder < :: enthält alle Konzept-IDs, die eine transitive is-a-Beziehung zu der als Wert bereitgestellten Konzept-ID haben, mit Ausnahme des bereitgestellten Konzepts selbst (d. h. untergeordnete Codes einschließen). is-not-a is-not-a is-not-a is-not-a :: the specified property of the code does not have an is-a relationship with the provided value is-not-a :: concepten die geen is-a relatie met het betreffende concept hebben is-not-a :: enthält alle Konzept-IDs, die keine transitive is-a-Beziehung zu der als Wert bereitgestellten Konzept-ID haben regex regex regex regex :: the specified property of the code matches the regex specified in the provided value regex :: concept-codes die voldoen aan het gespecificeerde reguliere-expressie-patroon regex :: Die angegebene Eigenschaft des Codes stimmt mit dem im angegebenen Wert angegebenen regulären Ausdruck überein in in in in :: the selection of a set of concepts based on their membership of a (SNOMED CT) reference set in :: de selectie van een set concepten gebaseerd op hun lidmaatschap van een (SNOMED CT) referentieset in :: die Auswahl einer Reihe von Konzepten basierend auf ihrer Zugehörigkeit zu einer (SNOMED CT) Referenzmenge equal equal equal equal :: the specified property of the code is equal to the provided value equal :: de opgegeven property van de code is gelijk aan de opgegeven waarde equal :: die angegebene Property des Codes ist gleich dem angegeben Wert exist exist exist exist :: the specified property of the code does exist/does not exist (provided value must be true or false) exist :: de opgegeven property van de code bestaat / bestaat niet (opgegeven waarde moet true of false zijn) exist :: die angegebene Property des Codes existiert / existiert nicht (angegebener Wert muss true oder false sein) The code of a defined property of a code system (or one of the standard properties) Property Filter Operators The value of a defined property of a code system (or one of the standard properties) Code System A description that describes the Code System The authoritative body who has reviewed the Code System for (clinical) accuracy and relevance, and authorized it for publication. Registries may require this element to be valued A list of bodies who have reviewed the Code System for (clinical) accuracy and relevance, and endorsed it for use A statement about the purpose of the Code System A copyright statement relating to the Code System and/or its contents. The free text description describing the changes in this version of the Code System as compared to the previous version. Since Code System versions are built off of previous versions, the net effect of this field is to function as a comprehensive historical reference of the Code System. Additional information supplied about each concept A version identifier that uniquely identifies each version of a Code System A reference to a version identifier of a Code System If code comparison is case sensitive when codes within this system are compared to each other. If this value is missing, then it is not specified whether a code system is case sensitive or not. Reference to a codeSystem/@codeSystem. Default is unspecified which means 'latest available version'. A language symbol for the concept that is intended to convey the concept meaning to a human being. It may contain multiple designations per language to expres preferences, synonyms etc. For example, in SNOMED CT, the concept of "fever" has the fully specified name of "fever (finding)", a preferred name of "fever", and synonyms of "febrile" and "pyrexia". These are all designations in English for the concept of "fever". You may add a description for convenience, but should note that most of the time the description here overlaps with the designation/description of the coded concept An identifier that uniquely names the class or "concept" within the context of the defining Code System Status of the coded concept during the design phase Use of "level" is actually deprecated in code systems and shall be calculated upon use Use of "type" D, S and L are deprecated in code systems and shall be calculated upon use. D when statusCode is deprecated, retired, cancelled or rejected. S when concept is not D and has children. L when concept is not D and does not have children. Type A still has purpose Property value for the concept A reference per code to a parent or child concept Additional information supplied about each concept Type of CodeSystem Property A simple code A coded concept A string An integer A boolean A dateTime A decimal A description for the designation Type of designation (for that language), preferred, synonym, abbreviation, fully specified name A short description string for the designation Details of how a designation would be used, see also http://hl7.org/fhir/ValueSet/designation-use (2.16.840.1.113883.4.642.3.259), extended preferred preferent bevorzugt preferred synonym synoniem Synonym synonym abbreviation afkorting Abkürzung abbreviation fully specified name volledig gespecificeerde naam vollständig spezifizierter Name fully specified name Details of how a designation would be used preferred synonym abbreviation fully specified name LOINC fully specified name LOINC fully specified name LOINC fully specified name patient friendly preferred term patient friendly preferred term B1 level Details of how two concepts map to each other, the source is : related-to | equivalent | equal | wider | narrower | not-related ; See also FHIR ConceptMapEquivalence http://hl7.org/fhir/concept-map-equivalence; Releationship with "ISO/TR 12300:2014 Health informatics, Principles of mapping between terminological systems" is also indicated equal gelijk gleich The definitions of the concepts are exactly the same (i.e. only grammatical differences) and structural implications of meaning are identical or irrelevant (i.e. intentionally identical). ISO 12300: 1 = Equivalence of meaning; lexical, as well as conceptual. For example, asthma and asthma; ovarian cyst and cyst of ovary. equivalent gelijkwaardig äquivalent The definitions of the concepts mean the same thing (including when structural implications of meaning are considered) (i.e. extensionally identical). ISO 12300: 2 = Equivalence of meaning, but with synonymy. For example, ureteric calculus and ureteric stone; gall stones and cholelithiasis related to gerelateerd aan verwandt mit The concepts are related to each other, and have at least some overlap in meaning, but the exact relationship is not known wider breder breiter The source concept is broader in meaning than the target concept. ISO 12300: 3 = Source concept is broader and has a less specific meaning than the target concept/term. For example, obesity and morbid obesity; diabetes and diabetes mellitus type II. narrower nauwer enger The source concept is narrower in meaning than the target concept. The sense in which the mapping is narrower SHALL be described in the comments in this case, and applications should be careful when attempting to use these mappings operationally. ISO 12300: 4 = Source concept is narrower and has a more specific meaning than the target concept/term. For example, feels ugly and self-image finding; acute renal failure syndrome secondary to dehydration and acute renal failure syndrome. unmatched onvergelijkbaar unvergleichbar There is no match for this concept in the destination concept system. ISO 12300: 5 = No map is possible. No concept was found in the target with some degree of equivalence (as measured by any of the other four ratings). Details of how two concepts map to each other, the source is : relatedto | equivalent | equal | wider | subsumes | narrower | specializes | inexact | unmatched | disjoint; See also FHIR ConceptMapEquivalence http://hl7.org/fhir/concept-map-equivalence; Releationship with "ISO/TR 12300:2014 Health informatics, Principles of mapping between terminological systems" is also indicated related to gerelateerd aan verwandt mit The concepts are related to each other, and have at least some overlap in meaning, but the exact relationship is not known equivalent gelijkwaardig äquivalent The definitions of the concepts mean the same thing (including when structural implications of meaning are considered) (i.e. extensionally identical). ISO 12300: 2 = Equivalence of meaning, but with synonymy. For example, ureteric calculus and ureteric stone; gall stones and cholelithiasis equal gelijk gleich The definitions of the concepts are exactly the same (i.e. only grammatical differences) and structural implications of meaning are identical or irrelevant (i.e. intentionally identical). ISO 12300: 1 = Equivalence of meaning; lexical, as well as conceptual. For example, asthma and asthma; ovarian cyst and cyst of ovary. wider breder breiter The source concept is broader in meaning than the target concept. ISO 12300: 3 = Source concept is broader and has a less specific meaning than the target concept/term. For example, obesity and morbid obesity; diabetes and diabetes mellitus type II. subsumes omvat umfasst The target concept subsumes the meaning of the source concept (e.g. the source is-a target) narrower nauwer enger The source concept is narrower in meaning than the target concept. The sense in which the mapping is narrower SHALL be described in the comments in this case, and applications should be careful when attempting to use these mappings operationally. ISO 12300: 4 = Source concept is narrower and has a more specific meaning than the target concept/term. For example, feels ugly and self-image finding; acute renal failure syndrome secondary to dehydration and acute renal failure syndrome. specializes specialiseert spezialisiert The target concept specializes the meaning of the source concept (e.g. the target is-a source) inexact onnauwkeurig ungenau The mappings overlap, but both source and target cover additional meaning, or the definitions are imprecise and it is uncertain whether they have the same boundaries to their meaning. The sense in which the mapping is different SHALL be described in the comments in this case, and applications should be careful when attempting to use these mappings operationally. unmatched onvergelijkbaar unvergleichbar There is no match for this concept in the destination concept system. ISO 12300: 5 = No map is possible. No concept was found in the target with some degree of equivalence (as measured by any of the other four ratings). disjoint elkaar uitsluitend sich auschließend This is an explicit assertion that there is no mapping between the source and target concept. This is the format for Code Systems that are used for the Centralized ART-DECOR Terminology Service (CADTS), e.g. for the cross terminology CADTS browser. This follows in essence the definition of the DECOR codeSystem but contains de-normalized items for speedy browsing. It has a mandatory id and no ref or compilation items and a shortened set of status codes, among others. It has a set of extensions, all classified as "denormalizing elements" that marked under the specific xs:appinfo Set of available languages of designations Indicates if a language is available for all concepts in the codesystem Name of the Code System A description for the Code System Filename of the logo for the codesystem License text of the Code System The authoritative body who has reviewed the Code System for (clinical) accuracy and relevance, and authorized it for publication. Registries may require this element to be valued A list of bodies who have reviewed the Code System for (clinical) accuracy and relevance, and endorsed it for use A statement about the purpose of the Code System A copyright statement relating to the Code System and/or its contents. A definition for the Code System A property definition A short identifier for the Code System An identifier that uniquely identifies the Code System Identifies last point in time that the object was changed. While any versionable object could principally be marked using this attribute, the list of objects that need this in practice is scoped to be dataset, scenario, transaction, valueSet, codeSystem, template. This list may be extended over time. If code comparison is case sensitive when codes within this system are compared to each other. If this value is missing, then it is not specified whether a code system is case sensitive or not. Reference to a codeSystem/@codeSystem. Default is unspecified which means 'latest available version'. This is a coded concept used for the Centralized ART-DECOR Terminology Service (CADTS), e.g. for the cross terminology CADTS browser. It has a set of extensions, all classified as "denormalizing elements" that marked under the specific xs:appinfo This is a browsable coded concept designation used for ART-DECOR Terminology Service (CADTS). Some elements or attributes use shorter names for less space occupancy in the browsable format, g use BrowsableFreeFormMarkupWithLanguageCode A description for the designation Type of designation (for that language), preferred, synonym, abbreviation, fully specified name Word count of the designation, used for sorting search results. SPED String length of the designation, used for sorting search results. SPED Status of the coded concept during the design phase LOINC axis (fsn) attributes of designation, can only appear if use=lfsn LOINC LOINC axis (fsn) attributes of designation, can only appear if use=lfsn LOINC LOINC axis (fsn) attributes of designation, can only appear if use=lfsn LOINC LOINC axis (fsn) attributes of designation, can only appear if use=lfsn LOINC LOINC axis (fsn) attributes of designation, can only appear if use=lfsn LOINC LOINC axis (fsn) attributes of designation, can only appear if use=lfsn LOINC A definition of the coded concept Status of the coded concept during the design phase container for LOINC properties LOINC Associated value set, important for normative associated value sets LOINC type of value set link, example, normative etc. id of the associated value set SPED List of stable parents of the coded concept SPED List of stable children of the coded concept SPED List of stable ancestors of the coded concept SPED List of stable ancestors of self of the coded concept SPED Group of relationships that belong together SPED Ancestors of the related concept, used for intensional valueset definitions List of refset SNOMED List of maps SNOMED Associated concept, used for additional information on deprecated concepts SPED Associated refset attribute SNOMED An identifier that uniquely names the class or "concept" within the context of the defining Code System Status of the coded concept during the design phase Level, optional, calculated A reference per code to a parent concept, code carried in a different element name for speedy browsing SPED A reference per code to a parent concept, code carried in a different element name for speedy browsing SPED SPED SPED Structure definition wrapper: wraps FHIR StructureDefinition either as the source or as a reference, and holds enough information to manage it. StructureDefinition Wrapper StructureDefinition Wrapper StructureDefinition Wrapper If the FHIR StructureDefinition is contained as the source it goes here The identifying OID of the StructureDefinition Wrapper Not in use yet: Reference to a StructureDefinition Wrapper @id. StructureDefinition Wrappers SHALL carry either @id or @ref The mnemonic name of the StructureDefinition If the FHIR StructureDefinition is contained as a reference, this link points to the source Not in use yet: Reference to a StructureDefinition Wrapper. Default is unspecified which means 'latest available version'. Structure definition associations: associates logical model/dataset concepts to a FHIR StructureDefinition, and holds enough information to fetch the associated StructureDefinition. The StructureDefinition is expected to 'live' in the localhost FHIR package, or on a remote server. StructureDefinition Associations StructureDefinition Associations StructureDefinition Associations Reference to the StructureDefinition Warpper @id where this StructureDefinition association is referring to Reference to the StructureDefinition Warpper @effectiveDate where this StructureDefinition association is referring to Reference to the template/@id where this template association is referring to Reference to the template/@effectiveDate where this template association is referring to (should actually be named templateEffectiveDate according to the other attribute @templateId Reference to a concept/@id that is not in history or in a concept list For Templates this matches an element of attribute @id attribute. For StructureDefinitions this matches an element @id attribute For Templates this attribute is not applicable. For StructureDefinitions this matches an element/path/@value attribute. The attribute @elementPath is only relevant in the absence of an element/@id to bind on. When StructureDefinitions contains slicing then the element/path/@value will NOT be unique making the making the binding ambiguous. The authoritative body who has reviewed the Template for (clinical) accuracy and relevance, and authorized it for publication. Registries may require this element to be valued A list of bodies who have reviewed the Template for (clinical) accuracy and relevance, and endorsed it for use A statement about the purpose of the template A copyright statement relating to the template and/or its contents. The free text description describing the changes in this version of the Template as compared to the previous version. Since Template versions are built off of previous versions, the net effect of this field is to function as a comprehensive historical reference of the Template. The identifying OID of the template Reference to a template/@id. Templates SHALL carry either @id or @ref The mnemonic name of the template Whether the template is open (other elements than specified allowed) or closed (no other elements than specified allowed) Id of the authority/organisation/person Name of the authority/organisation/person The classification of the template In addition, tag elements could be incorporated to specifiy any number of tags for search purposes In addition, property elements could be incorporated to specifiy any number of properties not part of the standard metadata, e.g. for operationalization instructions The type of the template, something like "cdaentrylevel", "cdasectionlevel", "messagelevel" etc. CDA document level template CDA Document Level Template CDA Document Level Template CDA Document Level Template HL7v2/v3 message level template HL7 V2/V3 Message Level Template HL7 V2/V3 Message Level Template HL7 V2 or V3 Message Level Template CDA header level template CDA Header Level Template CDA Header Level Template CDA Header Level Template CDA section level template CDA Section Level Template CDA Section level template CDA Section Level Template CDA entry level template CDA Entry Level Template CDA Entry Level Template CDA Entry Level Template HL7v2 segment level template HL7 V2 Segment Level Template HL7 V2 Segment Level Template HL7 V2 Segment Level Template HL7v3 Clinical Statement level template HL7 V3 Clinical Statement Level Template HL7 V3 Clinical Statement Level Template HL7 V3 Clinical Statement Level Template HL7v3 Control Act level template HL7 V3 Control Act Level Template HL7 V3 Control Act Level Template HL7 V3 Control Act Level Template HL7v3 Payload level template HL7 V3 Payload Level Template HL7 V3 Payload Level Template HL7 V3 Payload Level Template HL7v2/v3 datatype level template HL7 V2/V3 Datatype Level Template HL7 V2/V3 Datatype Level Template HL7 V2 or V3 Datatype Level Template Templatetype niet gespecificeerd Template type not specified Template-Typ nicht spezifiziert Template type not specified The relationships of the template regarding other templates or model artifacts The @type of the relationship of the template, at this point in time something like "SPEC", "GEN", "EQUIV", "VERSION", etc. A reference by name or id to a template identifier, used for template-template relationships A reference to a model artifact identifier or description specifying from what this template is derived from or based on, e.g. an HL7 R-MIM, a DCM, used for template-model relationships Reference to a template/@effectiveDate. Default is unspecified which means 'latest available version'. Vervanging Replacement Ersatz This template replaces @template Specialisatie Specialization Spezialisierung This template specializes @template Generalisatie Generalization Generalisierung This template generalizes @template Kopie Copy Kopie This template is a design copy of @template Adaptatie Adaptation Adaptation This template is an adaptation of @template Equivalent Equivalent Equivalent This template is equivalent to @template regarding design Versie Version Version This template is a version of @template Backward compatible Backward Compatible Rückwärtskompatibel This template is backward compatible of @template Afgeleide Derived Abgeleitet For future use: This template is derived from model or other artifact expressed or specified in the @template attribute Afgeleide Derived Abgeleitet This Questionnaire is derived from a transaction expressed or specified in the @ref attribute Antwoord Answer Antwort This Questionnaire Response answers a Questionnaire specified in @ref As of now only a few formats are supported, e.g. "HL7 V3 XML ITS 1" = hl7v3xml1 Template format HL7v3 XML ITS 1 Template format HL7 V3 XML ITS 1 Template format HL7 V3 XML ITS 1 Template format HL7 V3 XML ITS 1 Template format HL7v2.5 XML ITS 1 Template format HL7 V2.5 XML ITS 1 Template format HL7 V2.5 XML ITS 1 Template format HL7 V2.5 XML ITS 1 Template format FHIR XML Template format FHIR XML Template format FHIR XML Template format FHIR XML Template format vMR CDS XML Template format vMR CDS XML Template format vMR CDS XML Template format vMR CDS XML Reference to a template/@id or @name. References to @name are discouraged because they become ambiguous quickly. Reference to a template/@effectiveDate. Default is unspecified which means 'latest available version'. Default is unspecified which in practice means 'false'. Whether the template is open (other elements than specified allowed) or closed (no other elements than specified allowed) Reference to a template/@id or @name. References to @name are discouraged because they become ambiguous quickly. Reference to a template/@effectiveDate. Default is unspecified which means 'latest available version'. Default is unspecified which in practice means 'false'. Inherit an artefact (here: a concept or a template), referenced by a ref (id). If no effectiveDate is given, flexibility DYNAMIC is assumed, STATIC date otherwise. Contains an artefact (here: a concept or a template), referenced by a ref (id). If no flexibility is given, flexibility DYNAMIC is assumed, STATIC date otherwise. Choice of elements and includes. The choice supports min/max occurence and any of its constituents may have a min/max occurence. Min/max on consituents cannot exceed the min/max boundaries of the choice. Can be used to indicate that the instance fragment (example) is right (@type=valid) or wrong (@type=error); default is "neutral". Kan worden gebruikt om te markeren dat het instancefragment (voorbeeld) geldig is (@type=valid) of fout (@type=error); standaardwaarde is "neutral". Can be used to specify a caption (string) that precedes the instance fragment (example) Type of Example given neutraal neutral neutral Used to indicate that the instance fragment (example) is not explictly stated to be right or wrong. Om aan te geven dat het instancefragment (voorbeeld) niet expliciet geldig of ongeldig is. geldig valid gültig Used to indicate explicitly that the instance fragment (example) is valid. Om aan te geven dat het een correct instancefragment (voorbeeld) betreft. ongeldig error ungültig Used to indicate explicitly that the instance fragment (example) is in error. Om aan te geven dat het een foutief instancefragment (voorbeeld) betreft. A short description string for the designation Relevant score value in an ordinal system, usually/preferably coded but ordinal values are known to exist with just a description. Coded examples include Apgar and Glasgow Coma Scale. An, at time of writing, uncoded example is the questionnaire "Positieve Gezondheid" (https://nl.wikipedia.org/wiki/Positieve_gezondheid) experimental voor testdoeleinden für Testzwecke DECOR project, codeSystem, valueSet or other artifact is for testing purposes, not real usage Identifies the effective date of the version of the object. Identifies the expiration date of the version of the object. Identifies the official release date of the version of the object. A human readable version number or version label for convenient human rendition; not used by an application. Identifies last point in time that the object was changed. Used to define version handling attributes Identifies last point in time that the object was changed. While any versionable object could principally be marked using this attribute, the list of objects that need this in practice is scoped to be dataset, scenario, transaction, valueSet, codeSystem, template. This list may be extended over time. Used to define version handling attributes, effective date is optional here Identifies last point in time that the object was changed. While any versionable object could principally be marked using this attribute, the list of objects that need this in practice is scoped to be dataset, scenario, transaction, valueSet, codeSystem, template. This list may be extended over time. Type of assertion (schematron) Fatal Fataal Fatal Error Fout Fehler Warning Waarschuwing Warnung Info Info Info Path starts at root node Path starts at any node Used as the type of a context template id Scope is templateId Scope is templateId Scope is templateId template scope is templateId element and sibling nodes. Requires a top level element templateId with the same id as the template itself Scope is top level element Scope is top level element Scope is top level element template scope is top level element with templateId element and child nodes. Requires that the template has one top level element and an element templateId with the same id as the template itself as child of that top level element a string "*" or "**" or a valid Oid. The value * requires a top level element templateId with the same id as the template itself. The value ** requires that the template has one top level element and an element templateId with the same id as the template itself as child of that top level element. When context/@id contains an Oid, the template requires requires a top level element templateId with that same id A real number that is restricted to a maximum of 10 characters, and may have no more than 5 decimal places. An integer number that is restricted to a maximum of 10 characters An integer or decimal range Default is unspecified which in practice means 'false'. Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Shorthand for HL7 V3 attribute. Use is discouraged, please use @name='..' and optionally @value='..' instead Determines that the attribute is requird to be in the instance. Default is 'false', meaning that the attribute is NOT optional, and thus required. Determines that the attribute is prohibited to be in the instance. Determines the datatype of the attribute in the instance. Used for datatype names of attributes only Used for attributes of type "quantity", "string" or "boolean". Allows assertion of one or more units, ranges, fraction digits or fixed values. Valid combinations of attributes are:
    • @unit @minInclude @maxInclude @fractionDigits
      @currency @minInclude @maxInclude @fractionDigits
      @minLength @maxLength
      @value
  • Data Set Value Domain Time Stamp Precision Used for attributes of "coded" types. Allows assertion of one or more codes, code systems or value sets. Reference to a valueSet/@id or @name. References to @name are discouraged because they become ambiguous quickly. Reference to a valueSet/@effectiveDate. Default is unspecified which means 'latest available version'. Coding strength of a vocabulary binding deprecated: use required. Required/CNE. Coded with no exceptions; this element SHALL be from the specified value set deprecated: gebruik required. Verplicht/CNE. Gecodeerd, geen uitzonderingen; dit element MOET uit de gespecificeerde waardenlijst komen deprecated: use required. Erforderlich/CNE. Codiert, keine Ausnahmen; das Element muss aus dem angegebene Value Set kommen. Required/CNE Verplicht/CNE Erforderlich/CNE Required/CNE. Coded with no exceptions; this element SHALL be from the specified value set Verplicht/CNE. Gecodeerd, geen uitzonderingen; dit element MOET uit de gespecificeerde waardenlijst komen Erforderlich/CNE. Codiert, keine Ausnahmen; das Element muss aus dem angegebene Value Set kommen. Required/CNE Verplicht/CNE Erforderlich/CNE deprecated, use extensible. Extensible/CWE. Coded with Exceptions; this element SHALL be from the specified value set if any of the codes within the value set can apply to the concept being communicated. If the value set does not cover the concept (based on human review), alternate codings (or, data type allowing, text) may be included instead. deprecated, gebruik extensible. Uitbreidbaar/CWE. Gecodeerde uitzonderingen toegestaan; dit element MOET uit de gespecificeerde waardenlijst komen als een van de codes binnen de waardenlijst van toepassing is op het concept dat wordt gecommuniceerd. Als de waarde het concept niet dekt (op basis van menselijke beoordeling), kunnen in plaats daarvan alternatieve coderingen (of datatype waarmee wordt toegestaan, tekst) worden opgenomen. deprecated, use extensible. Erweiterbar/CWE. Codiert, Ausnahmen zugelassen; Dieses Element sollte aus dem angegebenen Value Set kommen, wenn das Konzept kommuniziert wird. Wenn der Code das Konzept nicht abdeckt (basierend auf menschlicher Überprüfung), können alternative Kodierungen (oder falls der Datentyp es erlaubt, Text) eingeschlossen sein. Extensible/CWE Uitbreidbaar/CWE Erweiterbar/CWE Extensible/CWE. Coded with Exceptions; this element SHALL be from the specified value set if any of the codes within the value set can apply to the concept being communicated. If the value set does not cover the concept (based on human review), alternate codings (or, data type allowing, text) may be included instead. Uitbreidbaar/CWE. Gecodeerde uitzonderingen toegestaan; dit element MOET uit de gespecificeerde waardenlijst komen als een van de codes binnen de value set van toepassing is op het concept dat wordt gecommuniceerd. Als de waarde het concept niet dekt (op basis van menselijke beoordeling), kunnen in plaats daarvan alternatieve coderingen (of datatype waarmee wordt toegestaan, tekst) worden opgenomen. Erweiterbar/CWE. Codiert, Ausnahmen zugelassen; Dieses Element sollte aus dem angegebenen Value Set kommen, wenn das Konzept kommuniziert wird. Wenn der Code das Konzept nicht abdeckt (basierend auf menschlicher Überprüfung), können alternative Kodierungen (oder falls der Datentyp es erlaubt, Text) eingeschlossen sein. Extensible/CWE Uitbreidbaar/CWE Erweiterbar/CWE Preferred. Instances are encouraged to draw from the specified codes for interoperability purposes but are not required to do so to be considered conformant. Voorkeur. Instantiaties worden aangemoedigd om voor interoperabiliteitsdoeleinden codes op basis van de gespecificeerde waardenlijst te gebruiken. Bevorzugt. Instanzen werden aufgefordert, für Interoperabilitätszwecke die Codes aus dem Value Set zu nutzen. Preferred Voorkeur Bevorzugt Example. Instances are not expected or even encouraged to draw from the specified value set. The value set merely provides examples of the types of concepts intended to be included. Voorbeeld. Instantiaties worden niet verwacht of zelfs maar aangemoedigd om codes op basis van de gespecificeerde waardenlijst te gebruiken. De waardenlijst stelt een voorbeeld voor van het type concept dat gebruikt kan worden. Beispiel. Es wird in Instanzen nicht erwartet, dass der Code aus dem Value Set genutzt wird. Das Value Set enthält Beispiele für den Typ Konzept, die verwendet werden können. Example Voorbeeld Beispiel Additional compilation attributes on the dataset, template and valueSet element Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the services URL useful in retrieving the dataset, template, or value set Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the project @prefix of the project that defines the dataset, template, or value set Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the project @prefix of the project that referenced the dataset, template, or value set (normally current project) Additional compilation attributes on the decor root element Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the date stamp or 'development' for the currently processed project/(version|release) Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the label for the currently processed project/(version|release) Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the date stamp or 'development' of the compilation process Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains principal used in the compilation process (compilation may be run multiple times, one per language) Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains ART-DECOR URI of the server that ran the compilation. Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains DECOR services URI of the server that ran the compilation. Additional compilation attributes on the dataset element Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the short name for the dataset Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the project prefix for the dataset (ref) Additional compilation attributes on the dataset element Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the short name for the concept HL7® FHIR® canonical URI. Logical URI to reference this StructureDefinition, logical model, value set, etc. (globally unique) HL7® FHIR® canonical URI. Logical URI to reference this StructureDefinition, logical model, value set, etc. (globally unique) HL7® FHIR® kanonieke URI. Logische URI om te verwijzen naar deze StructureDefinition, dit logisch model, waardelijst, etc. (wereldwijd uniek) Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the calculated display name for the value in @id Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the calculated display name for the value in @ref Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the project prefix for the original concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the dataset id for the original concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the dataset effectiveDate for the inherited concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the dataset expirationDate for the original concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the dataset statusCode for the inherited concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the dataset versionLabel for the original concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the type for the original concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the statusCode for the inherited concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the effectiveDate for the inherited concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the versionLabel for the inherited concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the expirationDate for the inherited concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the concept id for the original concept, if the inherited concept was itself an inheriting/containing concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the concept statusCode for the original concept, if the inherited concept was itself an inheriting/containing concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the concept effectiveDate for the original concept, if the inherited concept was itself an inheriting/containing concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the concept versionLabel for the original concept, if the inherited concept was itself an inheriting/containing concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the concept expirationDate for the original concept, if the inherited concept was itself an inheriting/containing concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the concept project prefix for the original concept, if the inherited concept was itself an inheriting/containing concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains a boolean for whether or not the relationship 'lives' in the same project or not Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the implementation specific info (TODO: explain in more detail) Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the condition info from a transaction concept Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the copied terminology association from the terminology section applicable for this concept (TODO: explain in more detail) Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the copied identifier association from the ids section applicable for this concept (TODO: explain in more detail) Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains copied community information for this concept (TODO: explain in more detail) Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the enahanced value set bound to this concept (TODO: explain in more detail) Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the contextual information from a transaction concept (TODO: explain in more detail) Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains display names for code systems as an optimalization aid in the publication process Additional compilation attributes on the template/relationship element Added in compilation process for relationship. DO NOT ADD/EDIT yourself. Contains the id of the template Added in compilation process for relationship. DO NOT ADD/EDIT yourself. Contains the name of the template Added in compilation process for relationship. DO NOT ADD/EDIT yourself. Contains the displayName of the template Added in compilation process for relationship. DO NOT ADD/EDIT yourself. Contains the effectiveDate of the template Added in compilation process for relationship. DO NOT ADD/EDIT yourself. Contains the expirationDate of the template Added in compilation process for relationship. DO NOT ADD/EDIT yourself. Contains the statusCode of the template Added in compilation process for relationship. DO NOT ADD/EDIT yourself. Contains the versionLabel of the template Added in compilation process for relationship. DO NOT ADD/EDIT yourself. Contains the server url for template Added in compilation process for relationship. DO NOT ADD/EDIT yourself. Contains the project prefix for template Added in compilation process for relationship. DO NOT ADD/EDIT yourself. Signals the template indicated in the relationship was not found Additional compilation attributes on the terminologyAssociation element Added in compilation process for releases. DO NOT ADD/EDIT yourself. Contains the displayName of the value set if available else the name