From e9a2531ea5de196ad699c913b44731c84600d12f Mon Sep 17 00:00:00 2001 From: Lloyd McKenzie Date: Fri, 1 Feb 2019 20:42:28 -0700 Subject: [PATCH] Added new snapshot test (which currently fails) --- .../main/resources/schemas/fhir-single.xsd | 45085 ++++++++++++++++ .../src/main/resources/schemas/fhir-xhtml.xsd | 2101 + .../src/main/resources/schemas/xml.xsd | 272 + .../resources/schemas/xmldsig-core-schema.xsd | 254 + .../resources/snapshot-generation-tests.xml | 86 +- 5 files changed, 47793 insertions(+), 5 deletions(-) create mode 100644 org.hl7.fhir.r4/src/main/resources/schemas/fhir-single.xsd create mode 100644 org.hl7.fhir.r4/src/main/resources/schemas/fhir-xhtml.xsd create mode 100644 org.hl7.fhir.r4/src/main/resources/schemas/xml.xsd create mode 100644 org.hl7.fhir.r4/src/main/resources/schemas/xmldsig-core-schema.xsd diff --git a/org.hl7.fhir.r4/src/main/resources/schemas/fhir-single.xsd b/org.hl7.fhir.r4/src/main/resources/schemas/fhir-single.xsd new file mode 100644 index 000000000..7bb9366f8 --- /dev/null +++ b/org.hl7.fhir.r4/src/main/resources/schemas/fhir-single.xsd @@ -0,0 +1,45085 @@ + + + + + + + + + + + + + + + + + + A date or partial date (e.g. just year or year + month). There is no time zone. The format is a union of the schema types gYear, gYearMonth and date. Dates SHALL be valid dates. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + + + + + + + A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + + + + + A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents + If the element is present, it must have either a @value, an @id referenced from the Narrative, or extensions + + + + + + + + + + + + + + + A sequence of Unicode characters + Note that FHIR strings SHALL NOT exceed 1MB in size + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + + + + A whole number + 32 bit number; for values larger than this, use decimal + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + + + + + An OID represented as a URI + RFC 3001. See also ISO/IEC 8824:1990 € + If the element is present, it must have either a @value, an @id referenced from the Narrative, or extensions + + + + + + + + + + + + + + + + A URI that is a reference to a canonical URL on a FHIR resource + see [Canonical References](references.html#canonical) + If the element is present, it must have either a @value, an @id referenced from the Narrative, or extensions + + + + + + + + + + + + + + + String of characters used to identify a name or a resource + see http://en.wikipedia.org/wiki/Uniform_resource_identifier + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + + + + + A UUID, represented as a URI + See The Open Group, CDE 1.1 Remote Procedure Call specification, Appendix A. + If the element is present, it must have either a @value, an @id referenced from the Narrative, or extensions + + + + + + + + + + + + + + + + A URI that is a literal reference + If the element is present, it must have either a @value, an @id referenced from the Narrative, or extensions + + + + + + + + + + + + + + + An instant in time - known at least to the second + Note: This is intended for where precisely observed times are required, typically system logs etc., and not human-reported times - for them, see date and dateTime (which can be as precise as instant, but is not required to be) below. Time zone is always required + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + + + + Value of "true" or "false" + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + + + + A stream of bytes + A stream of bytes, base64 encoded + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + + + + An integer with a value that is not negative (e.g. >= 0) + If the element is present, it must have either a @value, an @id referenced from the Narrative, or extensions + + + + + + + + + + + + + + + + A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine + Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/ + If the element is present, it must have either a @value, an @id referenced from the Narrative, or extensions + + + + + + + + + + + + + + + A time during the day, with no date specified + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + + + + + + Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive. + RFC 4122 + If the element is present, it must have either a @value, an @id referenced from the Narrative, or extensions + + + + + + + + + + + + + + + An integer with a value that is positive (e.g. >0) + If the element is present, it must have either a @value, an @id referenced from the Narrative, or extensions + + + + + + + + + + + + + A rational number with implicit precision + Do not use an IEEE type floating point type, instead use something that works like a true decimal, with inbuilt precision (e.g. Java BigInteger) + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Optional Extension Element - found in all resources. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Base definition for all elements that are defined inside a resource - but not those in a data type. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. + +Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). + + + + + + + + + A human-readable summary of the resource conveying the essential clinical and business information for the resource. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data. + + + + + The actual narrative content, a stripped down version of XHTML. + + + + + + + + + + + Generated + + + + + Extensions + + + + + Additional + + + + + Empty + + + + + + + The status of a resource narrative. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Base definition for all elements in a resource. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. + + + + + + + + The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. + + + + + When the resource last changed - e.g. when the version changed. + + + + + A uri that identifies the source system of the resource. This provides a minimal amount of [[[Provenance]]] information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. + + + + + A list of profiles (references to [[[StructureDefinition]]] resources) that this resource claims to conform to. The URL is a reference to [[[StructureDefinition.url]]]. + + + + + Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. + + + + + Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. + + + + + + + + + An address expressed using postal conventions (as opposed to GPS or other location definition formats). This data type may be used to convey addresses for use in delivering mail as well as for visiting locations which might not be valid for mail delivery. There are a variety of postal address formats defined around the world. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The purpose of this address. + + + + + Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both. + + + + + Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts. + + + + + This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information. + + + + + The name of the city, town, suburb, village or other community or delivery center. + + + + + The name of the administrative area (county). + + + + + Sub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (e.g. US 2 letter state codes). + + + + + A postal code designating a region defined by the postal service. + + + + + Country - a nation as commonly understood or generally accepted. + + + + + Time period when address was/is in use. + + + + + + + + + + + Home + + + + + Work + + + + + Temporary + + + + + Old / Incorrect + + + + + Billing + + + + + + + The use of an address. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Postal + + + + + Physical + + + + + Postal & Physical + + + + + + + The type of an address (physical / postal). + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A contributor to the content of a knowledge asset, including authors, editors, reviewers, and endorsers. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The type of contributor. + + + + + The name of the individual or organization responsible for the contribution. + + + + + Contact details to assist a user in finding and communicating with the contributor. + + + + + + + + + + + Author + + + + + Editor + + + + + Reviewer + + + + + Endorser + + + + + + + The type of contributor. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + For referring to data content defined in other formats. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + Identifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate. + + + + + The human language of the content. The value can be any valid value according to BCP 47. + + + + + The actual data of the attachment - a sequence of bytes, base64 encoded. + + + + + A location where the data can be accessed. + + + + + The number of bytes of data that make up this attachment (before base64 encoding, if that is done). + + + + + The calculated hash of the data using SHA-1. Represented using base64. + + + + + A label or set of text to display in place of the data. + + + + + The date that the attachment was first created. + + + + + + + + + A measured amount (or an amount that can potentially be measured). Note that measured amounts include amounts that are not precisely quantified, including amounts involving arbitrary units and floating currencies. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + + + + + Describes a required data item for evaluation in terms of the type of data, and optional code or date-based filters of the data. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The type of the required data, specified as the type name of a resource. For profiles, this value is set to the type of the base resource of the profile. + + + + + The profile of the required data, specified as the uri of the profile definition. + + + + + The intended subjects of the data requirement. If this element is not provided, a Patient subject is assumed. + + + + + + + Indicates that specific elements of the type are referenced by the knowledge module and must be supported by the consumer in order to obtain an effective evaluation. This does not mean that a value is required for this element, only that the consuming system must understand the element and be able to provide values for it if they are available. + +The value of mustSupport SHALL be a FHIRPath resolveable on the type of the DataRequirement. The path SHALL consist only of identifiers, constant indexers, and .resolve() (see the [Simple FHIRPath Profile](fhirpath.html#simple) for full details). + + + + + Code filters specify additional constraints on the data, specifying the value set of interest for a particular element of the data. Each code filter defines an additional constraint on the data, i.e. code filters are AND'ed, not OR'ed. + + + + + Date filters specify additional constraints on the data in terms of the applicable date range for specific elements. Each date filter specifies an additional constraint on the data, i.e. date filters are AND'ed, not OR'ed. + + + + + Specifies a maximum number of results that are required (uses the _count search parameter). + + + + + Specifies the order of the results to be returned. + + + + + + + + + Describes a required data item for evaluation in terms of the type of data, and optional code or date-based filters of the data. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The code-valued attribute of the filter. The specified path SHALL be a FHIRPath resolveable on the specified type of the DataRequirement, and SHALL consist only of identifiers, constant indexers, and .resolve(). The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements (see the [Simple FHIRPath Profile](fhirpath.html#simple) for full details). Note that the index must be an integer constant. The path must resolve to an element of type code, Coding, or CodeableConcept. + + + + + A token parameter that refers to a search parameter defined on the specified type of the DataRequirement, and which searches on elements of type code, Coding, or CodeableConcept. + + + + + The valueset for the code filter. The valueSet and code elements are additive. If valueSet is specified, the filter will return only those data items for which the value of the code-valued element specified in the path is a member of the specified valueset. + + + + + The codes for the code filter. If values are given, the filter will return only those data items for which the code-valued attribute specified by the path has a value that is one of the specified codes. If codes are specified in addition to a value set, the filter returns items matching a code in the value set or one of the specified codes. + + + + + + + + + Describes a required data item for evaluation in terms of the type of data, and optional code or date-based filters of the data. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The date-valued attribute of the filter. The specified path SHALL be a FHIRPath resolveable on the specified type of the DataRequirement, and SHALL consist only of identifiers, constant indexers, and .resolve(). The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements (see the [Simple FHIRPath Profile](fhirpath.html#simple) for full details). Note that the index must be an integer constant. The path must resolve to an element of type date, dateTime, Period, Schedule, or Timing. + + + + + A date parameter that refers to a search parameter defined on the specified type of the DataRequirement, and which searches on elements of type date, dateTime, Period, Schedule, or Timing. + + + + + The value of the filter. If period is specified, the filter will return only those data items that fall within the bounds determined by the Period, inclusive of the period boundaries. If dateTime is specified, the filter will return only those data items that are equal to the specified dateTime. If a Duration is specified, the filter will return only those data items that fall within Duration before now. + + + + + + + + + + + + Describes a required data item for evaluation in terms of the type of data, and optional code or date-based filters of the data. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The attribute of the sort. The specified path must be resolvable from the type of the required data. The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements. Note that the index must be an integer constant. + + + + + The direction of the sort, ascending or descending. + + + + + + + + + + + Ascending + + + + + Descending + + + + + + + The possible sort directions, ascending or descending. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Indicates how the medication is/was taken or should be taken by the patient. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + Indicates the order in which the dosage instructions should be applied or interpreted. + + + + + Free text dosage instructions e.g. SIG. + + + + + Supplemental instructions to the patient on how to take the medication (e.g. "with meals" or"take half to one hour before food") or warnings for the patient about the medication (e.g. "may cause drowsiness" or "avoid exposure of skin to direct sunlight or sunlamps"). + + + + + Instructions in terms that are understood by the patient or consumer. + + + + + When medication should be administered. + + + + + Indicates whether the Medication is only taken when needed within a specific dosing schedule (Boolean option), or it indicates the precondition for taking the Medication (CodeableConcept). + + + + + + + Body site to administer to. + + + + + How drug should enter body. + + + + + Technique for administering medication. + + + + + The amount of medication administered. + + + + + Upper limit on medication per unit of time. + + + + + Upper limit on medication per administration. + + + + + Upper limit on medication per lifetime of the patient. + + + + + + + + + Indicates how the medication is/was taken or should be taken by the patient. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The kind of dose or rate specified, for example, ordered or calculated. + + + + + Amount of medication per dose. + + + + + + + Amount of medication per unit of time. + + + + + + + + + + + + An amount of economic utility in some recognized currency. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + Numerical value (with implicit precision). + + + + + ISO 4217 Currency Code. + + + + + + + + + A human's name with the ability to identify parts and usage. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + Identifies the purpose for this name. + + + + + Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts. + + + + + The part of a name that links to the genealogy. In some cultures (e.g. Eritrea) the family name of a son is the first name of his father. + + + + + Given name. + + + + + Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the start of the name. + + + + + Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the end of the name. + + + + + Indicates the period of time when this name was valid for the named person. + + + + + + + + + + + Usual + + + + + Official + + + + + Temp + + + + + Nickname + + + + + Anonymous + + + + + Old + + + + + Name changed for Marriage + + + + + + + The use of a human name. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + Telecommunications form for contact point - what communications system is required to make use of the contact. + + + + + The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address). + + + + + Identifies the purpose for the contact point. + + + + + Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values. + + + + + Time period when the contact point was/is in use. + + + + + + + + + + + Phone + + + + + Fax + + + + + Email + + + + + Pager + + + + + URL + + + + + SMS + + + + + Other + + + + + + + Telecommunications form for contact point. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Home + + + + + Work + + + + + Temp + + + + + Old + + + + + Mobile + + + + + + + Use of contact point. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + The marketing status describes the date when a medicinal product is actually put on the market or the date as of which it is no longer available. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The country in which the marketing authorisation has been granted shall be specified It should be specified using the ISO 3166 ‑ 1 alpha-2 code elements. + + + + + Where a Medicines Regulatory Agency has granted a marketing authorisation for which specific provisions within a jurisdiction apply, the jurisdiction can be specified using an appropriate controlled terminology The controlled term and the controlled term identifier shall be specified. + + + + + This attribute provides information on the status of the marketing of the medicinal product See ISO/TS 20443 for more information and examples. + + + + + The date when the Medicinal Product is placed on the market by the Marketing Authorisation Holder (or where applicable, the manufacturer/distributor) in a country and/or jurisdiction shall be provided A complete date consisting of day, month and year shall be specified using the ISO 8601 date format NOTE “Placed on the market” refers to the release of the Medicinal Product into the distribution chain. + + + + + The date when the Medicinal Product is placed on the market by the Marketing Authorisation Holder (or where applicable, the manufacturer/distributor) in a country and/or jurisdiction shall be provided A complete date consisting of day, month and year shall be specified using the ISO 8601 date format NOTE “Placed on the market” refers to the release of the Medicinal Product into the distribution chain. + + + + + + + + + An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The purpose of this identifier. + + + + + A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. + + + + + Establishes the namespace for the value - that is, a URL that describes a set values that are unique. + + + + + The portion of the identifier typically relevant to the user and which is unique within the context of the system. + + + + + Time period during which identifier is/was valid for use. + + + + + Organization that issued/manages the identifier. + + + + + + + + + + + Usual + + + + + Official + + + + + Temp + + + + + Secondary + + + + + Old + + + + + + + Identifies the purpose for this identifier, if known . + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Chemical substances are a single substance type whose primary defining element is the molecular structure. Chemical substances shall be defined on the basis of their complete covalent molecular structure; the presence of a salt (counter-ion) and/or solvates (water, alcohols) is also captured. Purity, grade, physical form or particle size are not taken into account in the definition of a chemical substance or in the assignment of a Substance ID. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + Used to capture quantitative values for a variety of elements. If only limits are given, the arithmetic mean would be the average. If only a single definite value for a given element is given, it would be captured in this field. + + + + + + + + Most elements that require a quantitative value will also have a field called amount type. Amount type should always be specified because the actual value of the amount is often dependent on it. EXAMPLE: In capturing the actual relative amounts of substances or molecular fragments it is essential to indicate whether the amount refers to a mole ratio or weight ratio. For any given element an effort should be made to use same the amount type for all related definitional elements. + + + + + A textual comment on a numeric value. + + + + + Reference range of possible or expected values. + + + + + + + + + Chemical substances are a single substance type whose primary defining element is the molecular structure. Chemical substances shall be defined on the basis of their complete covalent molecular structure; the presence of a salt (counter-ion) and/or solvates (water, alcohols) is also captured. Purity, grade, physical form or particle size are not taken into account in the definition of a chemical substance or in the assignment of a Substance ID. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + Lower limit possible or expected. + + + + + Upper limit possible or expected. + + + + + + + + + A reference to a code defined by a terminology system. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The identification of the code system that defines the meaning of the symbol in the code. + + + + + 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. + + + + + 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). + + + + + A representation of the meaning of the code in the system, following the rules of the system. + + + + + Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). + + + + + + + + + A series of measurements taken by a device, with upper and lower limits. There may be more than one dimension in the data. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The base quantity that a measured value of zero represents. In addition, this provides the units of the entire measurement series. + + + + + The length of time between sampling times, measured in milliseconds. + + + + + A correction factor that is applied to the sampled data points before they are added to the origin. + + + + + The lower limit of detection of the measured points. This is needed if any of the data points have the value "L" (lower than detection limit). + + + + + The upper limit of detection of the measured points. This is needed if any of the data points have the value "U" (higher than detection limit). + + + + + The number of sample points at each time point. If this value is greater than one, then the dimensions will be interlaced - all the sample points for a point in time will be recorded at once. + + + + + A series of data points which are decimal values separated by a single space (character u20). The special values "E" (error), "L" (below detection limit) and "U" (above detection limit) can also be used in place of a decimal value. + + + + + + + + + + + + + + + + + + + + + + A populatioof people with some set of grouping criteria. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The age of the specific population. + + + + + + + The gender of the specific population. + + + + + Race of the specific population. + + + + + The existing physiological conditions of the specific population to which this applies. + + + + + + + + + A relationship of two Quantity values - expressed as a numerator and a denominator. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The value of the numerator. + + + + + The value of the denominator. + + + + + + + + + A length - a value with a unit that is a physical distance. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + + + + + A duration of time during which an organism (or a process) has existed. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + + + + + A reference from one resource to another. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. + + + + + The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. + +The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). + + + + + An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. + + + + + Plain text narrative that identifies the resource in addition to the resource reference. + + + + + + + + + A description of a triggering event. Triggering events can be named events, data events, or periodic, as determined by the type element. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The type of triggering event. + + + + + A formal name for the event. This may be an absolute URI that identifies the event formally (e.g. from a trigger registry), or a simple relative URI that identifies the event in a local context. + + + + + The timing of the event (if this is a periodic trigger). + + + + + + + + + The triggering data of the event (if this is a data trigger). If more than one data is requirement is specified, then all the data requirements must be true. + + + + + A boolean-valued expression that is evaluated in the context of the container of the trigger definition and returns whether or not the trigger fires. + + + + + + + + + + + Named Event + + + + + Periodic + + + + + Data Changed + + + + + Data Added + + + + + Data Updated + + + + + Data Removed + + + + + Data Accessed + + + + + Data Access Ended + + + + + + + The type of trigger. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A measured amount (or an amount that can potentially be measured). Note that measured amounts include amounts that are not precisely quantified, including amounts involving arbitrary units and floating currencies. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The value of the measured amount. The value includes an implicit precision in the presentation of the value. + + + + + How the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues; e.g. if the comparator is "<" , then the real value is < stated value. + + + + + A human-readable form of the unit. + + + + + The identification of the system that provides the coded form of the unit. + + + + + A computer processable form of the unit in some unit representation system. + + + + + + + + + + + Less than + + + + + Less or Equal to + + + + + Greater or Equal to + + + + + Greater than + + + + + + + How the Quantity should be understood and represented. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A time period defined by a start and end date and optionally time. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The start of the period. The boundary is inclusive. + + + + + The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. + + + + + + + + + A length of time. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + + + + + A set of ordered Quantities defined by a low and high limit. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The low limit. The boundary is inclusive. + + + + + The high limit. The boundary is inclusive. + + + + + + + + + Related artifacts such as additional documentation, justification, or bibliographic references. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The type of relationship to the related artifact. + + + + + A short label that can be used to reference the citation from elsewhere in the containing artifact, such as a footnote index. + + + + + A brief description of the document or knowledge resource being referenced, suitable for display to a consumer. + + + + + A bibliographic citation for the related artifact. This text SHOULD be formatted according to an accepted citation format. + + + + + A url for the artifact that can be followed to access the actual content. + + + + + The document being referenced, represented as an attachment. This is exclusive with the resource element. + + + + + The related resource, such as a library, value set, profile, or other knowledge resource. + + + + + + + + + + + Documentation + + + + + Justification + + + + + Citation + + + + + Predecessor + + + + + Successor + + + + + Derived From + + + + + Depends On + + + + + Composed Of + + + + + + + The type of relationship to the related artifact. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A text note which also contains information about who made the statement and when. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The individual responsible for making the annotation. + + + + + + + Indicates when this particular annotation was made. + + + + + The text of the annotation in markdown format. + + + + + + + + + The shelf-life and storage information for a medicinal product item or container can be described using this class. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + Unique identifier for the packaged Medicinal Product. + + + + + This describes the shelf life, taking into account various scenarios such as shelf life of the packaged Medicinal Product itself, shelf life after transformation where necessary and shelf life after the first opening of a bottle, etc. The shelf life type shall be specified using an appropriate controlled vocabulary The controlled term and the controlled term identifier shall be specified. + + + + + The shelf life time period can be specified using a numerical value for the period of time and its unit of time measurement The unit of measurement shall be specified in accordance with ISO 11240 and the resulting terminology The symbol and the symbol identifier shall be used. + + + + + Special precautions for storage, if any, can be specified using an appropriate controlled vocabulary The controlled term and the controlled term identifier shall be specified. + + + + + + + + + Specifies contact information for a person or organization. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The name of an individual to contact. + + + + + The contact details for the individual (if a name was provided) or the organization. + + + + + + + + + Specifies clinical/business/etc. metadata that can be used to retrieve, index and/or categorize an artifact. This metadata can either be specific to the applicable population (e.g., age category, DRG) or the specific context of care (e.g., venue, care setting, provider of care). + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + A code that identifies the type of context being specified by this usage context. + + + + + A value that defines the context specified in this context of use. The interpretation of the value is defined by the code. + + + + + + + + + + + + + A expression that is evaluated in a specified context and returns a value. The context of use of the expression must specify the context in which the expression is evaluated, and how the result of the expression is used. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + A brief, natural language description of the condition that effectively communicates the intended semantics. + + + + + A short name assigned to the expression to allow for multiple reuse of the expression in the context where it is defined. + + + + + The media type of the language for the expression. + + + + + An expression in the specified language that returns a value. + + + + + A URI that defines where the expression is found. + + + + + + + + + + + CQL + + + + + FHIRPath + + + + + FHIR Query + + + + + + + The media type of the expression language. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A signature along with supporting context. The signature may be a digital signature that is cryptographic in nature, or some other signature acceptable to the domain. This other signature may be as simple as a graphical image representing a hand-written signature, or a signature ceremony Different signature approaches have different utilities. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + An indication of the reason that the entity signed this document. This may be explicitly included as part of the signature information and can be used when determining accountability for various actions concerning the document. + + + + + When the digital signature was signed. + + + + + A reference to an application-usable description of the identity that signed (e.g. the signature used their private key). + + + + + A reference to an application-usable description of the identity that is represented by the signature. + + + + + A mime type that indicates the technical format of the target resources signed by the signature. + + + + + A mime type that indicates the technical format of the signature. Important mime types are application/signature+xml for X ML DigSig, application/jose for JWS, and image/* for a graphical image of a signature, etc. + + + + + The base64 encoding of the Signature content. When signature is not recorded electronically this element would be empty. + + + + + + + + + Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + Identifies specific times when the event occurs. + + + + + A set of rules that describe when the event is scheduled. + + + + + A code for the timing schedule (or just text in code.text). Some codes such as BID are ubiquitous, but many institutions define their own additional codes. If a code is provided, the code is understood to be a complete statement of whatever is specified in the structured timing data, and either the code or the data may be used to interpret the Timing, with the exception that .repeat.bounds still applies over the code (and is not contained in the code). + + + + + + + + + Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + Either a duration for the length of the timing schedule, a range of possible length, or outer bounds for start and/or end limits of the timing schedule. + + + + + + + + A total count of the desired number of repetitions across the duration of the entire timing specification. If countMax is present, this element indicates the lower bound of the allowed range of count values. + + + + + If present, indicates that the count is a range - so to perform the action between [count] and [countMax] times. + + + + + How long this thing happens for when it happens. If durationMax is present, this element indicates the lower bound of the allowed range of the duration. + + + + + If present, indicates that the duration is a range - so to perform the action between [duration] and [durationMax] time length. + + + + + The units of time for the duration, in UCUM units. + + + + + The number of times to repeat the action within the specified period. If frequencyMax is present, this element indicates the lower bound of the allowed range of the frequency. + + + + + If present, indicates that the frequency is a range - so to repeat between [frequency] and [frequencyMax] times within the period or period range. + + + + + Indicates the duration of time over which repetitions are to occur; e.g. to express "3 times per day", 3 would be the frequency and "1 day" would be the period. If periodMax is present, this element indicates the lower bound of the allowed range of the period length. + + + + + If present, indicates that the period is a range from [period] to [periodMax], allowing expressing concepts such as "do this once every 3-5 days. + + + + + The units of time for the period in UCUM units. + + + + + If one or more days of week is provided, then the action happens only on the specified day(s). + + + + + Specified time of day for action to take place. + + + + + An approximate time period during the day, potentially linked to an event of daily living that indicates when the action should occur. + + + + + The number of minutes from the event. If the event code does not indicate whether the minutes is before or after the event, then the offset is assumed to be after the event. + + + + + + + + + + + 秒 + + + + + 分钟 + + + + + 小时 + + + + + 天 + + + + + 星期 + + + + + 月 + + + + + 年 + + + + + + + A unit of time (units from UCUM). + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Morning + + + + + Early Morning + + + + + Late Morning + + + + + Noon + + + + + Afternoon + + + + + Early Afternoon + + + + + Late Afternoon + + + + + Evening + + + + + Early Evening + + + + + Late Evening + + + + + Night + + + + + After Sleep + + + + + HS + + + + + WAKE + + + + + C + + + + + CM + + + + + CD + + + + + CV + + + + + AC + + + + + ACM + + + + + ACD + + + + + ACV + + + + + PC + + + + + PCM + + + + + PCD + + + + + PCV + + + + + + + Real world event relating to the schedule. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + The marketing status describes the date when a medicinal product is actually put on the market or the date as of which it is no longer available. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + Where applicable, the height can be specified using a numerical value and its unit of measurement The unit of measurement shall be specified in accordance with ISO 11240 and the resulting terminology The symbol and the symbol identifier shall be used. + + + + + Where applicable, the width can be specified using a numerical value and its unit of measurement The unit of measurement shall be specified in accordance with ISO 11240 and the resulting terminology The symbol and the symbol identifier shall be used. + + + + + Where applicable, the depth can be specified using a numerical value and its unit of measurement The unit of measurement shall be specified in accordance with ISO 11240 and the resulting terminology The symbol and the symbol identifier shall be used. + + + + + Where applicable, the weight can be specified using a numerical value and its unit of measurement The unit of measurement shall be specified in accordance with ISO 11240 and the resulting terminology The symbol and the symbol identifier shall be used. + + + + + Where applicable, the nominal volume can be specified using a numerical value and its unit of measurement The unit of measurement shall be specified in accordance with ISO 11240 and the resulting terminology The symbol and the symbol identifier shall be used. + + + + + Where applicable, the external diameter can be specified using a numerical value and its unit of measurement The unit of measurement shall be specified in accordance with ISO 11240 and the resulting terminology The symbol and the symbol identifier shall be used. + + + + + Where applicable, the shape can be specified An appropriate controlled vocabulary shall be used The term and the term identifier shall be used. + + + + + Where applicable, the color can be specified An appropriate controlled vocabulary shall be used The term and the term identifier shall be used. + + + + + Where applicable, the imprint can be specified as text. + + + + + Where applicable, the image can be provided The format of the image attachment shall be specified by regional implementations. + + + + + Where applicable, the scoring can be specified An appropriate controlled vocabulary shall be used The term and the term identifier shall be used. + + + + + + + + + A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + A reference to a code defined by a terminology system. + + + + + A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. + + + + + + + + + The parameters to the module. This collection specifies both the input and output parameters. Input parameters are provided by the caller as part of the $evaluate operation. Output parameters are included in the GuidanceResponse. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The name of the parameter used to allow access to the value of the parameter in evaluation contexts. + + + + + Whether the parameter is input or output for the module. + + + + + The minimum number of times this parameter SHALL appear in the request or response. + + + + + The maximum number of times this element is permitted to appear in the request or response. + + + + + A brief discussion of what the parameter is for and how it is used by the module. + + + + + The type of the parameter. + + + + + If specified, this indicates a profile that the input data must conform to, or that the output data will conform to. + + + + + + + + + Captures constraints on each element within the resource, profile, or extension. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The path identifies the element and is expressed as a "."-separated list of ancestor elements, beginning with the name of the resource or extension. + + + + + Codes that define how this element is represented in instances, when the deviation varies from the normal case. + + + + + The name of this element definition slice, when slicing is working. The name must be a token with no dots or spaces. This is a unique name referring to a specific set of constraints applied to this element, used to provide a name to different slices of the same element. + + + + + If true, indicates that this slice definition is constraining a slice definition with the same name in an inherited profile. If false, the slice is not overriding any slice in an inherited profile. If missing, the slice might or might not be overriding a slice in an inherited profile, depending on the sliceName. + + + + + A single preferred label which is the text to display beside the element indicating its meaning or to use to prompt for the element in a user display or form. + + + + + A code that has the same meaning as the element in a particular terminology. + + + + + Indicates that the element is sliced into a set of alternative definitions (i.e. in a structure definition, there are multiple different constraints on a single element in the base resource). Slicing can be used in any resource that has cardinality ..* on the base resource, or any resource with a choice of types. The set of slices is any elements that come after this in the element sequence that have the same path, until a shorter path occurs (the shorter path terminates the set). + + + + + A concise description of what this element means (e.g. for use in autogenerated summaries). + + + + + Provides a complete explanation of the meaning of the data element for human readability. For the case of elements derived from existing elements (e.g. constraints), the definition SHALL be consistent with the base definition, but convey the meaning of the element in the particular context of use of the resource. (Note: The text you are reading is specified in ElementDefinition.definition). + + + + + Explanatory notes and implementation guidance about the data element, including notes about how to use the data properly, exceptions to proper use, etc. (Note: The text you are reading is specified in ElementDefinition.comment). + + + + + This element is for traceability of why the element was created and why the constraints exist as they do. This may be used to point to source materials or specifications that drove the structure of this element. + + + + + Identifies additional names by which this element might also be known. + + + + + The minimum number of times this element SHALL appear in the instance. + + + + + The maximum number of times this element is permitted to appear in the instance. + + + + + Information about the base definition of the element, provided to make it unnecessary for tools to trace the deviation of the element through the derived and related profiles. When the element definition is not the original definition of an element - i.g. either in a constraint on another type, or for elements from a super type in a snap shot - then the information in provided in the element definition may be different to the base definition. On the original definition of the element, it will be same. + + + + + Identifies an element defined elsewhere in the definition whose content rules should be applied to the current element. ContentReferences bring across all the rules that are in the ElementDefinition for the element, including definitions, cardinality constraints, bindings, invariants etc. + + + + + The data type or resource that the value of this element is permitted to be. + + + + + The value that should be used if there is no value stated in the instance (e.g. 'if not otherwise specified, the abstract is false'). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The Implicit meaning that is to be understood when this element is missing (e.g. 'when this element is missing, the period is ongoing'). + + + + + If present, indicates that the order of the repeating element has meaning and describes what that meaning is. If absent, it means that the order of the element has no meaning. + + + + + Specifies a value that SHALL be exactly the value for this element in the instance. For purposes of comparison, non-significant whitespace is ignored, and all values must be an exact match (case and accent sensitive). Missing elements/attributes must also be missing. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Specifies a value that the value in the instance SHALL follow - that is, any value in the pattern must be found in the instance. Other additional values may be found too. This is effectively constraint by example. + +When pattern[x] is used to constrain a primitive, it means that the value provided in the pattern[x] must match the instance value exactly. + +When pattern[x] is used to constrain an array, it means that each element provided in the pattern[x] array must (recursively) match at least one element from the instance array. + +When pattern[x] is used to constrain a complex object, it means that each property in the pattern must be present in the complex object, and its value must recursively match -- i.e., + +1. If primitive: it must match exactly the pattern value +2. If a complex object: it must match (recursively) the pattern value +3. If an array: it must match (recursively) the pattern value. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A sample value for this element demonstrating the type of information that would typically be found in the element. + + + + + The minimum allowed value for the element. The value is inclusive. This is allowed for the types date, dateTime, instant, time, decimal, integer, and Quantity. + + + + + + + + + + + + + + The maximum allowed value for the element. The value is inclusive. This is allowed for the types date, dateTime, instant, time, decimal, integer, and Quantity. + + + + + + + + + + + + + + Indicates the maximum length in characters that is permitted to be present in conformant instances and which is expected to be supported by conformant consumers that support the element. + + + + + A reference to an invariant that may make additional statements about the cardinality or value in the instance. + + + + + Formal constraints such as co-occurrence and other constraints that can be computationally evaluated within the context of the instance. + + + + + If true, implementations that produce or consume resources SHALL provide "support" for the element in some meaningful way. If false, the element may be ignored and not supported. If false, whether to populate or use the data element in any way is at the discretion of the implementation. + + + + + If true, the value of this element affects the interpretation of the element or resource that contains it, and the value of the element cannot be ignored. Typically, this is used for status, negation and qualification codes. The effect of this is that the element cannot be ignored by systems: they SHALL either recognize the element and process it, and/or a pre-determination has been made that it is not relevant to their particular system. + + + + + Explains how that element affects the interpretation of the resource or element that contains it. + + + + + Whether the element should be included if a client requests a search with the parameter _summary=true. + + + + + Binds to a value set if this element is coded (code, Coding, CodeableConcept, Quantity), or the data types (string, uri). + + + + + Identifies a concept from an external specification that roughly corresponds to this element. + + + + + + + + + Captures constraints on each element within the resource, profile, or extension. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + Allows identification of which elements have their cardinalities impacted by the constraint. Will not be referenced for constraints that do not affect cardinality. + + + + + Description of why this constraint is necessary or appropriate. + + + + + Identifies the impact constraint violation has on the conformance of the instance. + + + + + Text that can be used to describe the constraint in messages identifying that the constraint has been violated. + + + + + A [FHIRPath](fhirpath.html) expression of constraint that can be executed to see if this constraint is met. + + + + + An XPath expression of constraint that can be executed to see if this constraint is met. + + + + + A reference to the original source of the constraint, for traceability purposes. + + + + + + + + + Captures constraints on each element within the resource, profile, or extension. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + An internal reference to the definition of a mapping. + + + + + Identifies the computable language in which mapping.map is expressed. + + + + + Expresses what part of the target specification corresponds to this element. + + + + + Comments that provide information about the mapping or its use. + + + + + + + + + Captures constraints on each element within the resource, profile, or extension. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + The Path that identifies the base element - this matches the ElementDefinition.path for that element. Across FHIR, there is only one base definition of any element - that is, an element definition on a [[[StructureDefinition]]] without a StructureDefinition.base. + + + + + Minimum cardinality of the base element identified by the path. + + + + + Maximum cardinality of the base element identified by the path. + + + + + + + + + Captures constraints on each element within the resource, profile, or extension. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + URL of Data type or Resource that is a(or the) type used for this element. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition e.g. "string" is a reference to http://hl7.org/fhir/StructureDefinition/string. Absolute URLs are only allowed in logical models. + + + + + Identifies a profile structure or implementation Guide that applies to the datatype this element refers to. If any profiles are specified, then the content must conform to at least one of them. The URL can be a local reference - to a contained StructureDefinition, or a reference to another StructureDefinition or Implementation Guide by a canonical URL. When an implementation guide is specified, the type SHALL conform to at least one profile defined in the implementation guide. + + + + + Used when the type is "Reference" or "canonical", and identifies a profile structure or implementation Guide that applies to the target of the reference this element refers to. If any profiles are specified, then the content must conform to at least one of them. The URL can be a local reference - to a contained StructureDefinition, or a reference to another StructureDefinition or Implementation Guide by a canonical URL. When an implementation guide is specified, the target resource SHALL conform to at least one profile defined in the implementation guide. + + + + + If the type is a reference to another resource, how the resource is or can be aggregated - is it a contained resource, or a reference, and if the context is a bundle, is it included in the bundle. + + + + + Whether this reference needs to be version specific or version independent, or whether either can be used. + + + + + + + + + Captures constraints on each element within the resource, profile, or extension. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + Describes the purpose of this example amoung the set of examples. + + + + + The actual value for the element, which must be one of the types allowed for this element. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Captures constraints on each element within the resource, profile, or extension. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + Designates which child elements are used to discriminate between the slices when processing an instance. If one or more discriminators are provided, the value of the child elements in the instance data SHALL completely distinguish which slice the element in the resource matches based on the allowed values for those elements in each of the slices. + + + + + A human-readable text description of how the slicing works. If there is no discriminator, this is required to be present to provide whatever information is possible about how the slices can be differentiated. + + + + + If the matching elements have to occur in the same order as defined in the profile. + + + + + Whether additional slices are allowed or not. When the slices are ordered, profile authors can also say that additional slices are only allowed at the end. + + + + + + + + + Captures constraints on each element within the resource, profile, or extension. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + Indicates the degree of conformance expectations associated with this binding - that is, the degree to which the provided value set must be adhered to in the instances. + + + + + Describes the intended use of this particular set of codes. + + + + + Refers to the value set that identifies the set of codes the binding refers to. + + + + + + + + + Captures constraints on each element within the resource, profile, or extension. + If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions + + + + + + + How the element value is interpreted when discrimination is evaluated. + + + + + A FHIRPath expression, using [the simple subset of FHIRPath](fhirpath.html#simple), that is used to identify the element on which discrimination is based. + + + + + + + + + + + XML Attribute + + + + + XML Text + + + + + Type Attribute + + + + + CDA Text Format + + + + + XHTML + + + + + + + How a property is represented when serialized. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Error + + + + + Warning + + + + + + + SHALL applications comply with this constraint? + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Contained + + + + + Referenced + + + + + Bundled + + + + + + + How resource references can be aggregated. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Either Specific or independent + + + + + Version independent + + + + + Version Specific + + + + + + + Whether a reference needs to be version specific or version independent, or whether either can be used. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Closed + + + + + Open + + + + + Open at End + + + + + + + How slices are interpreted when evaluating an instance. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Required + + + + + Extensible + + + + + Preferred + + + + + Example + + + + + + + Indication of the degree of conformance expectations associated with a binding. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Value + + + + + Exists + + + + + Pattern + + + + + Type + + + + + Profile + + + + + + + How an element value is interpreted when discrimination is evaluated. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A resource that includes narrative, extensions, and contained resources. + + + + + + + A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. + + + + + These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. + + + + + May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. + + + + + May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. + +Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). + + + + + + + + + This is the base resource type for everything. + + + + + The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. + + + + + The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. + + + + + A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. + + + + + The base language in which the resource is written. + + + + + + + + + Draft + черновик + ontwerp + + + + + Active + активный + actief + + + + + Retired + удалён + verouderd + + + + + Unknown + + + + + + + + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Number + + + + + Date/DateTime + + + + + String + + + + + Token + + + + + Reference + + + + + Composite + + + + + Quantity + + + + + URI + + + + + Special + + + + + + + + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Male + + + + + Female + + + + + Other + + + + + Unknown + + + + + + + + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + 0.01 + + + + + 0.05 + + + + + 0.06 + + + + + 0.11 + + + + + 0.0.80 + + + + + 0.0.81 + + + + + 0.0.82 + + + + + 0.4.0 + + + + + 0.5.0 + + + + + 1.0.0 + + + + + 1.0.1 + + + + + 1.0.2 + + + + + 1.1.0 + + + + + 1.4.0 + + + + + 1.6.0 + + + + + 1.8.0 + + + + + 3.0.0 + + + + + 3.0.1 + + + + + 3.3.0 + + + + + 3.5.0 + + + + + 4.0.0 + + + + + + + + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Display + + + + + Print (Form) + + + + + Print (Operator) + + + + + + + + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Queued + + + + + Processing Complete + + + + + Error + + + + + Partial Processing + + + + + + + + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Related To + + + + + Equivalent + + + + + Equal + + + + + Wider + + + + + Subsumes + + + + + Narrower + + + + + Specializes + + + + + Inexact + + + + + Unmatched + + + + + Disjoint + + + + + + + + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Current + + + + + Superseded + + + + + Entered in Error + + + + + + + + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A financial tool for tracking value accrued for a particular purpose. In the healthcare field, used to track charges for a patient, cost centers, etc. + + + + + A financial tool for tracking value accrued for a particular purpose. In the healthcare field, used to track charges for a patient, cost centers, etc. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Unique identifier used to reference the account. Might or might not be intended for human use (e.g. credit card number). + + + + + Indicates whether the account is presently used/usable or not. + + + + + Categorizes the account for reporting and searching purposes. + + + + + Name used for the account when displaying it to humans in reports, etc. + + + + + Identifies the entity which incurs the expenses. While the immediate recipients of services or goods might be entities related to the subject, the expenses were ultimately incurred by the subject of the Account. + + + + + The date range of services associated with this account. + + + + + The party(s) that are responsible for covering the payment of this account, and what order should they be applied to the account. + + + + + Indicates the service area, hospital, department, etc. with responsibility for managing the Account. + + + + + Provides additional information about what the account tracks and how it is used. + + + + + The parties responsible for balancing the account if other payment options fall short. + + + + + Reference to a parent Account. + + + + + + + + + A financial tool for tracking value accrued for a particular purpose. In the healthcare field, used to track charges for a patient, cost centers, etc. + + + + + + + The party(s) that contribute to payment (or part of) of the charges applied to this account (including self-pay). + +A coverage may only be responsible for specific types of charges, and the sequence of the coverages in the account could be important when processing billing. + + + + + The priority of the coverage in the context of this account. + + + + + + + + + A financial tool for tracking value accrued for a particular purpose. In the healthcare field, used to track charges for a patient, cost centers, etc. + + + + + + + The entity who is responsible. + + + + + A guarantor may be placed on credit hold or otherwise have their role temporarily suspended. + + + + + The timeframe during which the guarantor accepts responsibility for the account. + + + + + + + + + + + Active + + + + + Inactive + + + + + Entered in error + + + + + On Hold + + + + + Unknown + + + + + + + Indicates whether the account is available to be used. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + This resource allows for the definition of some activity to be performed, independent of a particular patient, practitioner, or other performance context. + + + + + This resource allows for the definition of some activity to be performed, independent of a particular patient, practitioner, or other performance context. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this activity definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this activity definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the activity definition is stored on different servers. + + + + + A formal identifier that is used to identify this activity definition when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the activity definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the activity definition 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. To provide a version consistent with the Decision Support Service specification, use the format Major.Minor.Revision (e.g. 1.0.0). For more information on versioning knowledge assets, refer to the Decision Support Service specification. Note that a version is required for non-experimental active assets. + + + + + A natural language name identifying the activity definition. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the activity definition. + + + + + An explanatory or alternate title for the activity definition giving additional information about its content. + + + + + The status of this activity definition. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this activity definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + A code or group definition that describes the intended subject of the activity being defined. + + + + + + + The date (and optionally time) when the activity definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the activity definition changes. + + + + + The name of the organization or individual that published the activity definition. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the activity definition from a consumer's perspective. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate activity definition instances. + + + + + A legal or geographic region in which the activity definition is intended to be used. + + + + + Explanation of why this activity definition is needed and why it has been designed as it has. + + + + + A detailed description of how the activity definition is used from a clinical perspective. + + + + + A copyright statement relating to the activity definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the activity definition. + + + + + The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. + + + + + The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. + + + + + The period during which the activity definition content was or is planned to be in active use. + + + + + Descriptive topics related to the content of the activity. Topics provide a high-level categorization of the activity that can be useful for filtering and searching. + + + + + An individiual or organization primarily involved in the creation and maintenance of the content. + + + + + An individual or organization primarily responsible for internal coherence of the content. + + + + + An individual or organization primarily responsible for review of some aspect of the content. + + + + + An individual or organization responsible for officially endorsing the content for use in some setting. + + + + + Related artifacts such as additional documentation, justification, or bibliographic references. + + + + + A reference to a Library resource containing any formal logic used by the activity definition. + + + + + A description of the kind of resource the activity definition is representing. For example, a MedicationRequest, a ServiceRequest, or a CommunicationRequest. Typically, but not always, this is a Request resource. + + + + + A profile to which the target of the activity definition is expected to conform. + + + + + Detailed description of the type of activity; e.g. What lab test, what procedure, what kind of encounter. + + + + + Indicates the level of authority/intentionality associated with the activity and where the request should fit into the workflow chain. + + + + + Indicates how quickly the activity should be addressed with respect to other requests. + + + + + Set this to true if the definition is to indicate that a particular activity should NOT be performed. If true, this element should be interpreted to reinforce a negative coding. For example NPO as a code with a doNotPerform of true would still indicate to NOT perform the action. + + + + + The period, timing or frequency upon which the described activity is to occur. + + + + + + + + + + + Identifies the facility where the activity will occur; e.g. home, hospital, specific clinic, etc. + + + + + Indicates who should participate in performing the action described. + + + + + Identifies the food, drug or other product being consumed or supplied in the activity. + + + + + + + Identifies the quantity expected to be consumed at once (per dose, per meal, etc.). + + + + + Provides detailed dosage instructions in the same way that they are described for MedicationRequest resources. + + + + + Indicates the sites on the subject's body where the procedure should be performed (I.e. the target sites). + + + + + Defines specimen requirements for the action to be performed, such as required specimens for a lab test. + + + + + Defines observation requirements for the action to be performed, such as body weight or surface area. + + + + + Defines the observations that are expected to be produced by the action. + + + + + A reference to a StructureMap resource that defines a transform that can be executed to produce the intent resource using the ActivityDefinition instance as the input. + + + + + Dynamic values that will be evaluated to produce values for elements of the resulting resource. For example, if the dosage of a medication must be computed based on the patient's weight, a dynamic value would be used to specify an expression that calculated the weight, and the path on the request resource that would contain the result. + + + + + + + + + This resource allows for the definition of some activity to be performed, independent of a particular patient, practitioner, or other performance context. + + + + + + + The type of participant in the action. + + + + + The role the participant should play in performing the described action. + + + + + + + + + This resource allows for the definition of some activity to be performed, independent of a particular patient, practitioner, or other performance context. + + + + + + + The path to the element to be customized. This is the path on the resource that will hold the result of the calculation defined by the expression. The specified path SHALL be a FHIRPath resolveable on the specified target type of the ActivityDefinition, and SHALL consist only of identifiers, constant indexers, and a restricted subset of functions. The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements (see the [Simple FHIRPath Profile](fhirpath.html#simple) for full details). + + + + + An expression specifying the value of the customized element. + + + + + + + + + + + Patient + + + + + Practitioner + + + + + Related Person + + + + + Device + + + + + + + The type of participant in the activity. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Proposal + + + + + Plan + + + + + Directive + + + + + Order + + + + + Original Order + + + + + Reflex Order + + + + + Filler Order + + + + + Instance Order + + + + + Option + + + + + + + Codes indicating the degree of authority/intentionality associated with a request. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Appointment + + + + + AppointmentResponse + + + + + CarePlan + + + + + Claim + + + + + CommunicationRequest + + + + + Contract + + + + + DeviceRequest + + + + + EnrollmentRequest + + + + + ImmunizationRecommendation + + + + + MedicationRequest + + + + + NutritionOrder + + + + + ServiceRequest + + + + + SupplyRequest + + + + + Task + + + + + VisionPrescription + + + + + + + The kind of activity the definition is describing. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Routine + + + + + Urgent + + + + + ASAP + + + + + STAT + + + + + + + Identifies the level of importance to be assigned to actioning the request. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Actual or potential/avoided event causing unintended physical injury resulting from or contributed to by medical care, a research study or other healthcare setting factors that requires additional monitoring, treatment, or hospitalization, or that results in death. + + + + + Actual or potential/avoided event causing unintended physical injury resulting from or contributed to by medical care, a research study or other healthcare setting factors that requires additional monitoring, treatment, or hospitalization, or that results in death. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifiers assigned to this adverse event by the performer or other systems which remain constant as the resource is updated and propagates from server to server. + + + + + Whether the event actually happened, or just had the potential to. Note that this is independent of whether anyone was affected or harmed or how severely. + + + + + The overall type of event, intended for search and filtering purposes. + + + + + This element defines the specific type of event that occurred or that was prevented from occurring. + + + + + This subject or group impacted by the event. + + + + + The Encounter during which AdverseEvent was created or to which the creation of this record is tightly associated. + + + + + The date (and perhaps time) when the adverse event occurred. + + + + + Estimated or actual date the AdverseEvent began, in the opinion of the reporter. + + + + + The date on which the existence of the AdverseEvent was first recorded. + + + + + Includes information about the reaction that occurred as a result of exposure to a substance (for example, a drug or a chemical). + + + + + The information about where the adverse event occurred. + + + + + Assessment whether this event was of real importance. + + + + + Describes the severity of the adverse event, in relation to the subject. Contrast to AdverseEvent.seriousness - a severe rash might not be serious, but a mild heart problem is. + + + + + Describes the type of outcome from the adverse event. + + + + + Information on who recorded the adverse event. May be the patient or a practitioner. + + + + + Parties that may or should contribute or have contributed information to the adverse event, which can consist of one or more activities. Such information includes information leading to the decision to perform the activity and how to perform the activity (e.g. consultant), information that the activity itself seeks to reveal (e.g. informant of clinical history), or information about what activity was performed (e.g. informant witness). + + + + + Describes the entity that is suspected to have caused the adverse event. + + + + + AdverseEvent.subjectMedicalHistory. + + + + + AdverseEvent.referenceDocument. + + + + + AdverseEvent.study. + + + + + + + + + Actual or potential/avoided event causing unintended physical injury resulting from or contributed to by medical care, a research study or other healthcare setting factors that requires additional monitoring, treatment, or hospitalization, or that results in death. + + + + + + + Identifies the actual instance of what caused the adverse event. May be a substance, medication, medication administration, medication statement or a device. + + + + + Information on the possible cause of the event. + + + + + + + + + Actual or potential/avoided event causing unintended physical injury resulting from or contributed to by medical care, a research study or other healthcare setting factors that requires additional monitoring, treatment, or hospitalization, or that results in death. + + + + + + + Assessment of if the entity caused the event. + + + + + AdverseEvent.suspectEntity.causalityProductRelatedness. + + + + + AdverseEvent.suspectEntity.causalityAuthor. + + + + + ProbabilityScale | Bayesian | Checklist. + + + + + + + + + + + Adverse Event + + + + + Potential Adverse Event + + + + + + + Overall nature of the adverse event, e.g. real or potential. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance. + + + + + Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifiers assigned to this AllergyIntolerance by the performer or other systems which remain constant as the resource is updated and propagates from server to server. + + + + + The clinical status of the allergy or intolerance. + + + + + Assertion about certainty associated with the propensity, or potential risk, of a reaction to the identified substance (including pharmaceutical product). + + + + + Identification of the underlying physiological mechanism for the reaction risk. + + + + + Category of the identified substance. + + + + + Estimate of the potential clinical harm, or seriousness, of the reaction to the identified substance. + + + + + Code for an allergy or intolerance statement (either a positive or a negated/excluded statement). This may be a code for a substance or pharmaceutical product that is considered to be responsible for the adverse reaction risk (e.g., "Latex"), an allergy or intolerance condition (e.g., "Latex allergy"), or a negated/excluded code for a specific substance or class (e.g., "No latex allergy") or a general or categorical negated statement (e.g., "No known allergy", "No known drug allergies"). Note: the substance for a specific reaction may be different from the substance identified as the cause of the risk, but it must be consistent with it. For instance, it may be a more specific substance (e.g. a brand medication) or a composite product that includes the identified substance. It must be clinically safe to only process the 'code' and ignore the 'reaction.substance'. If a receiving system is unable to confirm that AllergyIntolerance.reaction.substance falls within the semantic scope of AllergyIntolerance.code, then the receiving system should ignore AllergyIntolerance.reaction.substance. + + + + + The patient who has the allergy or intolerance. + + + + + The encounter when the allergy or intolerance was asserted. + + + + + Estimated or actual date, date-time, or age when allergy or intolerance was identified. + + + + + + + + + + The recordedDate represents when this particular AllergyIntolerance record was created in the system, which is often a system-generated date. + + + + + Individual who recorded the record and takes responsibility for its content. + + + + + The source of the information about the allergy that is recorded. + + + + + Represents the date and/or time of the last known occurrence of a reaction event. + + + + + Additional narrative about the propensity for the Adverse Reaction, not captured in other fields. + + + + + Details about each adverse reaction event linked to exposure to the identified substance. + + + + + + + + + Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance. + + + + + + + Identification of the specific substance (or pharmaceutical product) considered to be responsible for the Adverse Reaction event. Note: the substance for a specific reaction may be different from the substance identified as the cause of the risk, but it must be consistent with it. For instance, it may be a more specific substance (e.g. a brand medication) or a composite product that includes the identified substance. It must be clinically safe to only process the 'code' and ignore the 'reaction.substance'. If a receiving system is unable to confirm that AllergyIntolerance.reaction.substance falls within the semantic scope of AllergyIntolerance.code, then the receiving system should ignore AllergyIntolerance.reaction.substance. + + + + + Clinical symptoms and/or signs that are observed or associated with the adverse reaction event. + + + + + Text description about the reaction as a whole, including details of the manifestation if required. + + + + + Record of the date and/or time of the onset of the Reaction. + + + + + Clinical assessment of the severity of the reaction event as a whole, potentially considering multiple different manifestations. + + + + + Identification of the route by which the subject was exposed to the substance. + + + + + Additional text about the adverse reaction event not captured in other fields. + + + + + + + + + + + Low Risk + + + + + High Risk + + + + + Unable to Assess Risk + + + + + + + Estimate of the potential clinical harm, or seriousness, of a reaction to an identified substance. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Allergy + + + + + Intolerance + + + + + + + Identification of the underlying physiological mechanism for a Reaction Risk. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Food + + + + + Medication + + + + + Environment + + + + + Biologic + + + + + + + Category of an identified substance associated with allergies or intolerances. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Mild + + + + + Moderate + + + + + Severe + + + + + + + Clinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A booking of a healthcare event among patient(s), practitioner(s), related person(s) and/or device(s) for a specific date/time. This may result in one or more Encounter(s). + + + + + A booking of a healthcare event among patient(s), practitioner(s), related person(s) and/or device(s) for a specific date/time. This may result in one or more Encounter(s). + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + This records identifiers associated with this appointment concern that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation). + + + + + The overall status of the Appointment. Each of the participants has their own participation status which indicates their involvement in the process, however this status indicates the shared status. + + + + + The coded reason for the appointment being cancelled. This is often used in reporting/billing/futher processing to determine if further actions are required, or specific fees apply. + + + + + A broad categorization of the service that is to be performed during this appointment. + + + + + The specific service that is to be performed during this appointment. + + + + + The specialty of a practitioner that would be required to perform the service requested in this appointment. + + + + + The style of appointment or patient that has been booked in the slot (not service type). + + + + + The coded reason that this appointment is being scheduled. This is more clinical than administrative. + + + + + Reason the appointment has been scheduled to take place, as specified using information from another resource. When the patient arrives and the encounter begins it may be used as the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure. + + + + + The priority of the appointment. Can be used to make informed decisions if needing to re-prioritize appointments. (The iCal Standard specifies 0 as undefined, 1 as highest, 9 as lowest priority). + + + + + The brief description of the appointment as would be shown on a subject line in a meeting request, or appointment list. Detailed or expanded information should be put in the comment field. + + + + + Additional information to support the appointment provided when making the appointment. + + + + + Date/Time that the appointment is to take place. + + + + + Date/Time that the appointment is to conclude. + + + + + Number of minutes that the appointment is to take. This can be less than the duration between the start and end times. For example, where the actual time of appointment is only an estimate or if a 30 minute appointment is being requested, but any time would work. Also, if there is, for example, a planned 15 minute break in the middle of a long appointment, the duration may be 15 minutes less than the difference between the start and end. + + + + + The slots from the participants' schedules that will be filled by the appointment. + + + + + The date that this appointment was initially created. This could be different to the meta.lastModified value on the initial entry, as this could have been before the resource was created on the FHIR server, and should remain unchanged over the lifespan of the appointment. + + + + + Additional comments about the appointment. + + + + + While Appointment.comment contains information for internal use, Appointment.patientInstructions is used to capture patient facing information about the Appointment (e.g. please bring your referral or fast from 8pm night before). + + + + + The service request this appointment is allocated to assess (e.g. incoming referral or procedure request). + + + + + List of participants involved in the appointment. + + + + + A set of date ranges (potentially including times) that the appointment is preferred to be scheduled within. + +The duration (usually in minutes) could also be provided to indicate the length of the appointment to fill and populate the start/end times for the actual allocated time. However, in other situations the duration may be calculated by the scheduling system. + + + + + + + + + A booking of a healthcare event among patient(s), practitioner(s), related person(s) and/or device(s) for a specific date/time. This may result in one or more Encounter(s). + + + + + + + Role of participant in the appointment. + + + + + A Person, Location/HealthcareService or Device that is participating in the appointment. + + + + + Whether this participant is required to be present at the meeting. This covers a use-case where two doctors need to meet to discuss the results for a specific patient, and the patient is not required to be present. + + + + + Participation status of the actor. + + + + + Participation period of the actor. + + + + + + + + + + + Required + + + + + Optional + + + + + Information Only + + + + + + + Is the Participant required to attend the appointment. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Proposed + + + + + Pending + + + + + Booked + + + + + Arrived + + + + + Fulfilled + + + + + Cancelled + + + + + No Show + + + + + Entered in error + + + + + Checked In + + + + + Waitlisted + + + + + + + The free/busy status of an appointment. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Accepted + + + + + Declined + + + + + Tentative + + + + + Needs Action + + + + + + + The Participation status of an appointment. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A reply to an appointment request for a patient and/or practitioner(s), such as a confirmation or rejection. + + + + + A reply to an appointment request for a patient and/or practitioner(s), such as a confirmation or rejection. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + This records identifiers associated with this appointment response concern that are defined by business processes and/ or used to refer to it when a direct URL reference to the resource itself is not appropriate. + + + + + Appointment that this response is replying to. + + + + + Date/Time that the appointment is to take place, or requested new start time. + + + + + This may be either the same as the appointment request to confirm the details of the appointment, or alternately a new time to request a re-negotiation of the end time. + + + + + Role of participant in the appointment. + + + + + A Person, Location, HealthcareService, or Device that is participating in the appointment. + + + + + Participation status of the participant. When the status is declined or tentative if the start/end times are different to the appointment, then these times should be interpreted as a requested time change. When the status is accepted, the times can either be the time of the appointment (as a confirmation of the time) or can be empty. + + + + + Additional comments about the appointment. + + + + + + + + + A record of an event made for purposes of maintaining a security log. Typical uses include detection of intrusion attempts and monitoring for inappropriate usage. + + + + + A record of an event made for purposes of maintaining a security log. Typical uses include detection of intrusion attempts and monitoring for inappropriate usage. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifier for a family of the event. For example, a menu item, program, rule, policy, function code, application name or URL. It identifies the performed function. + + + + + Identifier for the category of event. + + + + + Indicator for type of action performed during the event that generated the audit. + + + + + The period during which the activity occurred. + + + + + The time when the event was recorded. + + + + + Indicates whether the event succeeded or failed. + + + + + A free text description of the outcome of the event. + + + + + The purposeOfUse (reason) that was used during the event being recorded. + + + + + An actor taking an active role in the event or activity that is logged. + + + + + The system that is reporting the event. + + + + + Specific instances of data or objects that have been accessed. + + + + + + + + + A record of an event made for purposes of maintaining a security log. Typical uses include detection of intrusion attempts and monitoring for inappropriate usage. + + + + + + + Specification of the participation type the user plays when performing the event. + + + + + The security role that the user was acting under, that come from local codes defined by the access control security system (e.g. RBAC, ABAC) used in the local context. + + + + + Reference to who this agent is that was involved in the event. + + + + + Alternative agent Identifier. For a human, this should be a user identifier text string from authentication system. This identifier would be one known to a common authentication system (e.g. single sign-on), if available. + + + + + Human-meaningful name for the agent. + + + + + Indicator that the user is or is not the requestor, or initiator, for the event being audited. + + + + + Where the event occurred. + + + + + The policy or plan that authorized the activity being recorded. Typically, a single activity may have multiple applicable policies, such as patient consent, guarantor funding, etc. The policy would also indicate the security token used. + + + + + Type of media involved. Used when the event is about exporting/importing onto media. + + + + + Logical network location for application activity, if the activity has a network location. + + + + + The reason (purpose of use), specific to this agent, that was used during the event being recorded. + + + + + + + + + A record of an event made for purposes of maintaining a security log. Typical uses include detection of intrusion attempts and monitoring for inappropriate usage. + + + + + + + An identifier for the network access point of the user device for the audit event. + + + + + An identifier for the type of network access point that originated the audit event. + + + + + + + + + A record of an event made for purposes of maintaining a security log. Typical uses include detection of intrusion attempts and monitoring for inappropriate usage. + + + + + + + Logical source location within the healthcare enterprise network. For example, a hospital or other provider location within a multi-entity provider group. + + + + + Identifier of the source where the event was detected. + + + + + Code specifying the type of source where event originated. + + + + + + + + + A record of an event made for purposes of maintaining a security log. Typical uses include detection of intrusion attempts and monitoring for inappropriate usage. + + + + + + + Identifies a specific instance of the entity. The reference should be version specific. + + + + + The type of the object that was involved in this audit event. + + + + + Code representing the role the entity played in the event being audited. + + + + + Identifier for the data life-cycle stage for the entity. + + + + + Security labels for the identified entity. + + + + + A name of the entity in the audit event. + + + + + Text that describes the entity in more detail. + + + + + The query parameters for a query-type entities. + + + + + Tagged value pairs for conveying additional information about the entity. + + + + + + + + + A record of an event made for purposes of maintaining a security log. Typical uses include detection of intrusion attempts and monitoring for inappropriate usage. + + + + + + + The type of extra detail provided in the value. + + + + + The value of the extra detail. + + + + + + + + + + + + + Success + + + + + Minor failure + + + + + Serious failure + + + + + Major failure + + + + + + + Indicates whether the event succeeded or failed. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Create + + + + + Read/View/Print + + + + + Update + + + + + Delete + + + + + Execute + + + + + + + Indicator for type of action performed during the event that generated the event. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Machine Name + + + + + IP Address + + + + + Telephone Number + + + + + Email address + + + + + URI + + + + + + + The type of network access point of this agent in the audit event. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Basic is used for handling concepts not yet defined in FHIR, narrative-only resources that don't map to an existing resource, and custom resources not appropriate for inclusion in the FHIR specification. + + + + + Basic is used for handling concepts not yet defined in FHIR, narrative-only resources that don't map to an existing resource, and custom resources not appropriate for inclusion in the FHIR specification. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifier assigned to the resource for business purposes, outside the context of FHIR. + + + + + Identifies the 'type' of resource - equivalent to the resource name for other resources. + + + + + Identifies the patient, practitioner, device or any other resource that is the "focus" of this resource. + + + + + Identifies when the resource was first created. + + + + + Indicates who was responsible for creating the resource instance. + + + + + + + + + A resource that represents the data of a single raw artifact as digital content accessible in its native format. A Binary resource can contain any content, whether text, image, pdf, zip archive, etc. + + + + + A resource that represents the data of a single raw artifact as digital content accessible in its native format. A Binary resource can contain any content, whether text, image, pdf, zip archive, etc. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + MimeType of the binary content represented as a standard MimeType (BCP 13). + + + + + This element identifies another resource that can be used as a proxy of the security sensitivity to use when deciding and enforcing access control rules for the Binary resource. Given that the Binary resource contains very few elements that can be used to determine the sensitivity of the data and relationships to individuals, the referenced resource stands in as a proxy equivalent for this purpose. This referenced resource may be related to the Binary (e.g. Media, DocumentReference), or may be some non-related Resource purely as a security proxy. E.g. to identify that the binary resource relates to a patient, and access should only be granted to applications that have access to the patient. + + + + + The actual content, base64 encoded. + + + + + + + + + A material substance originating from a biological entity intended to be transplanted or infused +into another (possibly the same) biological entity. + + + + + A material substance originating from a biological entity intended to be transplanted or infused +into another (possibly the same) biological entity. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + This records identifiers associated with this biologically derived product instance that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation). + + + + + Broad category of this product. + + + + + A code that identifies the kind of this biologically derived product (SNOMED Ctcode). + + + + + Whether the product is currently available. + + + + + Procedure request to obtain this biologically derived product. + + + + + Number of discrete units within this product. + + + + + Parent product (if any). + + + + + How this product was collected. + + + + + Any processing of the product during collection that does not change the fundamental nature of the product. For example adding anti-coagulants during the collection of Peripheral Blood Stem Cells. + + + + + Any manipulation of product post-collection that is intended to alter the product. For example a buffy-coat enrichment or CD8 reduction of Peripheral Blood Stem Cells to make it more suitable for infusion. + + + + + Product storage. + + + + + + + + + A material substance originating from a biological entity intended to be transplanted or infused +into another (possibly the same) biological entity. + + + + + + + Healthcare professional who is performing the collection. + + + + + The patient or entity, such as a hospital or vendor in the case of a processed/manipulated/manufactured product, providing the product. + + + + + Time of product collection. + + + + + + + + + + + A material substance originating from a biological entity intended to be transplanted or infused +into another (possibly the same) biological entity. + + + + + + + Description of of processing. + + + + + Procesing code. + + + + + Substance added during processing. + + + + + Time of processing. + + + + + + + + + + + A material substance originating from a biological entity intended to be transplanted or infused +into another (possibly the same) biological entity. + + + + + + + Description of manipulation. + + + + + Time of manipulation. + + + + + + + + + + + A material substance originating from a biological entity intended to be transplanted or infused +into another (possibly the same) biological entity. + + + + + + + Description of storage. + + + + + Storage temperature. + + + + + Temperature scale used. + + + + + Storage timeperiod. + + + + + + + + + + + Organ + + + + + Tissue + + + + + Fluid + + + + + Cells + + + + + BiologicalAgent + + + + + + + Biologically Derived Product Category. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Available + + + + + Unavailable + + + + + + + Biologically Derived Product Status. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Fahrenheit + + + + + Celsius + + + + + Kelvin + + + + + + + BiologicallyDerived Product Storage Scale. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Record details about an anatomical structure. This resource may be used when a coded concept does not provide the necessary detail needed for the use case. + + + + + Record details about an anatomical structure. This resource may be used when a coded concept does not provide the necessary detail needed for the use case. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifier for this instance of the anatomical structure. + + + + + Whether this body site is in active use. + + + + + The kind of structure being represented by the body structure at `BodyStructure.location`. This can define both normal and abnormal morphologies. + + + + + The anatomical location or region of the specimen, lesion, or body structure. + + + + + Qualifier to refine the anatomical location. These include qualifiers for laterality, relative location, directionality, number, and plane. + + + + + A summary, characterization or explanation of the body structure. + + + + + Image or images used to identify a location. + + + + + The person to which the body site belongs. + + + + + + + + + A container for a collection of resources. + + + + + A container for a collection of resources. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A persistent identifier for the bundle that won't change as a bundle is copied from server to server. + + + + + Indicates the purpose of this bundle - how it is intended to be used. + + + + + The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle. + + + + + If a set of search matches, this is the total number of entries of type 'match' across all pages in the search. It does not include search.mode = 'include' or 'outcome' entries and it does not provide a count of the number of entries in the Bundle. + + + + + A series of links that provide context to this bundle. + + + + + An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only). + + + + + Digital Signature - base64 encoded. XML-DSig or a JWT. + + + + + + + + + A container for a collection of resources. + + + + + + + A name which details the functional use for this link - see [http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1](http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1). + + + + + The reference details for the link. + + + + + + + + + A container for a collection of resources. + + + + + + + A series of links that provide context to this entry. + + + + + The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that: +* fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle) +* Results from operations might involve resources that are not identified. + + + + + The Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type. + + + + + Information about the search process that lead to the creation of this entry. + + + + + Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry. + + + + + Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history. + + + + + + + + + A container for a collection of resources. + + + + + + + Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. + + + + + When searching, the server's search ranking score for the entry. + + + + + + + + + A container for a collection of resources. + + + + + + + In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred. + + + + + The URL for this entry, relative to the root (the address to which the request is posted). + + + + + If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http.html#cread). + + + + + Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http.html#cread). + + + + + Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http.html#concurrency). + + + + + Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?"). + + + + + + + + + A container for a collection of resources. + + + + + + + The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code. + + + + + The location header created by processing this operation, populated if the operation returns a location. + + + + + The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http.html#versioning) and [Managing Resource Contention](http.html#concurrency)). + + + + + The date/time that the resource was modified on the server. + + + + + An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction. + + + + + + + + + + + GET + + + + + HEAD + + + + + POST + + + + + PUT + + + + + DELETE + + + + + PATCH + + + + + + + HTTP verbs (in the HTTP command line). See [HTTP rfc](https://tools.ietf.org/html/rfc7231) for details. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Document + + + + + Message + + + + + Transaction + + + + + Transaction Response + + + + + Batch + + + + + Batch Response + + + + + History List + + + + + Search Results + + + + + Collection + + + + + + + Indicates the purpose of a bundle - how it is intended to be used. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Match + + + + + Include + + + + + Outcome + + + + + + + Why an entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this capability statement when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this capability statement is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the capability statement is stored on different servers. + + + + + The identifier that is used to identify this version of the capability statement when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the capability statement 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. + + + + + A natural language name identifying the capability statement. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the capability statement. + + + + + The status of this capability statement. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this capability statement is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The date (and optionally time) when the capability statement was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the capability statement changes. + + + + + The name of the organization or individual that published the capability statement. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the capability statement from a consumer's perspective. Typically, this is used when the capability statement describes a desired rather than an actual solution, for example as a formal expression of requirements as part of an RFP. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate capability statement instances. + + + + + A legal or geographic region in which the capability statement is intended to be used. + + + + + Explanation of why this capability statement is needed and why it has been designed as it has. + + + + + A copyright statement relating to the capability statement and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the capability statement. + + + + + The way that this statement is intended to be used, to describe an actual running instance of software, a particular product (kind, not instance of software) or a class of implementation (e.g. a desired purchase). + + + + + Reference to a canonical URL of another CapabilityStatement that this software implements. This capability statement is a published API description that corresponds to a business service. The server may actually implement a subset of the capability statement it claims to implement, so the capability statement must specify the full capability details. + + + + + Reference to a canonical URL of another CapabilityStatement that this software adds to. The capability statement automatically includes everything in the other statement, and it is not duplicated, though the server may repeat the same resources, interactions and operations to add additional details to them. + + + + + Software that is covered by this capability statement. It is used when the capability statement describes the capabilities of a particular software version, independent of an installation. + + + + + Identifies a specific implementation instance that is described by the capability statement - i.e. a particular installation, rather than the capabilities of a software program. + + + + + The version of the FHIR specification that this CapabilityStatement describes (which SHALL be the same as the FHIR version of the CapabilityStatement itself). There is no default value. + + + + + A list of the formats supported by this implementation using their content types. + + + + + A list of the patch formats supported by this implementation using their content types. + + + + + A list of implementation guides that the server does (or should) support in their entirety. + + + + + A definition of the restful capabilities of the solution, if any. + + + + + A description of the messaging capabilities of the solution. + + + + + A document definition. + + + + + + + + + A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + Name the software is known by. + + + + + The version identifier for the software covered by this statement. + + + + + Date this version of the software was released. + + + + + + + + + A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + Information about the specific installation that this capability statement relates to. + + + + + An absolute base URL for the implementation. This forms the base for REST interfaces as well as the mailbox and document interfaces. + + + + + The organization responsible for the management of the instance and oversight of the data on the server at the specified URL. + + + + + + + + + A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + Identifies whether this portion of the statement is describing the ability to initiate or receive restful operations. + + + + + Information about the system's restful capabilities that apply across all applications, such as security. + + + + + Information about security implementation from an interface perspective - what a client needs to know. + + + + + A specification of the restful capabilities of the solution for a specific resource type. + + + + + A specification of restful operations supported by the system. + + + + + Search parameters that are supported for searching all resources for implementations to support and/or make use of - either references to ones defined in the specification, or additional ones defined for/by the implementation. + + + + + Definition of an operation or a named query together with its parameters and their meaning and type. + + + + + An absolute URI which is a reference to the definition of a compartment that the system supports. The reference is to a CompartmentDefinition resource by its canonical URL . + + + + + + + + + A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + Server adds CORS headers when responding to requests - this enables Javascript applications to use the server. + + + + + Types of security services that are supported/required by the system. + + + + + General description of how security works. + + + + + + + + + A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + A type of resource exposed via the restful interface. + + + + + A specification of the profile that describes the solution's overall support for the resource, including any constraints on cardinality, bindings, lengths or other limitations. See further discussion in [Using Profiles](profiling.html#profile-uses). + + + + + A list of profiles that represent different use cases supported by the system. For a server, "supported by the system" means the system hosts/produces a set of resources that are conformant to a particular profile, and allows clients that use its services to search using this profile and to find appropriate data. For a client, it means the system will search by this profile and process data according to the guidance implicit in the profile. See further discussion in [Using Profiles](profiling.html#profile-uses). + + + + + Additional information about the resource type used by the system. + + + + + Identifies a restful operation supported by the solution. + + + + + This field is set to no-version to specify that the system does not support (server) or use (client) versioning for this resource type. If this has some other value, the server must at least correctly track and populate the versionId meta-property on resources. If the value is 'versioned-update', then the server supports all the versioning features, including using e-tags for version integrity in the API. + + + + + A flag for whether the server is able to return past versions as part of the vRead operation. + + + + + A flag to indicate that the server allows or needs to allow the client to create new identities on the server (that is, the client PUTs to a location where there is no existing resource). Allowing this operation means that the server allows the client to create new identities on the server. + + + + + A flag that indicates that the server supports conditional create. + + + + + A code that indicates how the server supports conditional read. + + + + + A flag that indicates that the server supports conditional update. + + + + + A code that indicates how the server supports conditional delete. + + + + + A set of flags that defines how references are supported. + + + + + A list of _include values supported by the server. + + + + + A list of _revinclude (reverse include) values supported by the server. + + + + + Search parameters for implementations to support and/or make use of - either references to ones defined in the specification, or additional ones defined for/by the implementation. + + + + + Definition of an operation or a named query together with its parameters and their meaning and type. Consult the definition of the operation for details about how to invoke the operation, and the parameters. + + + + + + + + + A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + Coded identifier of the operation, supported by the system resource. + + + + + Guidance specific to the implementation of this operation, such as 'delete is a logical delete' or 'updates are only allowed with version id' or 'creates permitted from pre-authorized certificates only'. + + + + + + + + + A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + The name of the search parameter used in the interface. + + + + + An absolute URI that is a formal reference to where this parameter was first defined, so that a client can be confident of the meaning of the search parameter (a reference to [[[SearchParameter.url]]]). This element SHALL be populated if the search parameter refers to a SearchParameter defined by the FHIR core specification or externally defined IGs. + + + + + The type of value a search parameter refers to, and how the content is interpreted. + + + + + This allows documentation of any distinct behaviors about how the search parameter is used. For example, text matching algorithms. + + + + + + + + + A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + The name of the operation or query. For an operation, this is the name prefixed with $ and used in the URL. For a query, this is the name used in the _query parameter when the query is called. + + + + + Where the formal definition can be found. If a server references the base definition of an Operation (i.e. from the specification itself such as ```http://hl7.org/fhir/OperationDefinition/ValueSet-expand```), that means it supports the full capabilities of the operation - e.g. both GET and POST invocation. If it only supports a subset, it must define its own custom [[[OperationDefinition]]] with a 'base' of the original OperationDefinition. The custom definition would describe the specific subset of functionality supported. + + + + + Documentation that describes anything special about the operation behavior, possibly detailing different behavior for system, type and instance-level invocation of the operation. + + + + + + + + + A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + A coded identifier of the operation, supported by the system. + + + + + Guidance specific to the implementation of this operation, such as limitations on the kind of transactions allowed, or information about system wide search is implemented. + + + + + + + + + A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + An endpoint (network accessible address) to which messages and/or replies are to be sent. + + + + + Length if the receiver's reliable messaging cache in minutes (if a receiver) or how long the cache length on the receiver should be (if a sender). + + + + + Documentation about the system's messaging capabilities for this endpoint not otherwise documented by the capability statement. For example, the process for becoming an authorized messaging exchange partner. + + + + + References to message definitions for messages this system can send or receive. + + + + + + + + + A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + A list of the messaging transport protocol(s) identifiers, supported by this endpoint. + + + + + The network address of the endpoint. For solutions that do not use network addresses for routing, it can be just an identifier. + + + + + + + + + A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + The mode of this event declaration - whether application is sender or receiver. + + + + + Points to a message definition that identifies the messaging event, message structure, allowed responses, etc. + + + + + + + + + A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + Mode of this document declaration - whether an application is a producer or consumer. + + + + + A description of how the application supports or uses the specified document profile. For example, when documents are created, what action is taken with consumed documents, etc. + + + + + A profile on the document Bundle that constrains which resources are present, and their contents. + + + + + + + + + + + Instance + + + + + Capability + + + + + Requirements + + + + + + + How a capability statement is intended to be used. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Sender + + + + + Receiver + + + + + + + The mode of a message capability statement. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + No VersionId Support + + + + + Versioned + + + + + VersionId tracked fully + + + + + + + How the system supports versioning for a resource. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Producer + + + + + Consumer + + + + + + + Whether the application produces or consumes documents. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Client + + + + + Server + + + + + + + The mode of a RESTful capability statement. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + read + + + + + vread + + + + + update + + + + + patch + + + + + delete + + + + + history-instance + + + + + history-type + + + + + create + + + + + search-type + + + + + + + Operations supported by REST at the type or instance level. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + transaction + + + + + batch + + + + + search-system + + + + + history-system + + + + + + + Operations supported by REST at the system level. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Not Supported + + + + + If-Modified-Since + + + + + If-None-Match + + + + + Full Support + + + + + + + A code that indicates how the server supports conditional read. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Literal References + + + + + Logical References + + + + + Resolves References + + + + + Reference Integrity Enforced + + + + + Local References Only + + + + + + + A set of flags that defines how references are supported. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Not Supported + + + + + Single Deletes Supported + + + + + Multiple Deletes Supported + + + + + + + A code that indicates how the server supports conditional delete. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Describes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions. + + + + + Describes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifiers assigned to this care plan by the performer or other systems which remain constant as the resource is updated and propagates from server to server. + + + + + The URL pointing to a FHIR-defined protocol, guideline, questionnaire or other definition that is adhered to in whole or in part by this CarePlan. + + + + + The URL pointing to an externally maintained protocol, guideline, questionnaire or other definition that is adhered to in whole or in part by this CarePlan. + + + + + A care plan that is fulfilled in whole or in part by this care plan. + + + + + Completed or terminated care plan whose function is taken by this new care plan. + + + + + A larger care plan of which this particular care plan is a component or step. + + + + + Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record. + + + + + Indicates the level of authority/intentionality associated with the care plan and where the care plan fits into the workflow chain. + + + + + Identifies what "kind" of plan this is to support differentiation between multiple co-existing plans; e.g. "Home health", "psychiatric", "asthma", "disease management", "wellness plan", etc. + + + + + Human-friendly name for the care plan. + + + + + A description of the scope and nature of the plan. + + + + + Identifies the patient or group whose intended care is described by the plan. + + + + + The Encounter during which this CarePlan was created or to which the creation of this record is tightly associated. + + + + + Indicates when the plan did (or is intended to) come into effect and end. + + + + + Represents when this particular CarePlan record was created in the system, which is often a system-generated date. + + + + + When populated, the author is responsible for the care plan. The care plan is attributed to the author. + + + + + Identifies the individual(s) or organization who provided the contents of the care plan. + + + + + Identifies all people and organizations who are expected to be involved in the care envisioned by this plan. + + + + + Identifies the conditions/problems/concerns/diagnoses/etc. whose management and/or mitigation are handled by this plan. + + + + + Identifies portions of the patient's record that specifically influenced the formation of the plan. These might include comorbidities, recent procedures, limitations, recent assessments, etc. + + + + + Describes the intended objective(s) of carrying out the care plan. + + + + + Identifies a planned action to occur as part of the plan. For example, a medication to be used, lab tests to perform, self-monitoring, education, etc. + + + + + General notes about the care plan not covered elsewhere. + + + + + + + + + Describes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions. + + + + + + + Identifies the outcome at the point when the status of the activity is assessed. For example, the outcome of an education activity could be patient understands (or not). + + + + + Details of the outcome or action resulting from the activity. The reference to an "event" resource, such as Procedure or Encounter or Observation, is the result/outcome of the activity itself. The activity can be conveyed using CarePlan.activity.detail OR using the CarePlan.activity.reference (a reference to a “request” resource). + + + + + Notes about the adherence/status/progress of the activity. + + + + + The details of the proposed activity represented in a specific resource. + + + + + A simple summary of a planned activity suitable for a general care plan system (e.g. form driven) that doesn't know about specific resources such as procedure etc. + + + + + + + + + Describes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions. + + + + + + + A description of the kind of resource the in-line definition of a care plan activity is representing. The CarePlan.activity.detail is an in-line definition when a resource is not referenced using CarePlan.activity.reference. For example, a MedicationRequest, a ServiceRequest, or a CommunicationRequest. + + + + + The URL pointing to a FHIR-defined protocol, guideline, questionnaire or other definition that is adhered to in whole or in part by this CarePlan activity. + + + + + The URL pointing to an externally maintained protocol, guideline, questionnaire or other definition that is adhered to in whole or in part by this CarePlan activity. + + + + + Detailed description of the type of planned activity; e.g. what lab test, what procedure, what kind of encounter. + + + + + Provides the rationale that drove the inclusion of this particular activity as part of the plan or the reason why the activity was prohibited. + + + + + Indicates another resource, such as the health condition(s), whose existence justifies this request and drove the inclusion of this particular activity as part of the plan. + + + + + Internal reference that identifies the goals that this activity is intended to contribute towards meeting. + + + + + Identifies what progress is being made for the specific activity. + + + + + Provides reason why the activity isn't yet started, is on hold, was cancelled, etc. + + + + + If true, indicates that the described activity is one that must NOT be engaged in when following the plan. If false, or missing, indicates that the described activity is one that should be engaged in when following the plan. + + + + + The period, timing or frequency upon which the described activity is to occur. + + + + + + + + Identifies the facility where the activity will occur; e.g. home, hospital, specific clinic, etc. + + + + + Identifies who's expected to be involved in the activity. + + + + + Identifies the food, drug or other product to be consumed or supplied in the activity. + + + + + + + Identifies the quantity expected to be consumed in a given day. + + + + + Identifies the quantity expected to be supplied, administered or consumed by the subject. + + + + + This provides a textual description of constraints on the intended activity occurrence, including relation to other activities. It may also include objectives, pre-conditions and end-conditions. Finally, it may convey specifics about the activity such as body site, method, route, etc. + + + + + + + + + + + Appointment + Appointment + Appuntamento + RendezVous + Cita + 预约 + + + + + CommunicationRequest + CommunicationRequest + RichiestaDiComunicazione + DemandeDeCommunication + ComunicaciónRequerimiento + 通讯请求 + + + + + DeviceRequest + DeviceRequest + RichiestaDispositivo + DemandeUtilisationDispositif + SolicitudDeDispositivo + 装置请求 + + + + + MedicationRequest + MedicationRequest + PrescriptionMédicamenteuseTODO + 药物请求 + PrescripciónMedicaciónTODO /PrescripcionMedicamento + + + + + NutritionOrder + NutritionOrder + OrdreNutrition + OrdenNutrición + 营养医嘱 + + + + + Task + Task + Tarea + 任务 + + + + + ServiceRequest + ServiceRequest + RichiestaDiServizio + DemandeService + PeticiónServicio + 服务项目请求 + + + + + VisionPrescription + VisionPrescription + PrescriptionVision + PrescripcionDeVision + 视力处方 + + + + + + + Resource types defined as part of FHIR that can be represented as in-line definitions of a care plan activity. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Not Started + + + + + Scheduled + + + + + In Progress + + + + + On Hold + + + + + Completed + + + + + Cancelled + + + + + Stopped + + + + + Unknown + + + + + Entered in Error + + + + + + + Codes that reflect the current state of a care plan activity within its overall life cycle. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Proposal + + + + + Plan + + + + + Order + + + + + Option + + + + + + + Codes indicating the degree of authority/intentionality associated with a care plan. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Draft + + + + + Active + + + + + On Hold + + + + + Revoked + + + + + Completed + + + + + Entered in Error + + + + + Unknown + + + + + + + Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient. + + + + + The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifiers assigned to this care team by the performer or other systems which remain constant as the resource is updated and propagates from server to server. + + + + + Indicates the current state of the care team. + + + + + Identifies what kind of team. This is to support differentiation between multiple co-existing teams, such as care plan team, episode of care team, longitudinal care team. + + + + + A label for human use intended to distinguish like teams. E.g. the "red" vs. "green" trauma teams. + + + + + Identifies the patient or group whose intended care is handled by the team. + + + + + The Encounter during which this CareTeam was created or to which the creation of this record is tightly associated. + + + + + Indicates when the team did (or is intended to) come into effect and end. + + + + + Identifies all people and organizations who are expected to be involved in the care team. + + + + + Describes why the care team exists. + + + + + Condition(s) that this care team addresses. + + + + + The organization responsible for the care team. + + + + + A central contact detail for the care team (that applies to all members). + + + + + Comments made about the CareTeam. + + + + + + + + + The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient. + + + + + + + Indicates specific responsibility of an individual within the care team, such as "Primary care physician", "Trained social worker counselor", "Caregiver", etc. + + + + + The specific person or organization who is participating/expected to participate in the care team. + + + + + The organization of the practitioner. + + + + + Indicates when the specific member or organization did (or is intended to) come into effect and end. + + + + + + + + + + + Proposed + + + + + Active + + + + + Suspended + + + + + Inactive + + + + + Entered in Error + + + + + + + Indicates the status of the care team. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Catalog entries are wrappers that contextualize items included in a catalog. + + + + + Catalog entries are wrappers that contextualize items included in a catalog. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Used in supporting different identifiers for the same product, e.g. manufacturer code and retailer code. + + + + + The type of item - medication, device, service, protocol or other. + + + + + Whether the entry represents an orderable item. + + + + + The item in a catalog or definition. + + + + + Used in supporting related concepts, e.g. NDC to RxNorm. + + + + + Classes of devices, or ATC for medication. + + + + + Used to support catalog exchange even for unsupported products, e.g. getting list of medications even if not prescribable. + + + + + The time period in which this catalog entry is expected to be active. + + + + + The date until which this catalog entry is expected to be active. + + + + + Typically date of issue is different from the beginning of the validity. This can be used to see when an item was last updated. + + + + + Used for examplefor Out of Formulary, or any specifics. + + + + + User for example for ATC classification, or. + + + + + Used for example, to point to a substance, or to a device used to administer a medication. + + + + + + + + + Catalog entries are wrappers that contextualize items included in a catalog. + + + + + + + The type of relation to the related item: child, parent, packageContent, containerPackage, usedIn, uses, requires, etc. + + + + + The reference to the related item. + + + + + + + + + + + Triggers + + + + + Replaced By + + + + + + + The type of relations between entries. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + The resource ChargeItem describes the provision of healthcare provider products for a certain patient, therefore referring not only to the product, but containing in addition details of the provision, like date, time, amounts and participating organizations and persons. Main Usage of the ChargeItem is to enable the billing process and internal cost allocation. + + + + + The resource ChargeItem describes the provision of healthcare provider products for a certain patient, therefore referring not only to the product, but containing in addition details of the provision, like date, time, amounts and participating organizations and persons. Main Usage of the ChargeItem is to enable the billing process and internal cost allocation. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifiers assigned to this event performer or other systems. + + + + + References the (external) source of pricing information, rules of application for the code this ChargeItem uses. + + + + + References the source of pricing information, rules of application for the code this ChargeItem uses. + + + + + The current state of the ChargeItem. + + + + + ChargeItems can be grouped to larger ChargeItems covering the whole set. + + + + + A code that identifies the charge, like a billing code. + + + + + The individual or set of individuals the action is being or was performed on. + + + + + The encounter or episode of care that establishes the context for this event. + + + + + Date/time(s) or duration when the charged service was applied. + + + + + + + + Indicates who or what performed or participated in the charged service. + + + + + The organization requesting the service. + + + + + The organization performing the service. + + + + + The financial cost center permits the tracking of charge attribution. + + + + + Quantity of which the charge item has been serviced. + + + + + The anatomical location where the related service has been applied. + + + + + Factor overriding the factor determined by the rules associated with the code. + + + + + Total price of the charge overriding the list price associated with the code. + + + + + If the list price or the rule-based factor associated with the code is overridden, this attribute can capture a text to indicate the reason for this action. + + + + + The device, practitioner, etc. who entered the charge item. + + + + + Date the charge item was entered. + + + + + Describes why the event occurred in coded or textual form. + + + + + Indicated the rendered service that caused this charge. + + + + + Identifies the device, food, drug or other product being charged either by type code or reference to an instance. + + + + + + + Account into which this ChargeItems belongs. + + + + + Comments made about the event by the performer, subject or other participants. + + + + + Further information supporting this charge. + + + + + + + + + The resource ChargeItem describes the provision of healthcare provider products for a certain patient, therefore referring not only to the product, but containing in addition details of the provision, like date, time, amounts and participating organizations and persons. Main Usage of the ChargeItem is to enable the billing process and internal cost allocation. + + + + + + + Describes the type of performance or participation(e.g. primary surgeon, anesthesiologiest, etc.). + + + + + The device, practitioner, etc. who performed or participated in the service. + + + + + + + + + + + Planned + + + + + Billable + + + + + Not billable + + + + + Aborted + + + + + Billed + + + + + Entered in Error + + + + + Unknown + + + + + + + Codes identifying the lifecycle stage of a ChargeItem. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + The ChargeItemDefinition resource provides the properties that apply to the (billing) codes necessary to calculate costs and prices. The properties may differ largely depending on type and realm, therefore this resource gives only a rough structure and requires profiling for each type of billing code system. + + + + + The ChargeItemDefinition resource provides the properties that apply to the (billing) codes necessary to calculate costs and prices. The properties may differ largely depending on type and realm, therefore this resource gives only a rough structure and requires profiling for each type of billing code system. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this charge item definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this charge item definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the charge item definition is stored on different servers. + + + + + A formal identifier that is used to identify this charge item definition when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the charge item definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the charge item definition 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. To provide a version consistent with the Decision Support Service specification, use the format Major.Minor.Revision (e.g. 1.0.0). For more information on versioning knowledge assets, refer to the Decision Support Service specification. Note that a version is required for non-experimental active assets. + + + + + A short, descriptive, user-friendly title for the charge item definition. + + + + + The URL pointing to an externally-defined charge item definition that is adhered to in whole or in part by this definition. + + + + + A larger definition of which this particular definition is a component or step. + + + + + As new versions of a protocol or guideline are defined, allows identification of what versions are replaced by a new instance. + + + + + The current state of the ChargeItemDefinition. + + + + + A Boolean value to indicate that this charge item definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The date (and optionally time) when the charge item definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the charge item definition changes. + + + + + The name of the organization or individual that published the charge item definition. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the charge item definition from a consumer's perspective. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate charge item definition instances. + + + + + A legal or geographic region in which the charge item definition is intended to be used. + + + + + A copyright statement relating to the charge item definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the charge item definition. + + + + + The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. + + + + + The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. + + + + + The period during which the charge item definition content was or is planned to be in active use. + + + + + The defined billing details in this resource pertain to the given billing code. + + + + + The defined billing details in this resource pertain to the given product instance(s). + + + + + Expressions that describe applicability criteria for the billing code. + + + + + Group of properties which are applicable under the same conditions. If no applicability rules are established for the group, then all properties always apply. + + + + + + + + + The ChargeItemDefinition resource provides the properties that apply to the (billing) codes necessary to calculate costs and prices. The properties may differ largely depending on type and realm, therefore this resource gives only a rough structure and requires profiling for each type of billing code system. + + + + + + + A brief, natural language description of the condition that effectively communicates the intended semantics. + + + + + The media type of the language for the expression, e.g. "text/cql" for Clinical Query Language expressions or "text/fhirpath" for FHIRPath expressions. + + + + + An expression that returns true or false, indicating whether the condition is satisfied. When using FHIRPath expressions, the %context environment variable must be replaced at runtime with the ChargeItem resource to which this definition is applied. + + + + + + + + + The ChargeItemDefinition resource provides the properties that apply to the (billing) codes necessary to calculate costs and prices. The properties may differ largely depending on type and realm, therefore this resource gives only a rough structure and requires profiling for each type of billing code system. + + + + + + + Expressions that describe applicability criteria for the priceComponent. + + + + + The price for a ChargeItem may be calculated as a base price with surcharges/deductions that apply in certain conditions. A ChargeItemDefinition resource that defines the prices, factors and conditions that apply to a billing code is currently under development. The priceComponent element can be used to offer transparency to the recipient of the Invoice of how the prices have been calculated. + + + + + + + + + The ChargeItemDefinition resource provides the properties that apply to the (billing) codes necessary to calculate costs and prices. The properties may differ largely depending on type and realm, therefore this resource gives only a rough structure and requires profiling for each type of billing code system. + + + + + + + This code identifies the type of the component. + + + + + A code that identifies the component. Codes may be used to differentiate between kinds of taxes, surcharges, discounts etc. + + + + + The factor that has been applied on the base price for calculating this component. + + + + + The amount calculated for this component. + + + + + + + + + + + base price + + + + + surcharge + + + + + deduction + + + + + discount + + + + + tax + + + + + informational + + + + + + + Codes indicating the kind of the price component. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement. + + + + + A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A unique identifier assigned to this claim. + + + + + The status of the resource instance. + + + + + The category of claim, e.g. oral, pharmacy, vision, institutional, professional. + + + + + A finer grained suite of claim type codes which may convey additional information such as Inpatient vs Outpatient and/or a specialty service. + + + + + A code to indicate whether the nature of the request is: to request adjudication of products and services previously rendered; or requesting authorization and adjudication for provision in the future; or requesting the non-binding adjudication of the listed products and services which could be provided in the future. + + + + + The party to whom the professional services and/or products have been supplied or are being considered and for whom actual or forecast reimbursement is sought. + + + + + The period for which charges are being submitted. + + + + + The date this resource was created. + + + + + Individual who created the claim, predetermination or preauthorization. + + + + + The Insurer who is target of the request. + + + + + The provider which is responsible for the claim, predetermination or preauthorization. + + + + + The provider-required urgency of processing the request. Typical values include: stat, routine deferred. + + + + + A code to indicate whether and for whom funds are to be reserved for future claims. + + + + + Other claims which are related to this claim such as prior submissions or claims for related services or for the same event. + + + + + Prescription to support the dispensing of pharmacy, device or vision products. + + + + + Original prescription which has been superseded by this prescription to support the dispensing of pharmacy services, medications or products. + + + + + The party to be reimbursed for cost of the products and services according to the terms of the policy. + + + + + A reference to a referral resource. + + + + + Facility where the services were provided. + + + + + The members of the team who provided the products and services. + + + + + Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. + + + + + Information about diagnoses relevant to the claim items. + + + + + Procedures performed on the patient relevant to the billing items with the claim. + + + + + Financial instruments for reimbursement for the health care products and services specified on the claim. + + + + + Details of an accident which resulted in injuries which required the products and services listed in the claim. + + + + + A claim line. Either a simple product or service or a 'group' of details which can each be a simple items or groups of sub-details. + + + + + The total value of the all the items in the claim. + + + + + + + + + A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement. + + + + + + + Reference to a related claim. + + + + + A code to convey how the claims are related. + + + + + An alternate organizational reference to the case or file to which this particular claim pertains. + + + + + + + + + A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement. + + + + + + + Type of Party to be reimbursed: subscriber, provider, other. + + + + + Reference to the individual or organization to whom any payment will be made. + + + + + + + + + A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement. + + + + + + + A number to uniquely identify care team entries. + + + + + Member of the team who provided the product or service. + + + + + The party who is billing and/or responsible for the claimed products or services. + + + + + The lead, assisting or supervising practitioner and their discipline if a multidisciplinary team. + + + + + The qualification of the practitioner which is applicable for this service. + + + + + + + + + A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement. + + + + + + + A number to uniquely identify supporting information entries. + + + + + The general class of the information supplied: information; exception; accident, employment; onset, etc. + + + + + System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought. + + + + + The date when or period to which this information refers. + + + + + + + Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. + + + + + + + + + + Provides the reason in the situation where a reason code is required in addition to the content. + + + + + + + + + A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement. + + + + + + + A number to uniquely identify diagnosis entries. + + + + + The nature of illness or problem in a coded form or as a reference to an external defined Condition. + + + + + + + When the condition was observed or the relative ranking. + + + + + Indication of whether the diagnosis was present on admission to a facility. + + + + + A package billing code or bundle code used to group products and services to a particular health condition (such as heart attack) which is based on a predetermined grouping code system. + + + + + + + + + A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement. + + + + + + + A number to uniquely identify procedure entries. + + + + + When the condition was observed or the relative ranking. + + + + + Date and optionally time the procedure was performed. + + + + + The code or reference to a Procedure resource which identifies the clinical intervention performed. + + + + + + + Unique Device Identifiers associated with this line item. + + + + + + + + + A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement. + + + + + + + A number to uniquely identify insurance entries and provide a sequence of coverages to convey coordination of benefit order. + + + + + A flag to indicate that this Coverage is to be used for adjudication of this claim when set to true. + + + + + The business identifier to be used when the claim is sent for adjudication against this insurance policy. + + + + + Reference to the insurance card level information contained in the Coverage resource. The coverage issuing insurer will use these details to locate the patient's actual coverage within the insurer's information system. + + + + + A business agreement number established between the provider and the insurer for special business processing purposes. + + + + + Reference numbers previously provided by the insurer to the provider to be quoted on subsequent claims containing services or products related to the prior authorization. + + + + + The result of the adjudication of the line items for the Coverage specified in this insurance. + + + + + + + + + A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement. + + + + + + + Date of an accident event related to the products and services contained in the claim. + + + + + The type or context of the accident event for the purposes of selection of potential insurance coverages and determination of coordination between insurers. + + + + + The physical location of the accident event. + + + + + + + + + + + A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement. + + + + + + + A number to uniquely identify item entries. + + + + + CareTeam members related to this service or product. + + + + + Diagnosis applicable for this service or product. + + + + + Procedures applicable for this service or product. + + + + + Exceptions, special conditions and supporting information applicable for this service or product. + + + + + The type of revenue or cost center providing the product and/or service. + + + + + Code to identify the general type of benefits under which products and services are provided. + + + + + When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. + + + + + Item typification or modifiers codes to convey additional context for the product or service. + + + + + Identifies the program under which this may be recovered. + + + + + The date or dates when the service or product was supplied, performed or completed. + + + + + + + Where the product or service was provided. + + + + + + + + The number of repetitions of a service or product. + + + + + If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group. + + + + + A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. + + + + + The quantity times the unit price for an additional service or product or charge. + + + + + Unique Device Identifiers associated with this line item. + + + + + Physical service site on the patient (limb, tooth, etc.). + + + + + A region or surface of the bodySite, e.g. limb region or tooth surface(s). + + + + + The Encounters during which this Claim was created or to which the creation of this record is tightly associated. + + + + + A claim detail line. Either a simple (a product or service) or a 'group' of sub-details which are simple items. + + + + + + + + + A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement. + + + + + + + A number to uniquely identify item entries. + + + + + The type of revenue or cost center providing the product and/or service. + + + + + Code to identify the general type of benefits under which products and services are provided. + + + + + When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. + + + + + Item typification or modifiers codes to convey additional context for the product or service. + + + + + Identifies the program under which this may be recovered. + + + + + The number of repetitions of a service or product. + + + + + If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group. + + + + + A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. + + + + + The quantity times the unit price for an additional service or product or charge. + + + + + Unique Device Identifiers associated with this line item. + + + + + A claim detail line. Either a simple (a product or service) or a 'group' of sub-details which are simple items. + + + + + + + + + A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement. + + + + + + + A number to uniquely identify item entries. + + + + + The type of revenue or cost center providing the product and/or service. + + + + + Code to identify the general type of benefits under which products and services are provided. + + + + + When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. + + + + + Item typification or modifiers codes to convey additional context for the product or service. + + + + + Identifies the program under which this may be recovered. + + + + + The number of repetitions of a service or product. + + + + + If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group. + + + + + A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. + + + + + The quantity times the unit price for an additional service or product or charge. + + + + + Unique Device Identifiers associated with this line item. + + + + + + + + + + + Claim + + + + + Preauthorization + + + + + Predetermination + + + + + + + The purpose of the Claim: predetermination, preauthorization, claim. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Active + + + + + Cancelled + + + + + Draft + + + + + Entered in Error + + + + + + + A code specifying the state of the resource instance. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + This resource provides the adjudication details from the processing of a Claim resource. + + + + + This resource provides the adjudication details from the processing of a Claim resource. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A unique identifier assigned to this claim response. + + + + + The status of the resource instance. + + + + + A finer grained suite of claim type codes which may convey additional information such as Inpatient vs Outpatient and/or a specialty service. + + + + + A finer grained suite of claim type codes which may convey additional information such as Inpatient vs Outpatient and/or a specialty service. + + + + + A code to indicate whether the nature of the request is: to request adjudication of products and services previously rendered; or requesting authorization and adjudication for provision in the future; or requesting the non-binding adjudication of the listed products and services which could be provided in the future. + + + + + The party to whom the professional services and/or products have been supplied or are being considered and for whom actual for facast reimbursement is sought. + + + + + The date this resource was created. + + + + + The party responsible for authorization, adjudication and reimbursement. + + + + + The provider which is responsible for the claim, predetermination or preauthorization. + + + + + Original request resource reference. + + + + + The outcome of the claim, predetermination, or preauthorization processing. + + + + + A human readable description of the status of the adjudication. + + + + + Reference from the Insurer which is used in later communications which refers to this adjudication. + + + + + The time frame during which this authorization is effective. + + + + + Type of Party to be reimbursed: subscriber, provider, other. + + + + + A claim line. Either a simple (a product or service) or a 'group' of details which can also be a simple items or groups of sub-details. + + + + + The first-tier service adjudications for payor added product or service lines. + + + + + The adjudication results which are presented at the header level rather than at the line-item or add-item levels. + + + + + Categorized monetary totals for the adjudication. + + + + + Payment details for the adjudication of the claim. + + + + + A code, used only on a response to a preauthorization, to indicate whether the benefits payable have been reserved and for whom. + + + + + A code for the form to be used for printing the content. + + + + + The actual form, by reference or inclusion, for printing the content or an EOB. + + + + + A note that describes or explains adjudication results in a human readable form. + + + + + Request for additional supporting or authorizing information. + + + + + Financial instruments for reimbursement for the health care products and services specified on the claim. + + + + + Errors encountered during the processing of the adjudication. + + + + + + + + + This resource provides the adjudication details from the processing of a Claim resource. + + + + + + + A number to uniquely reference the claim item entries. + + + + + The numbers associated with notes below which apply to the adjudication of this item. + + + + + If this item is a group then the values here are a summary of the adjudication of the detail items. If this item is a simple product or service then this is the result of the adjudication of this item. + + + + + A claim detail. Either a simple (a product or service) or a 'group' of sub-details which are simple items. + + + + + + + + + This resource provides the adjudication details from the processing of a Claim resource. + + + + + + + A code to indicate the information type of this adjudication record. Information types may include the value submitted, maximum values or percentages allowed or payable under the plan, amounts that: the patient is responsible for in aggregate or pertaining to this item; amounts paid by other coverages; and, the benefit payable for this item. + + + + + A code supporting the understanding of the adjudication result and explaining variance from expected amount. + + + + + Monetary amount associated with the category. + + + + + A non-monetary value associated with the category. Mutually exclusive to the amount element above. + + + + + + + + + This resource provides the adjudication details from the processing of a Claim resource. + + + + + + + A number to uniquely reference the claim detail entry. + + + + + The numbers associated with notes below which apply to the adjudication of this item. + + + + + The adjudication results. + + + + + A sub-detail adjudication of a simple product or service. + + + + + + + + + This resource provides the adjudication details from the processing of a Claim resource. + + + + + + + A number to uniquely reference the claim sub-detail entry. + + + + + The numbers associated with notes below which apply to the adjudication of this item. + + + + + The adjudication results. + + + + + + + + + This resource provides the adjudication details from the processing of a Claim resource. + + + + + + + Claim items which this service line is intended to replace. + + + + + The sequence number of the details within the claim item which this line is intended to replace. + + + + + The sequence number of the sub-details within the details within the claim item which this line is intended to replace. + + + + + The providers who are authorized for the services rendered to the patient. + + + + + When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. + + + + + Item typification or modifiers codes to convey additional context for the product or service. + + + + + Identifies the program under which this may be recovered. + + + + + The date or dates when the service or product was supplied, performed or completed. + + + + + + + Where the product or service was provided. + + + + + + + + The number of repetitions of a service or product. + + + + + If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group. + + + + + A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. + + + + + The quantity times the unit price for an additional service or product or charge. + + + + + Physical service site on the patient (limb, tooth, etc.). + + + + + A region or surface of the bodySite, e.g. limb region or tooth surface(s). + + + + + The numbers associated with notes below which apply to the adjudication of this item. + + + + + The adjudication results. + + + + + The second-tier service adjudications for payor added services. + + + + + + + + + This resource provides the adjudication details from the processing of a Claim resource. + + + + + + + When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. + + + + + Item typification or modifiers codes to convey additional context for the product or service. + + + + + The number of repetitions of a service or product. + + + + + If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group. + + + + + A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. + + + + + The quantity times the unit price for an additional service or product or charge. + + + + + The numbers associated with notes below which apply to the adjudication of this item. + + + + + The adjudication results. + + + + + The third-tier service adjudications for payor added services. + + + + + + + + + This resource provides the adjudication details from the processing of a Claim resource. + + + + + + + When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. + + + + + Item typification or modifiers codes to convey additional context for the product or service. + + + + + The number of repetitions of a service or product. + + + + + If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group. + + + + + A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. + + + + + The quantity times the unit price for an additional service or product or charge. + + + + + The numbers associated with notes below which apply to the adjudication of this item. + + + + + The adjudication results. + + + + + + + + + This resource provides the adjudication details from the processing of a Claim resource. + + + + + + + A code to indicate the information type of this adjudication record. Information types may include: the value submitted, maximum values or percentages allowed or payable under the plan, amounts that the patient is responsible for in aggregate or pertaining to this item, amounts paid by other coverages, and the benefit payable for this item. + + + + + Monetary total amount associated with the category. + + + + + + + + + This resource provides the adjudication details from the processing of a Claim resource. + + + + + + + Whether this represents partial or complete payment of the benefits payable. + + + + + Total amount of all adjustments to this payment included in this transaction which are not related to this claim's adjudication. + + + + + Reason for the payment adjustment. + + + + + Estimated date the payment will be issued or the actual issue date of payment. + + + + + Benefits payable less any payment adjustment. + + + + + Issuer's unique identifier for the payment instrument. + + + + + + + + + This resource provides the adjudication details from the processing of a Claim resource. + + + + + + + A number to uniquely identify a note entry. + + + + + The business purpose of the note text. + + + + + The explanation or description associated with the processing. + + + + + A code to define the language used in the text of the note. + + + + + + + + + This resource provides the adjudication details from the processing of a Claim resource. + + + + + + + A number to uniquely identify insurance entries and provide a sequence of coverages to convey coordination of benefit order. + + + + + A flag to indicate that this Coverage is to be used for adjudication of this claim when set to true. + + + + + Reference to the insurance card level information contained in the Coverage resource. The coverage issuing insurer will use these details to locate the patient's actual coverage within the insurer's information system. + + + + + A business agreement number established between the provider and the insurer for special business processing purposes. + + + + + The result of the adjudication of the line items for the Coverage specified in this insurance. + + + + + + + + + This resource provides the adjudication details from the processing of a Claim resource. + + + + + + + The sequence number of the line item submitted which contains the error. This value is omitted when the error occurs outside of the item structure. + + + + + The sequence number of the detail within the line item submitted which contains the error. This value is omitted when the error occurs outside of the item structure. + + + + + The sequence number of the sub-detail within the detail within the line item submitted which contains the error. This value is omitted when the error occurs outside of the item structure. + + + + + An error code, from a specified code system, which details why the claim could not be adjudicated. + + + + + + + + + + + Queued + + + + + Processing Complete + + + + + Error + + + + + Partial Processing + + + + + + + The result of the claim processing. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A record of a clinical assessment performed to determine what problem(s) may affect the patient and before planning the treatments or management strategies that are best to manage a patient's condition. Assessments are often 1:1 with a clinical consultation / encounter, but this varies greatly depending on the clinical workflow. This resource is called "ClinicalImpression" rather than "ClinicalAssessment" to avoid confusion with the recording of assessment tools such as Apgar score. + + + + + A record of a clinical assessment performed to determine what problem(s) may affect the patient and before planning the treatments or management strategies that are best to manage a patient's condition. Assessments are often 1:1 with a clinical consultation / encounter, but this varies greatly depending on the clinical workflow. This resource is called "ClinicalImpression" rather than "ClinicalAssessment" to avoid confusion with the recording of assessment tools such as Apgar score. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifiers assigned to this clinical impression by the performer or other systems which remain constant as the resource is updated and propagates from server to server. + + + + + Identifies the workflow status of the assessment. + + + + + Captures the reason for the current state of the ClinicalImpression. + + + + + Categorizes the type of clinical assessment performed. + + + + + A summary of the context and/or cause of the assessment - why / where it was performed, and what patient events/status prompted it. + + + + + The patient or group of individuals assessed as part of this record. + + + + + The Encounter during which this ClinicalImpression was created or to which the creation of this record is tightly associated. + + + + + The point in time or period over which the subject was assessed. + + + + + + + Indicates when the documentation of the assessment was complete. + + + + + The clinician performing the assessment. + + + + + A reference to the last assessment that was conducted on this patient. Assessments are often/usually ongoing in nature; a care provider (practitioner or team) will make new assessments on an ongoing basis as new data arises or the patient's conditions changes. + + + + + A list of the relevant problems/conditions for a patient. + + + + + One or more sets of investigations (signs, symptoms, etc.). The actual grouping of investigations varies greatly depending on the type and context of the assessment. These investigations may include data generated during the assessment process, or data previously generated and recorded that is pertinent to the outcomes. + + + + + Reference to a specific published clinical protocol that was followed during this assessment, and/or that provides evidence in support of the diagnosis. + + + + + A text summary of the investigations and the diagnosis. + + + + + Specific findings or diagnoses that were considered likely or relevant to ongoing treatment. + + + + + Estimate of likely outcome. + + + + + RiskAssessment expressing likely outcome. + + + + + Information supporting the clinical impression. + + + + + Commentary about the impression, typically recorded after the impression itself was made, though supplemental notes by the original author could also appear. + + + + + + + + + A record of a clinical assessment performed to determine what problem(s) may affect the patient and before planning the treatments or management strategies that are best to manage a patient's condition. Assessments are often 1:1 with a clinical consultation / encounter, but this varies greatly depending on the clinical workflow. This resource is called "ClinicalImpression" rather than "ClinicalAssessment" to avoid confusion with the recording of assessment tools such as Apgar score. + + + + + + + A name/code for the group ("set") of investigations. Typically, this will be something like "signs", "symptoms", "clinical", "diagnostic", but the list is not constrained, and others such groups such as (exposure|family|travel|nutritional) history may be used. + + + + + A record of a specific investigation that was undertaken. + + + + + + + + + A record of a clinical assessment performed to determine what problem(s) may affect the patient and before planning the treatments or management strategies that are best to manage a patient's condition. Assessments are often 1:1 with a clinical consultation / encounter, but this varies greatly depending on the clinical workflow. This resource is called "ClinicalImpression" rather than "ClinicalAssessment" to avoid confusion with the recording of assessment tools such as Apgar score. + + + + + + + Specific text or code for finding or diagnosis, which may include ruled-out or resolved conditions. + + + + + Specific reference for finding or diagnosis, which may include ruled-out or resolved conditions. + + + + + Which investigations support finding or diagnosis. + + + + + + + + + + + In Progress + + + + + Completed + + + + + Entered in Error + + + + + + + The workflow state of a clinical impression. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + The CodeSystem resource is used to declare the existence of and describe a code system or code system supplement and its key properties, and optionally define a part or all of its content. + + + + + The CodeSystem resource is used to declare the existence of and describe a code system or code system supplement and its key properties, and optionally define a part or all of its content. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this code system when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this code system is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the code system is stored on different servers. This is used in [Coding](datatypes.html#Coding).system. + + + + + A formal identifier that is used to identify this code system when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the code system when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the code system 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. This is used in [Coding](datatypes.html#Coding).version. + + + + + A natural language name identifying the code system. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the code system. + + + + + The date (and optionally time) when the code system resource was created or revised. + + + + + A Boolean value to indicate that this code system is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The date (and optionally time) when the code system was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the code system changes. + + + + + The name of the organization or individual that published the code system. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the code system from a consumer's perspective. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate code system instances. + + + + + A legal or geographic region in which the code system is intended to be used. + + + + + Explanation of why this code system is needed and why it has been designed as it has. + + + + + A copyright statement relating to the code system and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the code system. + + + + + If code comparison is case sensitive when codes within this system are compared to each other. + + + + + Canonical reference to the value set that contains the entire code system. + + + + + The meaning of the hierarchy of concepts as represented in this resource. + + + + + The code system defines a compositional (post-coordination) grammar. + + + + + This flag is used to signify that the code system does not commit to concept permanence across versions. If true, a version must be specified when referencing this code system. + + + + + The extent of the content of the code system (the concepts and codes it defines) are represented in this resource instance. + + + + + The canonical URL of the code system that this code system supplement is adding designations and properties to. + + + + + The total number of concepts defined by the code system. Where the code system has a compositional grammar, the basis of this count is defined by the system steward. + + + + + A filter that can be used in a value set compose statement when selecting concepts using a filter. + + + + + A property defines an additional slot through which additional information can be provided about a concept. + + + + + Concepts that are in the code system. The concept definitions are inherently hierarchical, but the definitions must be consulted to determine what the meanings of the hierarchical relationships are. + + + + + + + + + The CodeSystem resource is used to declare the existence of and describe a code system or code system supplement and its key properties, and optionally define a part or all of its content. + + + + + + + The code that identifies this filter when it is used as a filter in [[[ValueSet]]].compose.include.filter. + + + + + A description of how or why the filter is used. + + + + + A list of operators that can be used with the filter. + + + + + A description of what the value for the filter should be. + + + + + + + + + The CodeSystem resource is used to declare the existence of and describe a code system or code system supplement and its key properties, and optionally define a part or all of its content. + + + + + + + A code that is used to identify the property. The code is used internally (in CodeSystem.concept.property.code) and also externally, such as in property filters. + + + + + Reference to the formal meaning of the property. One possible source of meaning is the [Concept Properties](codesystem-concept-properties.html) code system. + + + + + A description of the property- why it is defined, and how its value might be used. + + + + + The type of the property value. Properties of type "code" contain a code defined by the code system (e.g. a reference to another defined concept). + + + + + + + + + The CodeSystem resource is used to declare the existence of and describe a code system or code system supplement and its key properties, and optionally define a part or all of its content. + + + + + + + A code - a text symbol - that uniquely identifies the concept within the code system. + + + + + A human readable string that is the recommended default way to present this concept to a user. + + + + + The formal definition of the concept. The code system resource does not make formal definitions required, because of the prevalence of legacy systems. However, they are highly recommended, as without them there is no formal meaning associated with the concept. + + + + + Additional representations for the concept - other languages, aliases, specialized purposes, used for particular purposes, etc. + + + + + A property value for this concept. + + + + + Defines children of a concept to produce a hierarchy of concepts. The nature of the relationships is variable (is-a/contains/categorizes) - see hierarchyMeaning. + + + + + + + + + The CodeSystem resource is used to declare the existence of and describe a code system or code system supplement and its key properties, and optionally define a part or all of its content. + + + + + + + The language this designation is defined for. + + + + + A code that details how this designation would be used. + + + + + The text value for this designation. + + + + + + + + + The CodeSystem resource is used to declare the existence of and describe a code system or code system supplement and its key properties, and optionally define a part or all of its content. + + + + + + + A code that is a reference to CodeSystem.property.code. + + + + + The value of this property. + + + + + + + + + + + + + + + + + + Equals + + + + + Is A (by subsumption) + + + + + Descendent Of (by subsumption) + + + + + Not (Is A) (by subsumption) + + + + + Regular Expression + + + + + In Set + + + + + Not in Set + + + + + Generalizes (by Subsumption) + + + + + Exists + + + + + + + The kind of operation to perform as a part of a property based filter. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + code (internal reference) + + + + + Coding (external reference) + + + + + string + + + + + integer + + + + + boolean + + + + + dateTime + + + + + decimal + + + + + + + The type of a property value. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Grouped By + + + + + Is-A + + + + + Part Of + + + + + Classified With + + + + + + + The meaning of the hierarchy of concepts in a code system. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Not Present + + + + + Example + + + + + Fragment + + + + + Complete + + + + + Supplement + + + + + + + The extent of the content of the code system (the concepts and codes it defines) are represented in a code system resource. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + An occurrence of information being transmitted; e.g. an alert that was sent to a responsible provider, a public health agency that was notified about a reportable condition. + + + + + An occurrence of information being transmitted; e.g. an alert that was sent to a responsible provider, a public health agency that was notified about a reportable condition. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifiers assigned to this communication by the performer or other systems which remain constant as the resource is updated and propagates from server to server. + + + + + The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Communication. + + + + + The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Communication. + + + + + An order, proposal or plan fulfilled in whole or in part by this Communication. + + + + + Part of this action. + + + + + Prior communication that this communication is in response to. + + + + + The status of the transmission. + + + + + Captures the reason for the current state of the Communication. + + + + + The type of message conveyed such as alert, notification, reminder, instruction, etc. + + + + + Characterizes how quickly the planned or in progress communication must be addressed. Includes concepts such as stat, urgent, routine. + + + + + A channel that was used for this communication (e.g. email, fax). + + + + + The patient or group that was the focus of this communication. + + + + + Description of the purpose/content, similar to a subject line in an email. + + + + + Other resources that pertain to this communication and to which this communication should be associated. + + + + + The Encounter during which this Communication was created or to which the creation of this record is tightly associated. + + + + + The time when this communication was sent. + + + + + The time when this communication arrived at the destination. + + + + + The entity (e.g. person, organization, clinical information system, care team or device) which was the target of the communication. If receipts need to be tracked by an individual, a separate resource instance will need to be created for each recipient. Multiple recipient communications are intended where either receipts are not tracked (e.g. a mass mail-out) or a receipt is captured in aggregate (all emails confirmed received by a particular time). + + + + + The entity (e.g. person, organization, clinical information system, or device) which was the source of the communication. + + + + + The reason or justification for the communication. + + + + + Indicates another resource whose existence justifies this communication. + + + + + Text, attachment(s), or resource(s) that was communicated to the recipient. + + + + + Additional notes or commentary about the communication by the sender, receiver or other interested parties. + + + + + + + + + An occurrence of information being transmitted; e.g. an alert that was sent to a responsible provider, a public health agency that was notified about a reportable condition. + + + + + + + A communicated content (or for multi-part communications, one portion of the communication). + + + + + + + + + + + + + + Preparation + + + + + In Progress + + + + + Not Done + + + + + On Hold + + + + + Stopped + + + + + Completed + + + + + Entered in Error + + + + + Unknown + + + + + + + The status of the communication. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A request to convey information; e.g. the CDS system proposes that an alert be sent to a responsible provider, the CDS system proposes that the public health agency be notified about a reportable condition. + + + + + A request to convey information; e.g. the CDS system proposes that an alert be sent to a responsible provider, the CDS system proposes that the public health agency be notified about a reportable condition. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifiers assigned to this communication request by the performer or other systems which remain constant as the resource is updated and propagates from server to server. + + + + + A plan or proposal that is fulfilled in whole or in part by this request. + + + + + Completed or terminated request(s) whose function is taken by this new request. + + + + + A shared identifier common to all requests that were authorized more or less simultaneously by a single author, representing the identifier of the requisition, prescription or similar form. + + + + + The status of the proposal or order. + + + + + Captures the reason for the current state of the CommunicationRequest. + + + + + The type of message to be sent such as alert, notification, reminder, instruction, etc. + + + + + Characterizes how quickly the proposed act must be initiated. Includes concepts such as stat, urgent, routine. + + + + + If true indicates that the CommunicationRequest is asking for the specified action to *not* occur. + + + + + A channel that was used for this communication (e.g. email, fax). + + + + + The patient or group that is the focus of this communication request. + + + + + Other resources that pertain to this communication request and to which this communication request should be associated. + + + + + The Encounter during which this CommunicationRequest was created or to which the creation of this record is tightly associated. + + + + + Text, attachment(s), or resource(s) to be communicated to the recipient. + + + + + The time when this communication is to occur. + + + + + + + For draft requests, indicates the date of initial creation. For requests with other statuses, indicates the date of activation. + + + + + The device, individual, or organization who initiated the request and has responsibility for its activation. + + + + + The entity (e.g. person, organization, clinical information system, device, group, or care team) which is the intended target of the communication. + + + + + The entity (e.g. person, organization, clinical information system, or device) which is to be the source of the communication. + + + + + Describes why the request is being made in coded or textual form. + + + + + Indicates another resource whose existence justifies this request. + + + + + Comments made about the request by the requester, sender, recipient, subject or other participants. + + + + + + + + + A request to convey information; e.g. the CDS system proposes that an alert be sent to a responsible provider, the CDS system proposes that the public health agency be notified about a reportable condition. + + + + + + + The communicated content (or for multi-part communications, one portion of the communication). + + + + + + + + + + + + A compartment definition that defines how resources are accessed on a server. + + + + + A compartment definition that defines how resources are accessed on a server. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this compartment definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this compartment definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the compartment definition is stored on different servers. + + + + + The identifier that is used to identify this version of the compartment definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the compartment definition 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. + + + + + A natural language name identifying the compartment definition. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + The status of this compartment definition. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this compartment definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The date (and optionally time) when the compartment definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the compartment definition changes. + + + + + The name of the organization or individual that published the compartment definition. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the compartment definition from a consumer's perspective. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate compartment definition instances. + + + + + Explanation of why this compartment definition is needed and why it has been designed as it has. + + + + + Which compartment this definition describes. + + + + + Whether the search syntax is supported,. + + + + + Information about how a resource is related to the compartment. + + + + + + + + + A compartment definition that defines how resources are accessed on a server. + + + + + + + The name of a resource supported by the server. + + + + + The name of a search parameter that represents the link to the compartment. More than one may be listed because a resource may be linked to a compartment in more than one way,. + + + + + Additional documentation about the resource and compartment. + + + + + + + + + + + Patient + + + + + Encounter + + + + + RelatedPerson + + + + + Practitioner + + + + + Device + + + + + + + Which type a compartment definition describes. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.). + + + + + A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.). + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A version-independent identifier for the Composition. This identifier stays constant as the composition is changed over time. + + + + + The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document. + + + + + Specifies the particular kind of composition (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the composition. + + + + + A categorization for the type of the composition - helps for indexing and searching. This may be implied by or derived from the code specified in the Composition Type. + + + + + Who or what the composition is about. The composition can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure). + + + + + Describes the clinical encounter or type of care this documentation is associated with. + + + + + The composition editing time, when the composition was last logically changed by the author. + + + + + Identifies who is responsible for the information in the composition, not necessarily who typed it in. + + + + + Official human-readable label for the composition. + + + + + The code specifying the level of confidentiality of the Composition. + + + + + A participant who has attested to the accuracy of the composition/document. + + + + + Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information. + + + + + Relationships that this composition has with other compositions or documents that already exist. + + + + + The clinical service, such as a colonoscopy or an appendectomy, being documented. + + + + + The root of the sections that make up the composition. + + + + + + + + + A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.). + + + + + + + The type of attestation the authenticator offers. + + + + + When the composition was attested by the party. + + + + + Who attested the composition in the specified way. + + + + + + + + + A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.). + + + + + + + The type of relationship that this composition has with anther composition or document. + + + + + The target composition/document of this relationship. + + + + + + + + + + + A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.). + + + + + + + This list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act. + + + + + The period of time covered by the documentation. There is no assertion that the documentation is a complete representation for this period, only that it documents events during this time. + + + + + The description and/or reference of the event(s) being documented. For example, this could be used to document such a colonoscopy or an appendectomy. + + + + + + + + + A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.). + + + + + + + The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. + + + + + A code identifying the kind of content contained within the section. This must be consistent with the section title. + + + + + Identifies who is responsible for the information in this section, not necessarily who typed it in. + + + + + The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). + + + + + A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. + + + + + How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. + + + + + Specifies the order applied to the items in the section entries. + + + + + A reference to the actual resource from which the narrative in the section is derived. + + + + + If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. + + + + + A nested sub-section within this section. + + + + + + + + + + + unrestricted + + + + + low + + + + + moderate + + + + + normal + + + + + restricted + + + + + very restricted + + + + + + + Codes specifying the level of confidentiality of the composition. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Preliminary + + + + + Final + + + + + Amended + + + + + Entered in Error + + + + + + + The workflow/clinical status of the composition. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Replaces + + + + + Transforms + + + + + Signs + + + + + Appends + + + + + + + The type of relationship between documents. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Personal + + + + + Professional + + + + + Legal + + + + + Official + + + + + + + The way in which a person authenticated a composition. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Working List + + + + + Snapshot List + + + + + Change List + + + + + + + The processing mode that applies to this section. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models. + + + + + A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this concept map when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this concept map is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the concept map is stored on different servers. + + + + + A formal identifier that is used to identify this concept map when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the concept map when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the concept map 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. + + + + + A natural language name identifying the concept map. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the concept map. + + + + + The status of this concept map. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this concept map is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The date (and optionally time) when the concept map was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the concept map changes. + + + + + The name of the organization or individual that published the concept map. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the concept map from a consumer's perspective. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate concept map instances. + + + + + A legal or geographic region in which the concept map is intended to be used. + + + + + Explanation of why this concept map is needed and why it has been designed as it has. + + + + + A copyright statement relating to the concept map and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the concept map. + + + + + Identifier for the source value set that contains the concepts that are being mapped and provides context for the mappings. + + + + + + + The target value set provides context for the mappings. Note that the mapping is made between concepts, not between value sets, but the value set provides important context about how the concept mapping choices are made. + + + + + + + A group of mappings that all have the same source and target system. + + + + + + + + + A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models. + + + + + + + An absolute URI that identifies the source system where the concepts to be mapped are defined. + + + + + The specific version of the code system, as determined by the code system authority. + + + + + An absolute URI that identifies the target system that the concepts will be mapped to. + + + + + The specific version of the code system, as determined by the code system authority. + + + + + Mappings for an individual concept in the source to one or more concepts in the target. + + + + + What to do when there is no mapping for the source concept. "Unmapped" does not include codes that are unmatched, and the unmapped element is ignored in a code is specified to have equivalence = unmatched. + + + + + + + + + A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models. + + + + + + + Identity (code or path) or the element/item being mapped. + + + + + The display for the code. The display is only provided to help editors when editing the concept map. + + + + + A concept from the target value set that this concept maps to. + + + + + + + + + A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models. + + + + + + + Identity (code or path) or the element/item that the map refers to. + + + + + The display for the code. The display is only provided to help editors when editing the concept map. + + + + + The equivalence between the source and target concepts (counting for the dependencies and products). The equivalence is read from target to source (e.g. the target is 'wider' than the source). + + + + + A description of status/issues in mapping that conveys additional information not represented in the structured data. + + + + + A set of additional dependencies for this mapping to hold. This mapping is only applicable if the specified element can be resolved, and it has the specified value. + + + + + A set of additional outcomes from this mapping to other elements. To properly execute this mapping, the specified element must be mapped to some data element or source that is in context. The mapping may still be useful without a place for the additional data elements, but the equivalence cannot be relied on. + + + + + + + + + A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models. + + + + + + + A reference to an element that holds a coded value that corresponds to a code system property. The idea is that the information model carries an element somewhere that is labeled to correspond with a code system property. + + + + + An absolute URI that identifies the code system of the dependency code (if the source/dependency is a value set that crosses code systems). + + + + + Identity (code or path) or the element/item/ValueSet/text that the map depends on / refers to. + + + + + The display for the code. The display is only provided to help editors when editing the concept map. + + + + + + + + + A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models. + + + + + + + Defines which action to take if there is no match for the source concept in the target system designated for the group. One of 3 actions are possible: use the unmapped code (this is useful when doing a mapping between versions, and only a few codes have changed), use a fixed code (a default code), or alternatively, a reference to a different concept map can be provided (by canonical URL). + + + + + The fixed code to use when the mode = 'fixed' - all unmapped codes are mapped to a single fixed code. + + + + + The display for the code. The display is only provided to help editors when editing the concept map. + + + + + The canonical reference to an additional ConceptMap resource instance to use for mapping if this ConceptMap resource contains no matching mapping for the source concept. + + + + + + + + + + + Provided Code + + + + + Fixed Code + + + + + Other Map + + + + + + + Defines which action to take if there is no match in the group. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern. + + + + + A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifiers assigned to this condition by the performer or other systems which remain constant as the resource is updated and propagates from server to server. + + + + + The clinical status of the condition. + + + + + The verification status to support the clinical status of the condition. + + + + + A category assigned to the condition. + + + + + A subjective assessment of the severity of the condition as evaluated by the clinician. + + + + + Identification of the condition, problem or diagnosis. + + + + + The anatomical location where this condition manifests itself. + + + + + Indicates the patient or group who the condition record is associated with. + + + + + The Encounter during which this Condition was created or to which the creation of this record is tightly associated. + + + + + Estimated or actual date or date-time the condition began, in the opinion of the clinician. + + + + + + + + + + The date or estimated date that the condition resolved or went into remission. This is called "abatement" because of the many overloaded connotations associated with "remission" or "resolution" - Conditions are never really resolved, but they can abate. + + + + + + + + + + The recordedDate represents when this particular Condition record was created in the system, which is often a system-generated date. + + + + + Individual who recorded the record and takes responsibility for its content. + + + + + Individual who is making the condition statement. + + + + + Clinical stage or grade of a condition. May include formal severity assessments. + + + + + Supporting evidence / manifestations that are the basis of the Condition's verification status, such as evidence that confirmed or refuted the condition. + + + + + Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis. + + + + + + + + + A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern. + + + + + + + A simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific. + + + + + Reference to a formal record of the evidence on which the staging assessment is based. + + + + + The kind of staging, such as pathological or clinical staging. + + + + + + + + + A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern. + + + + + + + A manifestation or symptom that led to the recording of this condition. + + + + + Links to other relevant information, including pathology reports. + + + + + + + + + A record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time. + + + + + A record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Unique identifier for this copy of the Consent Statement. + + + + + Indicates the current state of this consent. + + + + + A selector of the type of consent being presented: ADR, Privacy, Treatment, Research. This list is now extensible. + + + + + A classification of the type of consents found in the statement. This element supports indexing and retrieval of consent statements. + + + + + The patient/healthcare consumer to whom this consent applies. + + + + + When this Consent was issued / created / indexed. + + + + + Either the Grantor, which is the entity responsible for granting the rights listed in a Consent Directive or the Grantee, which is the entity responsible for complying with the Consent Directive, including any obligations or limitations on authorizations and enforcement of prohibitions. + + + + + The organization that manages the consent, and the framework within which it is executed. + + + + + The source on which this consent statement is based. The source might be a scanned original paper form, or a reference to a consent that links back to such a source, a reference to a document repository (e.g. XDS) that stores the original consent document. + + + + + + + The references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law. + + + + + A reference to the specific base computable regulation or policy. + + + + + Whether a treatment instruction (e.g. artificial respiration yes or no) was verified with the patient, his/her family or another authorized person. + + + + + An exception to the base policy of this consent. An exception can be an addition or removal of access permissions. + + + + + + + + + A record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time. + + + + + + + Entity or Organization having regulatory jurisdiction or accountability for enforcing policies pertaining to Consent Directives. + + + + + The references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law. + + + + + + + + + A record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time. + + + + + + + Has the instruction been verified. + + + + + Who verified the instruction (Patient, Relative or other Authorized Person). + + + + + Date verification was collected. + + + + + + + + + A record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time. + + + + + + + Action to take - permit or deny - when the rule conditions are met. Not permitted in root rule, required in all nested rules. + + + + + The timeframe in this rule is valid. + + + + + Who or what is controlled by this rule. Use group to identify a set of actors by some property they share (e.g. 'admitting officers'). + + + + + Actions controlled by this Rule. + + + + + A security label, comprised of 0..* security label fields (Privacy tags), which define which resources are controlled by this exception. + + + + + The context of the activities a user is taking - why the user is accessing the data - that are controlled by this rule. + + + + + The class of information covered by this rule. The type can be a FHIR resource type, a profile on a type, or a CDA document, or some other type that indicates what sort of information the consent relates to. + + + + + If this code is found in an instance, then the rule applies. + + + + + Clinical or Operational Relevant period of time that bounds the data controlled by this rule. + + + + + The resources controlled by this rule if specific resources are referenced. + + + + + Rules which provide exceptions to the base rule or subrules. + + + + + + + + + A record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time. + + + + + + + How the individual is involved in the resources content that is described in the exception. + + + + + The resource that identifies the actor. To identify actors by type, use group to identify a set of actors by some property they share (e.g. 'admitting officers'). + + + + + + + + + A record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time. + + + + + + + How the resource reference is interpreted when testing consent restrictions. + + + + + A reference to a specific resource that defines which resources are covered by this consent. + + + + + + + + + + + Opt Out + + + + + Opt In + + + + + + + How a rule statement is applied, such as adding additional consent or removing consent. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Instance + + + + + Related + + + + + Dependents + + + + + AuthoredBy + + + + + + + How a resource reference is interpreted when testing consent restrictions. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Pending + + + + + Proposed + + + + + Active + + + + + Rejected + + + + + Inactive + + + + + Entered in Error + + + + + + + Indicates the state of the consent. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. + + + + + Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Unique identifier for this Contract or a derivative that references a Source Contract. + + + + + Canonical identifier for this contract, represented as a URI (globally unique). + + + + + An edition identifier used for business purposes to label business significant variants. + + + + + The status of the resource instance. + + + + + Legal states of the formation of a legal instrument, which is a formally executed written document that can be formally attributed to its author, records and formally expresses a legally enforceable act, process, or contractual duty, obligation, or right, and therefore evidences that act, process, or agreement. + + + + + The URL pointing to a FHIR-defined Contract Definition that is adhered to in whole or part by this Contract. + + + + + The URL pointing to an externally maintained definition that is adhered to in whole or in part by this Contract. + + + + + The minimal content derived from the basal information source at a specific stage in its lifecycle. + + + + + When this Contract was issued. + + + + + Relevant time or time-period when this Contract is applicable. + + + + + Event resulting in discontinuation or termination of this Contract instance by one or more parties to the contract. + + + + + The target entity impacted by or of interest to parties to the agreement. + + + + + A formally or informally recognized grouping of people, principals, organizations, or jurisdictions formed for the purpose of achieving some form of collective action such as the promulgation, administration and enforcement of contracts and policies. + + + + + Recognized governance framework or system operating with a circumscribed scope in accordance with specified principles, policies, processes or procedures for managing rights, actions, or behaviors of parties or principals relative to resources. + + + + + Sites in which the contract is complied with, exercised, or in force. + + + + + A natural language name identifying this Contract definition, derivative, or instance in any legal state. Provides additional information about its content. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for this Contract definition, derivative, or instance in any legal state.t giving additional information about its content. + + + + + An explanatory or alternate user-friendly title for this Contract definition, derivative, or instance in any legal state.t giving additional information about its content. + + + + + Alternative representation of the title for this Contract definition, derivative, or instance in any legal state., e.g., a domain specific contract number related to legislation. + + + + + The individual or organization that authored the Contract definition, derivative, or instance in any legal state. + + + + + A selector of legal concerns for this Contract definition, derivative, or instance in any legal state. + + + + + Narrows the range of legal concerns to focus on the achievement of specific contractual objectives. + + + + + + + A high-level category for the legal instrument, whether constructed as a Contract definition, derivative, or instance in any legal state. Provides additional information about its content within the context of the Contract's scope to distinguish the kinds of systems that would be interested in the contract. + + + + + Sub-category for the Contract that distinguishes the kinds of systems that would be interested in the Contract within the context of the Contract's scope. + + + + + Precusory content developed with a focus and intent of supporting the formation a Contract instance, which may be associated with and transformable into a Contract. + + + + + One or more Contract Provisions, which may be related and conveyed as a group, and may contain nested groups. + + + + + Information that may be needed by/relevant to the performer in their execution of this term action. + + + + + Links to Provenance records for past versions of this Contract definition, derivative, or instance, which identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the Contract. The Provence.entity indicates the target that was changed in the update. http://build.fhir.org/provenance-definitions.html#Provenance.entity. + + + + + Parties with legal standing in the Contract, including the principal parties, the grantor(s) and grantee(s), which are any person or organization bound by the contract, and any ancillary parties, which facilitate the execution of the contract such as a notary or witness. + + + + + The "patient friendly language" versionof the Contract in whole or in parts. "Patient friendly language" means the representation of the Contract and Contract Provisions in a manner that is readily accessible and understandable by a layperson in accordance with best practices for communication styles that ensure that those agreeing to or signing the Contract understand the roles, actions, obligations, responsibilities, and implication of the agreement. + + + + + List of Legal expressions or representations of this Contract. + + + + + List of Computable Policy Rule Language Representations of this Contract. + + + + + Legally binding Contract: This is the signed and legally recognized representation of the Contract, which is considered the "source of truth" and which would be the basis for legal action related to enforcement of this Contract. + + + + + + + + + + + Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. + + + + + + + Precusory content structure and use, i.e., a boilerplate, template, application for a contract such as an insurance policy or benefits under a program, e.g., workers compensation. + + + + + Detailed Precusory content type. + + + + + The individual or organization that published the Contract precursor content. + + + + + The date (and optionally time) when the contract was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the contract changes. + + + + + draft | active | retired | unknown. + + + + + A copyright statement relating to Contract precursor content. Copyright statements are generally legal restrictions on the use and publishing of the Contract precursor content. + + + + + + + + + Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. + + + + + + + Unique identifier for this particular Contract Provision. + + + + + When this Contract Provision was issued. + + + + + Relevant time or time-period when this Contract Provision is applicable. + + + + + The entity that the term applies to. + + + + + + + A legal clause or condition contained within a contract that requires one or both parties to perform a particular requirement by some specified time or prevents one or both parties from performing a particular requirement by some specified time. + + + + + A specialized legal clause or condition based on overarching contract type. + + + + + Statement of a provision in a policy or a contract. + + + + + Security labels that protect the handling of information about the term and its elements, which may be specifically identified.. + + + + + The matter of concern in the context of this provision of the agrement. + + + + + Contract Term Asset List. + + + + + An actor taking a role in an activity for which it can be assigned some degree of responsibility for the activity taking place. + + + + + Nested group of Contract Provisions. + + + + + + + + + Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. + + + + + + + Number used to link this term or term element to the applicable Security Label. + + + + + Security label privacy tag that species the level of confidentiality protection required for this term and/or term elements. + + + + + Security label privacy tag that species the applicable privacy and security policies governing this term and/or term elements. + + + + + Security label privacy tag that species the manner in which term and/or term elements are to be protected. + + + + + + + + + Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. + + + + + + + Unique identifier for this particular Contract Provision. + + + + + Offer Recipient. + + + + + The owner of an asset has the residual control rights over the asset: the right to decide all usages of the asset in any way not inconsistent with a prior contract, custom, or law (Hart, 1995, p. 30). + + + + + Type of Contract Provision such as specific requirements, purposes for actions, obligations, prohibitions, e.g. life time maximum benefit. + + + + + Type of choice made by accepting party with respect to an offer made by an offeror/ grantee. + + + + + How the decision about a Contract was conveyed. + + + + + Response to offer text. + + + + + Human readable form of this Contract Offer. + + + + + The id of the clause or question text of the offer in the referenced questionnaire/response. + + + + + Security labels that protects the offer. + + + + + + + + + Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. + + + + + + + Participant in the offer. + + + + + How the party participates in the offer. + + + + + + + + + Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. + + + + + + + Response to an offer clause or question text, which enables selection of values to be agreed to, e.g., the period of participation, the date of occupancy of a rental, warrently duration, or whether biospecimen may be used for further research. + + + + + + + + + + + + + + + + + + + + + Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. + + + + + + + Differentiates the kind of the asset . + + + + + Target entity type about which the term may be concerned. + + + + + Associated entities. + + + + + May be a subtype or part of an offered asset. + + + + + Specifies the applicability of the term to an asset resource instance, and instances it refers to orinstances that refer to it, and/or are owned by the offeree. + + + + + Circumstance of the asset. + + + + + Description of the quality and completeness of the asset that imay be a factor in its valuation. + + + + + Type of Asset availability for use or ownership. + + + + + Asset relevant contractual time period. + + + + + Time period of asset use. + + + + + Clause or question text (Prose Object) concerning the asset in a linked form, such as a QuestionnaireResponse used in the formation of the contract. + + + + + Id [identifier??] of the clause or question text about the asset in the referenced form or QuestionnaireResponse. + + + + + Response to assets. + + + + + Security labels that protects the asset. + + + + + Contract Valued Item List. + + + + + + + + + Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. + + + + + + + Asset context reference may include the creator, custodian, or owning Person or Organization (e.g., bank, repository), location held, e.g., building, jurisdiction. + + + + + Coded representation of the context generally or of the Referenced entity, such as the asset holder type or location. + + + + + Context description. + + + + + + + + + Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. + + + + + + + Specific type of Contract Valued Item that may be priced. + + + + + + + Identifies a Contract Valued Item instance. + + + + + Indicates the time during which this Contract ValuedItem information is effective. + + + + + Specifies the units by which the Contract Valued Item is measured or counted, and quantifies the countable or measurable Contract Valued Item instances. + + + + + A Contract Valued Item unit valuation measure. + + + + + A real number that represents a multiplier used in determining the overall value of the Contract Valued Item delivered. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. + + + + + An amount that expresses the weighting (based on difficulty, cost and/or resource intensiveness) associated with the Contract Valued Item delivered. The concept of Points allows for assignment of point values for a Contract Valued Item, such that a monetary amount can be assigned to each point. + + + + + Expresses the product of the Contract Valued Item unitQuantity and the unitPriceAmt. For example, the formula: unit Quantity * unit Price (Cost per Point) * factor Number * points = net Amount. Quantity, factor and points are assumed to be 1 if not supplied. + + + + + Terms of valuation. + + + + + When payment is due. + + + + + Who will make payment. + + + + + Who will receive payment. + + + + + Id of the clause or question text related to the context of this valuedItem in the referenced form or QuestionnaireResponse. + + + + + A set of security labels that define which terms are controlled by this condition. + + + + + + + + + Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. + + + + + + + True if the term prohibits the action. + + + + + Activity or service obligation to be done or not done, performed or not performed, effectuated or not by this Contract term. + + + + + Entity of the action. + + + + + Reason or purpose for the action stipulated by this Contract Provision. + + + + + Id [identifier??] of the clause or question text related to this action in the referenced form or QuestionnaireResponse. + + + + + Current state of the term action. + + + + + Encounter or Episode with primary association to specified term activity. + + + + + Id [identifier??] of the clause or question text related to the requester of this action in the referenced form or QuestionnaireResponse. + + + + + When action happens. + + + + + + + + Who or what initiated the action and has responsibility for its activation. + + + + + Id [identifier??] of the clause or question text related to the requester of this action in the referenced form or QuestionnaireResponse. + + + + + The type of individual that is desired or required to perform or not perform the action. + + + + + The type of role or competency of an individual desired or required to perform or not perform the action. + + + + + Indicates who or what is being asked to perform (or not perform) the ction. + + + + + Id [identifier??] of the clause or question text related to the reason type or reference of this action in the referenced form or QuestionnaireResponse. + + + + + Rationale for the action to be performed or not performed. Describes why the action is permitted or prohibited. + + + + + Indicates another resource whose existence justifies permitting or not permitting this action. + + + + + Describes why the action is to be performed or not performed in textual form. + + + + + Id [identifier??] of the clause or question text related to the reason type or reference of this action in the referenced form or QuestionnaireResponse. + + + + + Comments made about the term action made by the requester, performer, subject or other participants. + + + + + Security labels that protects the action. + + + + + + + + + Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. + + + + + + + The entity the action is performed or not performed on or for. + + + + + Role type of agent assigned roles in this Contract. + + + + + + + + + Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. + + + + + + + Role of this Contract signer, e.g. notary, grantee. + + + + + Party which is a signator to this Contract. + + + + + Legally binding Contract DSIG signature contents in Base64. + + + + + + + + + Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. + + + + + + + Human readable rendering of this Contract in a format and representation intended to enhance comprehension and ensure understandability. + + + + + + + + + + + Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. + + + + + + + Contract legal text in human renderable form. + + + + + + + + + + + Legally enforceable, formally recorded unilateral or bilateral directive i.e., a policy or agreement. + + + + + + + Computable Contract conveyed using a policy rule language (e.g. XACML, DKAL, SecPal). + + + + + + + + + + + + + Amended + + + + + Appended + + + + + Cancelled + + + + + Disputed + + + + + Entered in Error + + + + + Executable + + + + + Executed + + + + + Negotiable + + + + + Offered + + + + + Policy + + + + + Rejected + + + + + Renewed + + + + + Revoked + + + + + Resolved + + + + + Terminated + + + + + + + A code specifying the state of the resource instance. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Amended + + + + + Appended + + + + + Cancelled + + + + + Disputed + + + + + Entered in Error + + + + + Executable + + + + + Executed + + + + + Negotiable + + + + + Offered + + + + + Policy + + + + + Rejected + + + + + Renewed + + + + + Revoked + + + + + Resolved + + + + + Terminated + + + + + + + Status of the publication of contract content. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Financial instrument which may be used to reimburse or pay for health care products and services. Includes both insurance and self-payment. + + + + + Financial instrument which may be used to reimburse or pay for health care products and services. Includes both insurance and self-payment. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A unique identifier assigned to this coverage. + + + + + The status of the resource instance. + + + + + The type of coverage: social program, medical plan, accident coverage (workers compensation, auto), group health or payment by an individual or organization. + + + + + The party who 'owns' the insurance policy. + + + + + The party who has signed-up for or 'owns' the contractual relationship to the policy or to whom the benefit of the policy for services rendered to them or their family is due. + + + + + The insurer assigned ID for the Subscriber. + + + + + The party who benefits from the insurance coverage; the patient when products and/or services are provided. + + + + + A unique identifier for a dependent under the coverage. + + + + + The relationship of beneficiary (patient) to the subscriber. + + + + + Time period during which the coverage is in force. A missing start date indicates the start date isn't known, a missing end date means the coverage is continuing to be in force. + + + + + The program or plan underwriter or payor including both insurance and non-insurance agreements, such as patient-pay agreements. + + + + + A suite of underwriter specific classifiers. + + + + + The order of applicability of this coverage relative to other coverages which are currently in force. Note, there may be gaps in the numbering and this does not imply primary, secondary etc. as the specific positioning of coverages depends upon the episode of care. + + + + + The insurer-specific identifier for the insurer-defined network of providers to which the beneficiary may seek treatment which will be covered at the 'in-network' rate, otherwise 'out of network' terms and conditions apply. + + + + + A suite of codes indicating the cost category and associated amount which have been detailed in the policy and may have been included on the health card. + + + + + When 'subrogation=true' this insurance instance has been included not for adjudication but to provide insurers with the details to recover costs. + + + + + The policy(s) which constitute this insurance coverage. + + + + + + + + + Financial instrument which may be used to reimburse or pay for health care products and services. Includes both insurance and self-payment. + + + + + + + The type of classification for which an insurer-specific class label or number and optional name is provided, for example may be used to identify a class of coverage or employer group, Policy, Plan. + + + + + The alphanumeric string value associated with the insurer issued label. + + + + + A short description for the class. + + + + + + + + + Financial instrument which may be used to reimburse or pay for health care products and services. Includes both insurance and self-payment. + + + + + + + The category of patient centric costs associated with treatment. + + + + + The amount due from the patient for the cost category. + + + + + + + A suite of codes indicating exceptions or reductions to patient costs and their effective periods. + + + + + + + + + Financial instrument which may be used to reimburse or pay for health care products and services. Includes both insurance and self-payment. + + + + + + + The code for the specific exception. + + + + + The timeframe during when the exception is in force. + + + + + + + + + The CoverageEligibilityRequest provides patient and insurance coverage information to an insurer for them to respond, in the form of an CoverageEligibilityResponse, with information regarding whether the stated coverage is valid and in-force and optionally to provide the insurance details of the policy. + + + + + The CoverageEligibilityRequest provides patient and insurance coverage information to an insurer for them to respond, in the form of an CoverageEligibilityResponse, with information regarding whether the stated coverage is valid and in-force and optionally to provide the insurance details of the policy. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A unique identifier assigned to this coverage eligiblity request. + + + + + The status of the resource instance. + + + + + When the requestor expects the processor to complete processing. + + + + + Code to specify whether requesting: prior authorization requirements for some service categories or billing codes; benefits for coverages specified or discovered; discovery and return of coverages for the patient; and/or validation that the specified coverage is in-force at the date/period specified or 'now' if not specified. + + + + + The party who is the beneficiary of the supplied coverage and for whom eligibility is sought. + + + + + The date or dates when the enclosed suite of services were performed or completed. + + + + + + + The date when this resource was created. + + + + + Person who created the request. + + + + + The provider which is responsible for the request. + + + + + The Insurer who issued the coverage in question and is the recipient of the request. + + + + + Facility where the services are intended to be provided. + + + + + Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. + + + + + Financial instruments for reimbursement for the health care products and services. + + + + + Service categories or billable services for which benefit details and/or an authorization prior to service delivery may be required by the payor. + + + + + + + + + The CoverageEligibilityRequest provides patient and insurance coverage information to an insurer for them to respond, in the form of an CoverageEligibilityResponse, with information regarding whether the stated coverage is valid and in-force and optionally to provide the insurance details of the policy. + + + + + + + A number to uniquely identify supporting information entries. + + + + + Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. + + + + + The supporting materials are applicable for all detail items, product/servce categories and specific billing codes. + + + + + + + + + The CoverageEligibilityRequest provides patient and insurance coverage information to an insurer for them to respond, in the form of an CoverageEligibilityResponse, with information regarding whether the stated coverage is valid and in-force and optionally to provide the insurance details of the policy. + + + + + + + A flag to indicate that this Coverage is to be used for evaluation of this request when set to true. + + + + + Reference to the insurance card level information contained in the Coverage resource. The coverage issuing insurer will use these details to locate the patient's actual coverage within the insurer's information system. + + + + + A business agreement number established between the provider and the insurer for special business processing purposes. + + + + + + + + + The CoverageEligibilityRequest provides patient and insurance coverage information to an insurer for them to respond, in the form of an CoverageEligibilityResponse, with information regarding whether the stated coverage is valid and in-force and optionally to provide the insurance details of the policy. + + + + + + + Exceptions, special conditions and supporting information applicable for this service or product line. + + + + + Code to identify the general type of benefits under which products and services are provided. + + + + + This contains the product, service, drug or other billing code for the item. + + + + + Item typification or modifiers codes to convey additional context for the product or service. + + + + + The practitioner who is responsible for the product or service to be rendered to the patient. + + + + + The number of repetitions of a service or product. + + + + + The amount charged to the patient by the provider for a single unit. + + + + + Facility where the services will be provided. + + + + + Patient diagnosis for which care is sought. + + + + + The plan/proposal/order describing the proposed service in detail. + + + + + + + + + The CoverageEligibilityRequest provides patient and insurance coverage information to an insurer for them to respond, in the form of an CoverageEligibilityResponse, with information regarding whether the stated coverage is valid and in-force and optionally to provide the insurance details of the policy. + + + + + + + The nature of illness or problem in a coded form or as a reference to an external defined Condition. + + + + + + + + + + + + + Coverage auth-requirements + + + + + Coverage benefits + + + + + Coverage Discovery + + + + + Coverage Validation + + + + + + + A code specifying the types of information being requested. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + This resource provides eligibility and plan details from the processing of an CoverageEligibilityRequest resource. + + + + + This resource provides eligibility and plan details from the processing of an CoverageEligibilityRequest resource. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A unique identifier assigned to this coverage eligiblity request. + + + + + The status of the resource instance. + + + + + Code to specify whether requesting: prior authorization requirements for some service categories or billing codes; benefits for coverages specified or discovered; discovery and return of coverages for the patient; and/or validation that the specified coverage is in-force at the date/period specified or 'now' if not specified. + + + + + The party who is the beneficiary of the supplied coverage and for whom eligibility is sought. + + + + + The date or dates when the enclosed suite of services were performed or completed. + + + + + + + The date this resource was created. + + + + + The provider which is responsible for the request. + + + + + Reference to the original request resource. + + + + + The outcome of the request processing. + + + + + A human readable description of the status of the adjudication. + + + + + The Insurer who issued the coverage in question and is the author of the response. + + + + + Financial instruments for reimbursement for the health care products and services. + + + + + A reference from the Insurer to which these services pertain to be used on further communication and as proof that the request occurred. + + + + + A code for the form to be used for printing the content. + + + + + Errors encountered during the processing of the request. + + + + + + + + + This resource provides eligibility and plan details from the processing of an CoverageEligibilityRequest resource. + + + + + + + Reference to the insurance card level information contained in the Coverage resource. The coverage issuing insurer will use these details to locate the patient's actual coverage within the insurer's information system. + + + + + Flag indicating if the coverage provided is inforce currently if no service date(s) specified or for the whole duration of the service dates. + + + + + The term of the benefits documented in this response. + + + + + Benefits and optionally current balances, and authorization details by category or service. + + + + + + + + + This resource provides eligibility and plan details from the processing of an CoverageEligibilityRequest resource. + + + + + + + Code to identify the general type of benefits under which products and services are provided. + + + + + This contains the product, service, drug or other billing code for the item. + + + + + Item typification or modifiers codes to convey additional context for the product or service. + + + + + The practitioner who is eligible for the provision of the product or service. + + + + + True if the indicated class of service is excluded from the plan, missing or False indicates the product or service is included in the coverage. + + + + + A short name or tag for the benefit. + + + + + A richer description of the benefit or services covered. + + + + + Is a flag to indicate whether the benefits refer to in-network providers or out-of-network providers. + + + + + Indicates if the benefits apply to an individual or to the family. + + + + + The term or period of the values such as 'maximum lifetime benefit' or 'maximum annual visits'. + + + + + Benefits used to date. + + + + + A boolean flag indicating whether a preauthorization is required prior to actual service delivery. + + + + + Codes or comments regarding information or actions associated with the preauthorization. + + + + + A web location for obtaining requirements or descriptive information regarding the preauthorization. + + + + + + + + + This resource provides eligibility and plan details from the processing of an CoverageEligibilityRequest resource. + + + + + + + Classification of benefit being provided. + + + + + The quantity of the benefit which is permitted under the coverage. + + + + + + + + The quantity of the benefit which have been consumed to date. + + + + + + + + + + + + This resource provides eligibility and plan details from the processing of an CoverageEligibilityRequest resource. + + + + + + + An error code,from a specified code system, which details why the eligibility check could not be performed. + + + + + + + + + + + Coverage auth-requirements + + + + + Coverage benefits + + + + + Coverage Discovery + + + + + Coverage Validation + + + + + + + A code specifying the types of information being requested. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, Ineffective treatment frequency, Procedure-condition conflict, etc. + + + + + Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, Ineffective treatment frequency, Procedure-condition conflict, etc. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifier associated with the detected issue record. + + + + + Indicates the status of the detected issue. + + + + + Identifies the general type of issue identified. + + + + + Indicates the degree of importance associated with the identified issue based on the potential impact on the patient. + + + + + Indicates the patient whose record the detected issue is associated with. + + + + + The date or period when the detected issue was initially identified. + + + + + + + Individual or device responsible for the issue being raised. For example, a decision support application or a pharmacist conducting a medication review. + + + + + Indicates the resource representing the current activity or proposed activity that is potentially problematic. + + + + + Supporting evidence or manifestations that provide the basis for identifying the detected issue such as a GuidanceResponse or MeasureReport. + + + + + A textual explanation of the detected issue. + + + + + The literature, knowledge-base or similar reference that describes the propensity for the detected issue identified. + + + + + Indicates an action that has been taken or is committed to reduce or eliminate the likelihood of the risk identified by the detected issue from manifesting. Can also reflect an observation of known mitigating factors that may reduce/eliminate the need for any action. + + + + + + + + + Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, Ineffective treatment frequency, Procedure-condition conflict, etc. + + + + + + + A manifestation that led to the recording of this detected issue. + + + + + Links to resources that constitute evidence for the detected issue such as a GuidanceResponse or MeasureReport. + + + + + + + + + Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, Ineffective treatment frequency, Procedure-condition conflict, etc. + + + + + + + Describes the action that was taken or the observation that was made that reduces/eliminates the risk associated with the identified issue. + + + + + Indicates when the mitigating action was documented. + + + + + Identifies the practitioner who determined the mitigation and takes responsibility for the mitigation step occurring. + + + + + + + + + + + Registered + + + + + Preliminary + + + + + Final + + + + + Amended + + + + + Corrected + + + + + Cancelled + + + + + Entered in Error + + + + + Unknown + + + + + + + Indicates the status of the identified issue. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + High + + + + + Moderate + + + + + Low + + + + + + + Indicates the potential degree of impact of the identified issue on the patient. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device. + + + + + A type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Unique instance identifiers assigned to a device by manufacturers other organizations or owners. + + + + + The reference to the definition for the device. + + + + + Unique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold. + + + + + Status of the Device availability. + + + + + Reason for the dtatus of the Device availability. + + + + + The distinct identification string as required by regulation for a human cell, tissue, or cellular and tissue-based product. + + + + + A name of the manufacturer. + + + + + The date and time when the device was manufactured. + + + + + The date and time beyond which this device is no longer valid or should not be used (if applicable). + + + + + Lot number assigned by the manufacturer. + + + + + The serial number assigned by the organization when the device was manufactured. + + + + + This represents the manufacturer's name of the device as provided by the device, from a UDI label, or by a person describing the Device. This typically would be used when a person provides the name(s) or when the device represents one of the names available from DeviceDefinition. + + + + + The model number for the device. + + + + + The part number of the device. + + + + + The kind or type of device. + + + + + The capabilities supported on a device, the standards to which the device conforms for a particular purpose, and used for the communication. + + + + + The actual design of the device or software version running on the device. + + + + + The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties. + + + + + Patient information, If the device is affixed to a person. + + + + + An organization that is responsible for the provision and ongoing maintenance of the device. + + + + + Contact details for an organization or a particular human that is responsible for the device. + + + + + The place where the device can be found. + + + + + A network address on which the device may be contacted directly. + + + + + Descriptive information, usage information or implantation information that is not captured in an existing element. + + + + + Provides additional safety characteristics about a medical device. For example devices containing latex. + + + + + The parent device. + + + + + + + + + A type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device. + + + + + + + The device identifier (DI) is a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device. + + + + + Organization that is charged with issuing UDIs for devices. For example, the US FDA issuers include : +1) GS1: +http://hl7.org/fhir/NamingSystem/gs1-di, +2) HIBCC: +http://hl7.org/fhir/NamingSystem/hibcc-dI, +3) ICCBBA for blood containers: +http://hl7.org/fhir/NamingSystem/iccbba-blood-di, +4) ICCBA for other devices: +http://hl7.org/fhir/NamingSystem/iccbba-other-di. + + + + + The identity of the authoritative source for UDI generation within a jurisdiction. All UDIs are globally unique within a single namespace with the appropriate repository uri as the system. For example, UDIs of devices managed in the U.S. by the FDA, the value is http://hl7.org/fhir/NamingSystem/fda-udi. + + + + + The full UDI carrier of the Automatic Identification and Data Capture (AIDC) technology representation of the barcode string as printed on the packaging of the device - e.g., a barcode or RFID. Because of limitations on character sets in XML and the need to round-trip JSON data through XML, AIDC Formats *SHALL* be base64 encoded. + + + + + The full UDI carrier as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device. + + + + + A coded entry to indicate how the data was entered. + + + + + + + + + A type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device. + + + + + + + The name of the device. + + + + + The type of deviceName. +UDILabelName | UserFriendlyName | PatientReportedName | ManufactureDeviceName | ModelName. + + + + + + + + + A type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device. + + + + + + + The standard that is used to operate and communicate. + + + + + The version of the standard that is used to operate and communicate. + + + + + + + + + A type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device. + + + + + + + The type of the device version. + + + + + A single component of the device version. + + + + + The version text. + + + + + + + + + A type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device. + + + + + + + Code that specifies the property DeviceDefinitionPropetyCode (Extensible). + + + + + Property value as a quantity. + + + + + Property value as a code, e.g., NTP4 (synced to NTP). + + + + + + + + + + + Active + + + + + Inactive + + + + + Entered in Error + + + + + Unknown + + + + + + + The availability status of the device. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + UDI Label name + + + + + User Friendly name + + + + + Patient Reported name + + + + + Manufacturer name + + + + + Model name + + + + + other + + + + + + + The type of name the device is referred by. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Barcode + + + + + RFID + + + + + Manual + + + + + Card + + + + + Self Reported + + + + + Unknown + + + + + + + Codes to identify how UDI data was entered. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + The characteristics, operational status and capabilities of a medical-related component of a medical device. + + + + + The characteristics, operational status and capabilities of a medical-related component of a medical device. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Unique instance identifiers assigned to a device by the software, manufacturers, other organizations or owners. For example: handle ID. + + + + + Unique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold. + + + + + A name of the manufacturer. + + + + + + + A name given to the device to identify it. + + + + + The model number for the device. + + + + + What kind of device or device system this is. + + + + + The capabilities supported on a device, the standards to which the device conforms for a particular purpose, and used for the communication. + + + + + The available versions of the device, e.g., software versions. + + + + + Safety characteristics of the device. + + + + + Shelf Life and storage information. + + + + + Dimensions, color etc. + + + + + Language code for the human-readable text strings produced by the device (all supported). + + + + + Device capabilities. + + + + + The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties. + + + + + An organization that is responsible for the provision and ongoing maintenance of the device. + + + + + Contact details for an organization or a particular human that is responsible for the device. + + + + + A network address on which the device may be contacted directly. + + + + + Access to on-line information about the device. + + + + + Descriptive information, usage information or implantation information that is not captured in an existing element. + + + + + The quantity of the device present in the packaging (e.g. the number of devices present in a pack, or the number of devices in the same package of the medicinal product). + + + + + The parent device it can be part of. + + + + + A substance used to create the material(s) of which the device is made. + + + + + + + + + The characteristics, operational status and capabilities of a medical-related component of a medical device. + + + + + + + The identifier that is to be associated with every Device that references this DeviceDefintiion for the issuer and jurisdication porvided in the DeviceDefinition.udiDeviceIdentifier. + + + + + The organization that assigns the identifier algorithm. + + + + + The jurisdiction to which the deviceIdentifier applies. + + + + + + + + + The characteristics, operational status and capabilities of a medical-related component of a medical device. + + + + + + + The name of the device. + + + + + The type of deviceName. +UDILabelName | UserFriendlyName | PatientReportedName | ManufactureDeviceName | ModelName. + + + + + + + + + The characteristics, operational status and capabilities of a medical-related component of a medical device. + + + + + + + The standard that is used to operate and communicate. + + + + + The version of the standard that is used to operate and communicate. + + + + + + + + + The characteristics, operational status and capabilities of a medical-related component of a medical device. + + + + + + + Type of capability. + + + + + Description of capability. + + + + + + + + + The characteristics, operational status and capabilities of a medical-related component of a medical device. + + + + + + + Code that specifies the property DeviceDefinitionPropetyCode (Extensible). + + + + + Property value as a quantity. + + + + + Property value as a code, e.g., NTP4 (synced to NTP). + + + + + + + + + The characteristics, operational status and capabilities of a medical-related component of a medical device. + + + + + + + The substance. + + + + + Indicates an alternative material of the device. + + + + + Whether the substance is a known or suspected allergen. + + + + + + + + + Describes a measurement, calculation or setting capability of a medical device. + + + + + Describes a measurement, calculation or setting capability of a medical device. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Unique instance identifiers assigned to a device by the device or gateway software, manufacturers, other organizations or owners. For example: handle ID. + + + + + Describes the type of the metric. For example: Heart Rate, PEEP Setting, etc. + + + + + Describes the unit that an observed value determined for this metric will have. For example: Percent, Seconds, etc. + + + + + Describes the link to the Device that this DeviceMetric belongs to and that contains administrative device information such as manufacturer, serial number, etc. + + + + + Describes the link to the Device that this DeviceMetric belongs to and that provide information about the location of this DeviceMetric in the containment structure of the parent Device. An example would be a Device that represents a Channel. This reference can be used by a client application to distinguish DeviceMetrics that have the same type, but should be interpreted based on their containment location. + + + + + Indicates current operational state of the device. For example: On, Off, Standby, etc. + + + + + Describes the color representation for the metric. This is often used to aid clinicians to track and identify parameter types by color. In practice, consider a Patient Monitor that has ECG/HR and Pleth for example; the parameters are displayed in different characteristic colors, such as HR-blue, BP-green, and PR and SpO2- magenta. + + + + + Indicates the category of the observation generation process. A DeviceMetric can be for example a setting, measurement, or calculation. + + + + + Describes the measurement repetition time. This is not necessarily the same as the update period. The measurement repetition time can range from milliseconds up to hours. An example for a measurement repetition time in the range of milliseconds is the sampling rate of an ECG. An example for a measurement repetition time in the range of hours is a NIBP that is triggered automatically every hour. The update period may be different than the measurement repetition time, if the device does not update the published observed value with the same frequency as it was measured. + + + + + Describes the calibrations that have been performed or that are required to be performed. + + + + + + + + + Describes a measurement, calculation or setting capability of a medical device. + + + + + + + Describes the type of the calibration method. + + + + + Describes the state of the calibration. + + + + + Describes the time last calibration has been performed. + + + + + + + + + + + Unspecified + + + + + Offset + + + + + Gain + + + + + Two Point + + + + + + + Describes the type of a metric calibration. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Color Black + + + + + Color Red + + + + + Color Green + + + + + Color Yellow + + + + + Color Blue + + + + + Color Magenta + + + + + Color Cyan + + + + + Color White + + + + + + + Describes the typical color of representation. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Not Calibrated + + + + + Calibration Required + + + + + Calibrated + + + + + Unspecified + + + + + + + Describes the state of a metric calibration. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + On + + + + + Off + + + + + Standby + + + + + Entered In Error + + + + + + + Describes the operational status of the DeviceMetric. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Measurement + + + + + Setting + + + + + Calculation + + + + + Unspecified + + + + + + + Describes the category of the metric. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Represents a request for a patient to employ a medical device. The device may be an implantable device, or an external assistive device, such as a walker. + + + + + Represents a request for a patient to employ a medical device. The device may be an implantable device, or an external assistive device, such as a walker. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifiers assigned to this order by the orderer or by the receiver. + + + + + The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest. + + + + + The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest. + + + + + Plan/proposal/order fulfilled by this request. + + + + + The request takes the place of the referenced completed or terminated request(s). + + + + + Composite request this is part of. + + + + + The status of the request. + + + + + Whether the request is a proposal, plan, an original order or a reflex order. + + + + + Indicates how quickly the {{title}} should be addressed with respect to other requests. + + + + + The details of the device to be used. + + + + + + + Specific parameters for the ordered item. For example, the prism value for lenses. + + + + + The patient who will use the device. + + + + + An encounter that provides additional context in which this request is made. + + + + + The timing schedule for the use of the device. The Schedule data type allows many different expressions, for example. "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013". + + + + + + + + When the request transitioned to being actionable. + + + + + The individual who initiated the request and has responsibility for its activation. + + + + + Desired type of performer for doing the diagnostic testing. + + + + + The desired performer for doing the diagnostic testing. + + + + + Reason or justification for the use of this device. + + + + + Reason or justification for the use of this device. + + + + + Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service. + + + + + Additional clinical information about the patient that may influence the request fulfilment. For example, this may include where on the subject's body the device will be used (i.e. the target site). + + + + + Details about this request that were not represented at all or sufficiently in one of the attributes provided in a class. These may include for example a comment, an instruction, or a note associated with the statement. + + + + + Key events in the history of the request. + + + + + + + + + Represents a request for a patient to employ a medical device. The device may be an implantable device, or an external assistive device, such as a walker. + + + + + + + A code or string that identifies the device detail being asserted. + + + + + The value of the device detail. + + + + + + + + + + + + + A record of a device being used by a patient where the record is the result of a report from the patient or another clinician. + + + + + A record of a device being used by a patient where the record is the result of a report from the patient or another clinician. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An external identifier for this statement such as an IRI. + + + + + A plan, proposal or order that is fulfilled in whole or in part by this DeviceUseStatement. + + + + + A code representing the patient or other source's judgment about the state of the device used that this statement is about. Generally this will be active or completed. + + + + + The patient who used the device. + + + + + Allows linking the DeviceUseStatement to the underlying Request, or to other information that supports or is used to derive the DeviceUseStatement. + + + + + How often the device was used. + + + + + + + + The time at which the statement was made/recorded. + + + + + Who reported the device was being used by the patient. + + + + + The details of the device used. + + + + + Reason or justification for the use of the device. + + + + + Indicates another resource whose existence justifies this DeviceUseStatement. + + + + + Indicates the anotomic location on the subject's body where the device was used ( i.e. the target). + + + + + Details about the device statement that were not represented at all or sufficiently in one of the attributes provided in a class. These may include for example a comment, an instruction, or a note associated with the statement. + + + + + + + + + + + Active + + + + + Completed + + + + + Entered in Error + + + + + Intended + + + + + Stopped + + + + + On Hold + + + + + + + A coded concept indicating the current status of the Device Usage. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + The findings and interpretation of diagnostic tests performed on patients, groups of patients, devices, and locations, and/or specimens derived from these. The report includes clinical context such as requesting and provider information, and some mix of atomic results, images, textual and coded interpretations, and formatted representation of diagnostic reports. + + + + + The findings and interpretation of diagnostic tests performed on patients, groups of patients, devices, and locations, and/or specimens derived from these. The report includes clinical context such as requesting and provider information, and some mix of atomic results, images, textual and coded interpretations, and formatted representation of diagnostic reports. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifiers assigned to this report by the performer or other systems. + + + + + Details concerning a service requested. + + + + + The status of the diagnostic report. + + + + + A code that classifies the clinical discipline, department or diagnostic service that created the report (e.g. cardiology, biochemistry, hematology, MRI). This is used for searching, sorting and display purposes. + + + + + A code or name that describes this diagnostic report. + + + + + The subject of the report. Usually, but not always, this is a patient. However, diagnostic services also perform analyses on specimens collected from a variety of other sources. + + + + + The healthcare event (e.g. a patient and healthcare provider interaction) which this DiagnosticReport is about. + + + + + The time or time-period the observed values are related to. When the subject of the report is a patient, this is usually either the time of the procedure or of specimen collection(s), but very often the source of the date/time is not known, only the date/time itself. + + + + + + + The date and time that this version of the report was made available to providers, typically after the report was reviewed and verified. + + + + + The diagnostic service that is responsible for issuing the report. + + + + + The practitioner or organization that is responsible for the report's conclusions and interpretations. + + + + + Details about the specimens on which this diagnostic report is based. + + + + + [Observations](observation.html) that are part of this diagnostic report. + + + + + One or more links to full details of any imaging performed during the diagnostic investigation. Typically, this is imaging performed by DICOM enabled modalities, but this is not required. A fully enabled PACS viewer can use this information to provide views of the source images. + + + + + A list of key images associated with this report. The images are generally created during the diagnostic process, and may be directly of the patient, or of treated specimens (i.e. slides of interest). + + + + + Concise and clinically contextualized summary conclusion (interpretation/impression) of the diagnostic report. + + + + + One or more codes that represent the summary conclusion (interpretation/impression) of the diagnostic report. + + + + + Rich text representation of the entire result as issued by the diagnostic service. Multiple formats are allowed but they SHALL be semantically equivalent. + + + + + + + + + The findings and interpretation of diagnostic tests performed on patients, groups of patients, devices, and locations, and/or specimens derived from these. The report includes clinical context such as requesting and provider information, and some mix of atomic results, images, textual and coded interpretations, and formatted representation of diagnostic reports. + + + + + + + A comment about the image. Typically, this is used to provide an explanation for why the image is included, or to draw the viewer's attention to important features. + + + + + Reference to the image source. + + + + + + + + + + + Registered + + + + + Partial + + + + + Preliminary + + + + + Final + + + + + Amended + + + + + Corrected + + + + + Appended + + + + + Cancelled + + + + + Entered in Error + + + + + Unknown + + + + + + + The status of the diagnostic report. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A collection of documents compiled for a purpose together with metadata that applies to the collection. + + + + + A collection of documents compiled for a purpose together with metadata that applies to the collection. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A single identifier that uniquely identifies this manifest. Principally used to refer to the manifest in non-FHIR contexts. + + + + + Other identifiers associated with the document manifest, including version independent identifiers. + + + + + The status of this document manifest. + + + + + The code specifying the type of clinical activity that resulted in placing the associated content into the DocumentManifest. + + + + + Who or what the set of documents is about. The documents can be about a person, (patient or healthcare practitioner), a device (i.e. machine) or even a group of subjects (such as a document about a herd of farm animals, or a set of patients that share a common exposure). If the documents cross more than one subject, then more than one subject is allowed here (unusual use case). + + + + + When the document manifest was created for submission to the server (not necessarily the same thing as the actual resource last modified time, since it may be modified, replicated, etc.). + + + + + Identifies who is the author of the manifest. Manifest author is not necessarly the author of the references included. + + + + + A patient, practitioner, or organization for which this set of documents is intended. + + + + + Identifies the source system, application, or software that produced the document manifest. + + + + + Human-readable description of the source document. This is sometimes known as the "title". + + + + + The list of Resources that consist of the parts of this manifest. + + + + + Related identifiers or resources associated with the DocumentManifest. + + + + + + + + + A collection of documents compiled for a purpose together with metadata that applies to the collection. + + + + + + + Related identifier to this DocumentManifest. For example, Order numbers, accession numbers, XDW workflow numbers. + + + + + Related Resource to this DocumentManifest. For example, Order, ServiceRequest, Procedure, EligibilityRequest, etc. + + + + + + + + + A reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text. + + + + + A reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Document identifier as assigned by the source of the document. This identifier is specific to this version of the document. This unique identifier may be used elsewhere to identify this version of the document. + + + + + Other identifiers associated with the document, including version independent identifiers. + + + + + The status of this document reference. + + + + + The status of the underlying document. + + + + + Specifies the particular kind of document referenced (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the document referenced. + + + + + A categorization for the type of document referenced - helps for indexing and searching. This may be implied by or derived from the code specified in the DocumentReference.type. + + + + + Who or what the document is about. The document can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of farm animals, or a set of patients that share a common exposure). + + + + + When the document reference was created. + + + + + Identifies who is responsible for adding the information to the document. + + + + + Which person or organization authenticates that this document is valid. + + + + + Identifies the organization or group who is responsible for ongoing maintenance of and access to the document. + + + + + Relationships that this document has with other document references that already exist. + + + + + Human-readable description of the source document. + + + + + A set of Security-Tag codes specifying the level of privacy/security of the Document. Note that DocumentReference.meta.security contains the security labels of the "reference" to the document, while DocumentReference.securityLabel contains a snapshot of the security labels on the document the reference refers to. + + + + + The document and format referenced. There may be multiple content element repetitions, each with a different format. + + + + + The clinical context in which the document was prepared. + + + + + + + + + A reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text. + + + + + + + The type of relationship that this document has with anther document. + + + + + The target document of this relationship. + + + + + + + + + A reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text. + + + + + + + The document or URL of the document along with critical metadata to prove content has integrity. + + + + + An identifier of the document encoding, structure, and template that the document conforms to beyond the base format indicated in the mimeType. + + + + + + + + + A reference to a document of any kind for any purpose. Provides metadata about the document so that the document can be discovered and managed. The scope of a document is any seralized object with a mime-type, so includes formal patient centric documents (CDA), cliical notes, scanned paper, and non-patient specific documents like policy text. + + + + + + + Describes the clinical encounter or type of care that the document content is associated with. + + + + + This list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the type Code, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act. + + + + + The time period over which the service that is described by the document was provided. + + + + + The kind of facility where the patient was seen. + + + + + This property may convey specifics about the practice setting where the content was created, often reflecting the clinical specialty. + + + + + The Patient Information as known when the document was published. May be a reference to a version specific, or contained. + + + + + Related identifiers or resources associated with the DocumentReference. + + + + + + + + + The EffectEvidenceSynthesis resource describes the difference in an outcome between exposures states in a population where the effect estimate is derived from a combination of research studies. + + + + + The EffectEvidenceSynthesis resource describes the difference in an outcome between exposures states in a population where the effect estimate is derived from a combination of research studies. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this effect evidence synthesis when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this effect evidence synthesis is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the effect evidence synthesis is stored on different servers. + + + + + A formal identifier that is used to identify this effect evidence synthesis when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the effect evidence synthesis when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the effect evidence synthesis 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. + + + + + A natural language name identifying the effect evidence synthesis. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the effect evidence synthesis. + + + + + The status of this effect evidence synthesis. Enables tracking the life-cycle of the content. + + + + + The date (and optionally time) when the effect evidence synthesis was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the effect evidence synthesis changes. + + + + + The name of the organization or individual that published the effect evidence synthesis. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the effect evidence synthesis from a consumer's perspective. + + + + + A human-readable string to clarify or explain concepts about the resource. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate effect evidence synthesis instances. + + + + + A legal or geographic region in which the effect evidence synthesis is intended to be used. + + + + + A copyright statement relating to the effect evidence synthesis and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the effect evidence synthesis. + + + + + The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. + + + + + The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. + + + + + The period during which the effect evidence synthesis content was or is planned to be in active use. + + + + + Descriptive topics related to the content of the EffectEvidenceSynthesis. Topics provide a high-level categorization grouping types of EffectEvidenceSynthesiss that can be useful for filtering and searching. + + + + + An individiual or organization primarily involved in the creation and maintenance of the content. + + + + + An individual or organization primarily responsible for internal coherence of the content. + + + + + An individual or organization primarily responsible for review of some aspect of the content. + + + + + An individual or organization responsible for officially endorsing the content for use in some setting. + + + + + Related artifacts such as additional documentation, justification, or bibliographic references. + + + + + Type of synthesis eg meta-analysis. + + + + + Type of study eg randomized trial. + + + + + A reference to a EvidenceVariable resource that defines the population for the research. + + + + + A reference to a EvidenceVariable resource that defines the exposure for the research. + + + + + A reference to a EvidenceVariable resource that defines the comparison exposure for the research. + + + + + A reference to a EvidenceVariable resomece that defines the outcome for the research. + + + + + A description of the size of the sample involved in the synthesis. + + + + + A description of the results for each exposure considered in the effect estimate. + + + + + The estimated effect of the exposure variant. + + + + + A description of the certainty of the effect estimate. + + + + + + + + + The EffectEvidenceSynthesis resource describes the difference in an outcome between exposures states in a population where the effect estimate is derived from a combination of research studies. + + + + + + + Human-readable summary of sample size. + + + + + Number of studies included in this evidence synthesis. + + + + + Number of participants included in this evidence synthesis. + + + + + + + + + The EffectEvidenceSynthesis resource describes the difference in an outcome between exposures states in a population where the effect estimate is derived from a combination of research studies. + + + + + + + Human-readable summary of results by exposure state. + + + + + Whether these results are for the exposure state or alternative exposure state. + + + + + Used to define variant exposure states such as low-risk state. + + + + + Reference to a RiskEvidenceSynthesis resource. + + + + + + + + + The EffectEvidenceSynthesis resource describes the difference in an outcome between exposures states in a population where the effect estimate is derived from a combination of research studies. + + + + + + + Human-readable summary of effect estimate. + + + + + Examples include relative risk and mean difference. + + + + + Used to define variant exposure states such as low-risk state. + + + + + The point estimate of the effect estimate. + + + + + Specifies the UCUM unit for the outcome. + + + + + A description of the precision of the estimate for the effect. + + + + + + + + + The EffectEvidenceSynthesis resource describes the difference in an outcome between exposures states in a population where the effect estimate is derived from a combination of research studies. + + + + + + + Examples include confidence interval and interquartile range. + + + + + Use 95 for a 95% confidence interval. + + + + + Lower bound of confidence interval. + + + + + Upper bound of confidence interval. + + + + + + + + + The EffectEvidenceSynthesis resource describes the difference in an outcome between exposures states in a population where the effect estimate is derived from a combination of research studies. + + + + + + + A rating of the certainty of the effect estimate. + + + + + A human-readable string to clarify or explain concepts about the resource. + + + + + A description of a component of the overall certainty. + + + + + + + + + The EffectEvidenceSynthesis resource describes the difference in an outcome between exposures states in a population where the effect estimate is derived from a combination of research studies. + + + + + + + Type of subcomponent of certainty rating. + + + + + A rating of a subcomponent of rating certainty. + + + + + A human-readable string to clarify or explain concepts about the resource. + + + + + + + + + + + Exposure + + + + + Exposure Alternative + + + + + + + Whether the results by exposure is describing the results for the primary exposure of interest (exposure) or the alternative state (exposureAlternative). + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. + + + + + An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifier(s) by which this encounter is known. + + + + + planned | arrived | triaged | in-progress | onleave | finished | cancelled +. + + + + + The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them. + + + + + Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations. + + + + + The class history permits the tracking of the encounters transitions without needing to go through the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transitions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kind of discharge from emergency to inpatient. + + + + + Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation). + + + + + Broad categorization of the service that is to be provided (e.g. cardiology). + + + + + Indicates the urgency of the encounter. + + + + + The patient or group present at the encounter. + + + + + Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem. The association is recorded on the encounter as these are typically created after the episode of care and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years). + + + + + The request this encounter satisfies (e.g. incoming referral or procedure request). + + + + + The list of people responsible for providing the service. + + + + + The appointment that scheduled this encounter. + + + + + The start and end time of the encounter. + + + + + Quantity of time the encounter lasted. This excludes the time during leaves of absence. + + + + + Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis. + + + + + Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis. + + + + + The list of diagnosis relevant to this encounter. + + + + + The set of accounts that may be used for billing for this Encounter. + + + + + Details about the admission to a healthcare service. + + + + + List of locations where the patient has been during this encounter. + + + + + The organization that is primarily responsible for this Encounter's services. This MAY be the same as the organization on the Patient record, however it could be different, such as if the actor performing the services was from an external organization (which may be billed seperately) for an external consultation. Refer to the example bundle showing an abbreviated set of Encounters for a colonoscopy. + + + + + Another Encounter of which this encounter is a part of (administratively or in time). + + + + + + + + + An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. + + + + + + + planned | arrived | triaged | in-progress | onleave | finished | cancelled +. + + + + + The time that the episode was in the specified status. + + + + + + + + + An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. + + + + + + + inpatient | outpatient | ambulatory | emergency +. + + + + + The time that the episode was in the specified class. + + + + + + + + + An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. + + + + + + + Role of participant in encounter. + + + + + The period of time that the specified participant participated in the encounter. These can overlap or be sub-sets of the overall encounter's period. + + + + + Persons involved in the encounter other than the patient. + + + + + + + + + An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. + + + + + + + Reason the encounter takes place, as specified using information from another resource. For admissions, this is the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure. + + + + + Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …). + + + + + Ranking of the diagnosis (for each role type). + + + + + + + + + An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. + + + + + + + Pre-admission identifier. + + + + + The location/organization from which the patient came before admission. + + + + + From where patient was admitted (physician referral, transfer). + + + + + Whether this hospitalization is a readmission and why if known. + + + + + Diet preferences reported by the patient. + + + + + Special courtesies (VIP, board member). + + + + + Any special requests that have been made for this hospitalization encounter, such as the provision of specific equipment or other things. + + + + + Location/organization to which the patient is discharged. + + + + + Category or kind of location after discharge. + + + + + + + + + An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. + + + + + + + The location where the encounter takes place. + + + + + The status of the participants' presence at the specified location during the period specified. If the participant is no longer at the location, then the period will have an end date/time. + + + + + This will be used to specify the required levels (bed/ward/room/etc.) desired to be recorded to simplify either messaging or query. + + + + + Time period during which the patient was present at the location. + + + + + + + + + + + Planned + + + + + Active + + + + + Reserved + + + + + Completed + + + + + + + The status of the location. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Planned + + + + + Arrived + + + + + Triaged + + + + + In Progress + + + + + On Leave + + + + + Finished + + + + + Cancelled + + + + + Entered in Error + + + + + Unknown + + + + + + + Current state of the encounter. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + The technical details of an endpoint that can be used for electronic services, such as for web services providing XDS.b or a REST endpoint for another FHIR server. This may include any security context information. + + + + + The technical details of an endpoint that can be used for electronic services, such as for web services providing XDS.b or a REST endpoint for another FHIR server. This may include any security context information. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifier for the organization that is used to identify the endpoint across multiple disparate systems. + + + + + active | suspended | error | off | test. + + + + + A coded value that represents the technical details of the usage of this endpoint, such as what WSDLs should be used in what way. (e.g. XDS.b/DICOM/cds-hook). + + + + + A friendly name that this endpoint can be referred to with. + + + + + The organization that manages this endpoint (even if technically another organization is hosting this in the cloud, it is the organization associated with the data). + + + + + Contact details for a human to contact about the subscription. The primary use of this for system administrator troubleshooting. + + + + + The interval during which the endpoint is expected to be operational. + + + + + The payload type describes the acceptable content that can be communicated on the endpoint. + + + + + The mime type to send the payload in - e.g. application/fhir+xml, application/fhir+json. If the mime type is not specified, then the sender could send any content (including no content depending on the connectionType). + + + + + The uri that describes the actual end-point to connect to. + + + + + Additional headers / information to send as part of the notification. + + + + + + + + + + + Active + + + + + Suspended + + + + + Error + + + + + Off + + + + + Entered in error + + + + + Test + + + + + + + The status of the endpoint. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + This resource provides the insurance enrollment details to the insurer regarding a specified coverage. + + + + + This resource provides the insurance enrollment details to the insurer regarding a specified coverage. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + The Response business identifier. + + + + + The status of the resource instance. + + + + + The date when this resource was created. + + + + + The Insurer who is target of the request. + + + + + The practitioner who is responsible for the services rendered to the patient. + + + + + Patient Resource. + + + + + Reference to the program or plan identification, underwriter or payor. + + + + + + + + + This resource provides enrollment and plan details from the processing of an EnrollmentRequest resource. + + + + + This resource provides enrollment and plan details from the processing of an EnrollmentRequest resource. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + The Response business identifier. + + + + + The status of the resource instance. + + + + + Original request resource reference. + + + + + Processing status: error, complete. + + + + + A description of the status of the adjudication. + + + + + The date when the enclosed suite of services were performed or completed. + + + + + The Insurer who produced this adjudicated response. + + + + + The practitioner who is responsible for the services rendered to the patient. + + + + + + + + + An association between a patient and an organization / healthcare provider(s) during which time encounters may occur. The managing organization assumes a level of responsibility for the patient during this time. + + + + + An association between a patient and an organization / healthcare provider(s) during which time encounters may occur. The managing organization assumes a level of responsibility for the patient during this time. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + The EpisodeOfCare may be known by different identifiers for different contexts of use, such as when an external agency is tracking the Episode for funding purposes. + + + + + planned | waitlist | active | onhold | finished | cancelled. + + + + + The history of statuses that the EpisodeOfCare has been through (without requiring processing the history of the resource). + + + + + A classification of the type of episode of care; e.g. specialist referral, disease management, type of funded care. + + + + + The list of diagnosis relevant to this episode of care. + + + + + The patient who is the focus of this episode of care. + + + + + The organization that has assumed the specific responsibilities for the specified duration. + + + + + The interval during which the managing organization assumes the defined responsibility. + + + + + Referral Request(s) that are fulfilled by this EpisodeOfCare, incoming referrals. + + + + + The practitioner that is the care manager/care coordinator for this patient. + + + + + The list of practitioners that may be facilitating this episode of care for specific purposes. + + + + + The set of accounts that may be used for billing for this EpisodeOfCare. + + + + + + + + + An association between a patient and an organization / healthcare provider(s) during which time encounters may occur. The managing organization assumes a level of responsibility for the patient during this time. + + + + + + + planned | waitlist | active | onhold | finished | cancelled. + + + + + The period during this EpisodeOfCare that the specific status applied. + + + + + + + + + An association between a patient and an organization / healthcare provider(s) during which time encounters may occur. The managing organization assumes a level of responsibility for the patient during this time. + + + + + + + A list of conditions/problems/diagnoses that this episode of care is intended to be providing care for. + + + + + Role that this diagnosis has within the episode of care (e.g. admission, billing, discharge …). + + + + + Ranking of the diagnosis (for each role type). + + + + + + + + + + + Planned + + + + + Waitlist + + + + + Active + + + + + On Hold + + + + + Finished + + + + + Cancelled + + + + + Entered in Error + + + + + + + The status of the episode of care. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + The EventDefinition resource provides a reusable description of when a particular event can occur. + + + + + The EventDefinition resource provides a reusable description of when a particular event can occur. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this event definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this event definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the event definition is stored on different servers. + + + + + A formal identifier that is used to identify this event definition when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the event definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the event definition 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. + + + + + A natural language name identifying the event definition. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the event definition. + + + + + An explanatory or alternate title for the event definition giving additional information about its content. + + + + + The status of this event definition. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this event definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + A code or group definition that describes the intended subject of the event definition. + + + + + + + The date (and optionally time) when the event definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the event definition changes. + + + + + The name of the organization or individual that published the event definition. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the event definition from a consumer's perspective. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate event definition instances. + + + + + A legal or geographic region in which the event definition is intended to be used. + + + + + Explanation of why this event definition is needed and why it has been designed as it has. + + + + + A detailed description of how the event definition is used from a clinical perspective. + + + + + A copyright statement relating to the event definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the event definition. + + + + + The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. + + + + + The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. + + + + + The period during which the event definition content was or is planned to be in active use. + + + + + Descriptive topics related to the module. Topics provide a high-level categorization of the module that can be useful for filtering and searching. + + + + + An individiual or organization primarily involved in the creation and maintenance of the content. + + + + + An individual or organization primarily responsible for internal coherence of the content. + + + + + An individual or organization primarily responsible for review of some aspect of the content. + + + + + An individual or organization responsible for officially endorsing the content for use in some setting. + + + + + Related resources such as additional documentation, justification, or bibliographic references. + + + + + The trigger element defines when the event occurs. If more than one trigger condition is specified, the event fires whenever any one of the trigger conditions is met. + + + + + + + + + The Evidence resource describes the conditional state (population and any exposures being compared within the population) and outcome (if specified) that the knowledge (evidence, assertion, recommendation) is about. + + + + + The Evidence resource describes the conditional state (population and any exposures being compared within the population) and outcome (if specified) that the knowledge (evidence, assertion, recommendation) is about. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this evidence when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this evidence is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the evidence is stored on different servers. + + + + + A formal identifier that is used to identify this evidence when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the evidence when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the evidence 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. To provide a version consistent with the Decision Support Service specification, use the format Major.Minor.Revision (e.g. 1.0.0). For more information on versioning knowledge assets, refer to the Decision Support Service specification. Note that a version is required for non-experimental active artifacts. + + + + + A natural language name identifying the evidence. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the evidence. + + + + + The short title provides an alternate title for use in informal descriptive contexts where the full, formal title is not necessary. + + + + + An explanatory or alternate title for the Evidence giving additional information about its content. + + + + + The status of this evidence. Enables tracking the life-cycle of the content. + + + + + The date (and optionally time) when the evidence was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the evidence changes. + + + + + The name of the organization or individual that published the evidence. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the evidence from a consumer's perspective. + + + + + A human-readable string to clarify or explain concepts about the resource. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate evidence instances. + + + + + A legal or geographic region in which the evidence is intended to be used. + + + + + A copyright statement relating to the evidence and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the evidence. + + + + + The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. + + + + + The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. + + + + + The period during which the evidence content was or is planned to be in active use. + + + + + Descriptive topics related to the content of the Evidence. Topics provide a high-level categorization grouping types of Evidences that can be useful for filtering and searching. + + + + + An individiual or organization primarily involved in the creation and maintenance of the content. + + + + + An individual or organization primarily responsible for internal coherence of the content. + + + + + An individual or organization primarily responsible for review of some aspect of the content. + + + + + An individual or organization responsible for officially endorsing the content for use in some setting. + + + + + Related artifacts such as additional documentation, justification, or bibliographic references. + + + + + A reference to a EvidenceVariable resource that defines the population for the research. + + + + + A reference to a EvidenceVariable resource that defines the exposure for the research. + + + + + A reference to a EvidenceVariable resomece that defines the outcome for the research. + + + + + + + + + The EvidenceVariable resource describes a "PICO" element that knowledge (evidence, assertion, recommendation) is about. + + + + + The EvidenceVariable resource describes a "PICO" element that knowledge (evidence, assertion, recommendation) is about. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this evidence variable when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this evidence variable is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the evidence variable is stored on different servers. + + + + + A formal identifier that is used to identify this evidence variable when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the evidence variable when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the evidence variable 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. To provide a version consistent with the Decision Support Service specification, use the format Major.Minor.Revision (e.g. 1.0.0). For more information on versioning knowledge assets, refer to the Decision Support Service specification. Note that a version is required for non-experimental active artifacts. + + + + + A natural language name identifying the evidence variable. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the evidence variable. + + + + + The short title provides an alternate title for use in informal descriptive contexts where the full, formal title is not necessary. + + + + + An explanatory or alternate title for the EvidenceVariable giving additional information about its content. + + + + + The status of this evidence variable. Enables tracking the life-cycle of the content. + + + + + The date (and optionally time) when the evidence variable was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the evidence variable changes. + + + + + The name of the organization or individual that published the evidence variable. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the evidence variable from a consumer's perspective. + + + + + A human-readable string to clarify or explain concepts about the resource. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate evidence variable instances. + + + + + A legal or geographic region in which the evidence variable is intended to be used. + + + + + A copyright statement relating to the evidence variable and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the evidence variable. + + + + + The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. + + + + + The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. + + + + + The period during which the evidence variable content was or is planned to be in active use. + + + + + Descriptive topics related to the content of the EvidenceVariable. Topics provide a high-level categorization grouping types of EvidenceVariables that can be useful for filtering and searching. + + + + + An individiual or organization primarily involved in the creation and maintenance of the content. + + + + + An individual or organization primarily responsible for internal coherence of the content. + + + + + An individual or organization primarily responsible for review of some aspect of the content. + + + + + An individual or organization responsible for officially endorsing the content for use in some setting. + + + + + Related artifacts such as additional documentation, justification, or bibliographic references. + + + + + The type of evidence element, a population, an exposure, or an outcome. + + + + + A characteristic that defines the members of the evidence element. Multiple characteristics are applied with "and" semantics. + + + + + + + + + The EvidenceVariable resource describes a "PICO" element that knowledge (evidence, assertion, recommendation) is about. + + + + + + + A short, natural language description of the characteristic that could be used to communicate the criteria to an end-user. + + + + + Define members of the evidence element using Codes (such as condition, medication, or observation), Expressions ( using an expression language such as FHIRPath or CQL) or DataRequirements (such as Diabetes diagnosis onset in the last year). + + + + + + + + + + + Use UsageContext to define the members of the population, such as Age Ranges, Genders, Settings. + + + + + When true, members with this characteristic are excluded from the element. + + + + + Indicates what effective period the study covers. + + + + + + + + + Indicates duration from the participant's study entry. + + + + + Indicates how elements are aggregated within the study effective period. + + + + + + + + + + + Dichotomous + + + + + Continuous + + + + + Descriptive + + + + + + + The possible types of variables for exposures or outcomes (E.g. Dichotomous, Continuous, Descriptive). + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Mean + + + + + Median + + + + + Mean of Study Means + + + + + Mean of Study Medins + + + + + Median of Study Means + + + + + Median of Study Medians + + + + + + + Possible group measure aggregates (E.g. Mean, Median). + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Example of workflow instance. + + + + + Example of workflow instance. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this example scenario when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this example scenario is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the example scenario is stored on different servers. + + + + + A formal identifier that is used to identify this example scenario when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the example scenario when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the example scenario 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. + + + + + A natural language name identifying the example scenario. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + The status of this example scenario. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this example scenario is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The date (and optionally time) when the example scenario was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the example scenario changes. (e.g. the 'content logical definition'). + + + + + The name of the organization or individual that published the example scenario. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate example scenario instances. + + + + + A legal or geographic region in which the example scenario is intended to be used. + + + + + A copyright statement relating to the example scenario and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the example scenario. + + + + + What the example scenario resource is created for. This should not be used to show the business purpose of the scenario itself, but the purpose of documenting a scenario. + + + + + Actor participating in the resource. + + + + + Each resource and each version that is present in the workflow. + + + + + Each major process - a group of operations. + + + + + Another nested workflow. + + + + + + + + + Example of workflow instance. + + + + + + + ID or acronym of actor. + + + + + The type of actor - person or system. + + + + + The name of the actor as shown in the page. + + + + + The description of the actor. + + + + + + + + + Example of workflow instance. + + + + + + + The id of the resource for referencing. + + + + + The type of the resource. + + + + + A short name for the resource instance. + + + + + Human-friendly description of the resource instance. + + + + + A specific version of the resource. + + + + + Resources contained in the instance (e.g. the observations contained in a bundle). + + + + + + + + + Example of workflow instance. + + + + + + + The identifier of a specific version of a resource. + + + + + The description of the resource version. + + + + + + + + + Example of workflow instance. + + + + + + + Each resource contained in the instance. + + + + + A specific version of a resource contained in the instance. + + + + + + + + + Example of workflow instance. + + + + + + + The diagram title of the group of operations. + + + + + A longer description of the group of operations. + + + + + Description of initial status before the process starts. + + + + + Description of final status after the process ends. + + + + + Each step of the process. + + + + + + + + + Example of workflow instance. + + + + + + + Nested process. + + + + + If there is a pause in the flow. + + + + + Each interaction or action. + + + + + Indicates an alternative step that can be taken instead of the operations on the base step in exceptional/atypical circumstances. + + + + + + + + + Example of workflow instance. + + + + + + + The sequential number of the interaction, e.g. 1.2.5. + + + + + The type of operation - CRUD. + + + + + The human-friendly name of the interaction. + + + + + Who starts the transaction. + + + + + Who receives the transaction. + + + + + A comment to be inserted in the diagram. + + + + + Whether the initiator is deactivated right after the transaction. + + + + + Whether the receiver is deactivated right after the transaction. + + + + + Each resource instance used by the initiator. + + + + + Each resource instance used by the responder. + + + + + + + + + Example of workflow instance. + + + + + + + The label to display for the alternative that gives a sense of the circumstance in which the alternative should be invoked. + + + + + A human-readable description of the alternative explaining when the alternative should occur rather than the base step. + + + + + What happens in each alternative option. + + + + + + + + + + + Person + + + + + System + + + + + + + The type of actor - system or human. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Account + Account + Cuenta + 账户 + + + + + ActivityDefinition + ActivityDefinition + DefinizioneAttivita + DefinicionDeActividad + 活动定义 + + + + + AdverseEvent + AdverseEvent + EventoAvverso + EventoAdverso + 不良事件 + + + + + AllergyIntolerance + AllergyIntolerance + AllergiaIntolleranza + IntoléranceAllergique + AllergiaIntolerancia + 变态反应与不耐性 + + + + + Appointment + Appointment + Appuntamento + RendezVous + Cita + 预约 + + + + + AppointmentResponse + AppointmentResponse + RispostaAppuntamento + RéponseRendezVous + CitaRespuesta + 预约响应 + + + + + AuditEvent + AuditEvent + ÉvènementSécurité + EventoSeguridad + 审计事件 + + + + + Basic + Basic + Basique + Basico + 初级资源 + + + + + Binary + Binary + Binario + Binaire + Binario + 二进制资源 + + + + + BiologicallyDerivedProduct + BiologicallyDerivedProduct + + + + + BodyStructure + BodyStructure + StrutturaDelCorpo + MorphologieDeCorps + EstructuraDelCuerpo + 身体结构 + + + + + Bundle + Bundle + Paquet + Paquete + 捆束 + + + + + CapabilityStatement + CapabilityStatement + DeclaracionDeCapacidad + 能力声明 + + + + + CarePlan + CarePlan + PianoDiCura + PlanDeSoins + PlanDeCuidado + 照护计划 + + + + + CareTeam + CareTeam + EquipoDeCuidado + 照护团队 + + + + + CatalogEntry + CatalogEntry + EntradaDeCatalogo + 条目定义 + + + + + ChargeItem + ChargeItem + CargoDeItem + 收费项目 + + + + + ChargeItemDefinition + ChargeItemDefinition + + + + + Claim + Claim + Réclamation + Reclamación / Factura + 赔单 + + + + + ClaimResponse + ClaimResponse + RéponseARéclamation + 赔单请求 + + + + + ClinicalImpression + ClinicalImpression + ImpressioneClinica + ImpressionClinique + HallazgoClinico + 临床印象 + + + + + CodeSystem + CodeSystem + SistemaDiCodifica + SistemaDeCodigos + 代码系统 + + + + + Communication + Communication + Comunicazione + Communication + Comunicación + 通讯 + + + + + CommunicationRequest + CommunicationRequest + RichiestaDiComunicazione + DemandeDeCommunication + ComunicaciónRequerimiento + 通讯请求 + + + + + CompartmentDefinition + CompartmentDefinition + DefinicionDeCompartimento + 逻辑区块定义 + + + + + Composition + Composition + Composizione + Composition + Composición + 组合式文书 + + + + + ConceptMap + ConceptMap + MappaDiConcetti + CarteDeConcepts + MapaDeConceptos + 概念映射 + + + + + Condition + Condition + Condizione + Condition + Condición + 情况 + + + + + Consent + Consent + Consenso + Consentimiento + 同意书 + + + + + Contract + Contract + Contratto + Contrat + Contato + 合同 + + + + + Coverage + Coverage + Copertura + Couverture + Cobertura + 保险责任 + + + + + CoverageEligibilityRequest + CoverageEligibilityRequest + RichiestaEleggibilitaCopertura + CouvertureDemandeEligibilité + 资格请求 + + + + + CoverageEligibilityResponse + CoverageEligibilityResponse + RispostaEleggibilitaCopertura + RéponseEligibilitéCouverture + 资格响应 + + + + + DetectedIssue + DetectedIssue + ProblemaRilevato + Problème Détecté + Problema-Detectado /ProblemaDetectado + 已发现问题 + + + + + Device + Device + Dispositivo + Dispositif + Dispositivo + 装置 + + + + + DeviceDefinition + DeviceDefinition + DéfinitionDeDispositif + DefiniciónDeDispositivo + 装置组件 + + + + + DeviceMetric + DeviceMetric + MétriqueDispositif + MetricaDeDispositivo + 装置指标 + + + + + DeviceRequest + DeviceRequest + RichiestaDispositivo + DemandeUtilisationDispositif + SolicitudDeDispositivo + 装置请求 + + + + + DeviceUseStatement + DeviceUseStatement + 装置使用声明 + + + + + DiagnosticReport + DiagnosticReport + RefertoDiagnostico + RapportDiagnostique + 诊断报告 + InformeDiagnostico + + + + + DocumentManifest + DocumentManifest + Manifeste + 文档清单 + ManifestoDocumento + + + + + DocumentReference + DocumentReference + RiferimentoDocumento + RéférenceDocument + ReferenciaDocumento + 文档引用 + + + + + DomainResource + DomainResource + RecursoDeDominio + 领域资源 + + + + + EffectEvidenceSynthesis + EffectEvidenceSynthesis + + + + + Encounter + Encounter + Venue + 就医过程 + Encuentro + + + + + Endpoint + Endpoint + Endpoint + 端点 + + + + + EnrollmentRequest + EnrollmentRequest + RichiestaIscrizione + DemandeInscription + SolicitudDeEnrolamiento + 保险注册请求 + + + + + EnrollmentResponse + EnrollmentResponse + RispostaIscrizione + RéponseInscription + RespuestaDeEnrolamiento + 保险注册响应 + + + + + EpisodeOfCare + EpisodeOfCare + EpisodioDiCura + ÉpisodeDeSoins + EpisodioDeCuidado + 照护服务节段 + + + + + EventDefinition + EventDefinition + DefinizioneEvento + DefinitionDeEvento + 事件定义 + + + + + Evidence + Evidence + + + + + EvidenceVariable + EvidenceVariable + + + + + ExampleScenario + ExampleScenario + ScenarioDiEsempio + EjemploDeEscenario + 示例场景 + + + + + ExplanationOfBenefit + ExplanationOfBenefit + ExplicationDuBénéfice + 赔付说明 + + + + + FamilyMemberHistory + FamilyMemberHistory + HistoireMembreFamille + HistorialMiembroFamiliar + 家族史 + + + + + Flag + Flag + Drapeau + Bandera + 标记 + + + + + Goal + Goal + But + Objetivo + 目标 + + + + + GraphDefinition + GraphDefinition + DefinitionGrafico + 图形定义 + + + + + Group + Group + Gruppo + Groupe + Grupo + 群组 + + + + + GuidanceResponse + GuidanceResponse + RespuestaDeOrientacion + 指导意见响应 + + + + + HealthcareService + HealthcareService + ServizioSanitario + ServiceDeSanté + ServicioDeCuidado + 医疗保健服务项目 + + + + + ImagingStudy + ImagingStudy + EtudeImagerie + EstudioImagen / EstudioImagen + 成像检查 + + + + + Immunization + Immunization + Immunizzazione + Immunisation + 免疫接种 + Inmunización + + + + + ImmunizationEvaluation + ImmunizationEvaluation + + + + + ImmunizationRecommendation + ImmunizationRecommendation + RecommendationImmunisation + 免疫接种建议 + RecomendaciónInmunización / + + + + + ImplementationGuide + ImplementationGuide + GuiaDeImplementacion + 实施指南 + + + + + InsurancePlan + InsurancePlan + + + + + Invoice + Invoice + + + + + Library + Library + Librería + 库 + + + + + Linkage + Linkage + Enlace / Conexión / Vinculo / Acoplamiento + 链接关系 + + + + + List + List + Lista + Liste + 列表 + Lista + + + + + Location + Location + Localisation + 位置 + Locacion + + + + + Measure + Measure + Misura + Medida + 指标 + + + + + MeasureReport + MeasureReport + ReporteMedida + 指标报告 + + + + + Media + Media + Media + Média + Medio + 媒体 + + + + + Medication + Medication + Médication + 药物 + Medicación /Medicamento + + + + + MedicationAdministration + MedicationAdministration + AdministrationMédicaments + 药物施用 + AdministraciónMedicación / AdministracionMedicamento + + + + + MedicationDispense + MedicationDispense + DispensationMédicaments + 药物配发 + DispensaciónMedicación /DispensacionMedicamento + + + + + MedicationKnowledge + MedicationKnowledge + + + + + MedicationRequest + MedicationRequest + PrescriptionMédicamenteuseTODO + 药物请求 + PrescripciónMedicaciónTODO /PrescripcionMedicamento + + + + + MedicationStatement + MedicationStatement + ÉtatMédication + 药物声明 + ResumenMedicación /ResumenMedicamento + + + + + MedicinalProduct + MedicinalProduct + ProdottoMedicinale + + + + + MedicinalProductAuthorization + MedicinalProductAuthorization + AutorizzazioneProdottoMedicinale + + + + + MedicinalProductContraindication + MedicinalProductContraindication + + + + + MedicinalProductIndication + MedicinalProductInteraction + + + + + MedicinalProductIngredient + MedicinalProductIngredient + IngredienteProdottoMedicinale + + + + + MedicinalProductInteraction + MedicinalProductInteraction + + + + + MedicinalProductManufactured + MedicinalProductManufactured + + + + + MedicinalProductPackaged + MedicinalProductPackaged + + + + + MedicinalProductPharmaceutical + MedicinalProductPharmaceutical + + + + + MedicinalProductUndesirableEffect + MedicinalProductUndesirableEffect + + + + + MessageDefinition + MessageDefinition + DefinizioneMessaggio + DefinicionMensaje + 消息定义 + + + + + MessageHeader + MessageHeader + EntêteMessage + 消息标头 + CabeceraMensaje + + + + + MolecularSequence + MolecularSequence + SecuenciaMolecular + 分子序列 + + + + + NamingSystem + NamingSystem + SystèmeDeNommage + SistemaDeNombres + 命名系统 + + + + + NutritionOrder + NutritionOrder + OrdreNutrition + OrdenNutrición + 营养医嘱 + + + + + Observation + Observation + Osservazione + Observation + 观察 + Observación + + + + + ObservationDefinition + ObservationDefinition + DefinizioneOsservazione + DefinicionDeEspecimen + 观察定义 + + + + + OperationDefinition + OperationDefinition + DefinizioneOperazione + DéfinitionOpération + DefinicionDeOperacion + 操作定义 + + + + + OperationOutcome + OperationOutcome + RisultatoOperazione + RésultatOpération + 操作结局 + ResultadoOperación + + + + + Organization + Organization + Organizzazione + Organisation + 组织机构 + Organización + + + + + OrganizationAffiliation + OrganizationAffiliation + + + + + Parameters + Parameters + Parametros + 参数 + + + + + Patient + Patient + Paziente + Patient + 患者 + Paciente + + + + + PaymentNotice + PaymentNotice + AvvisoDiPagamento + AvisPaiement + AvisoDePago + 付款通知 + + + + + PaymentReconciliation + PaymentReconciliation + RiconciliazionePagamento + RéconciliationPaiement + ConciliacionDePago + 付款对账 + + + + + Person + Person + Persona + Personne + Persona + 人员 + + + + + PlanDefinition + PlanDefinition + DefinicionDePlan + 计划定义 + + + + + Practitioner + Practitioner + Praticien + 执业人员 + Practicante / Profesional + + + + + PractitionerRole + PractitionerRole + RolProfesional + 执业人员角色 + + + + + Procedure + Procedure + Procedura + Procédure + 操作项目 + Procedimiento + + + + + Provenance + Provenance + Provenienza + Provenance + 出处 + Procedencia + + + + + Questionnaire + Questionnaire + Questionario + Questionnaire + 调查问卷 + Cuestionario + + + + + QuestionnaireResponse + QuestionnaireResponse + RispostaQuestionario + RéponseQuestionnaire + RespuestaAlCuestionario + 调查问卷答复 + + + + + RelatedPerson + RelatedPerson + PersonaCorrelata + PersonneEnRelation + PersonaRelacionada + 相关人员 + + + + + RequestGroup + RequestGroup + GruppoDiRichieste + GrupoDeSolicitudes + 请求分组 + + + + + ResearchDefinition + ResearchDefinition + + + + + ResearchElementDefinition + ResearchElementDefinition + + + + + ResearchStudy + ResearchStudy + EstudioDeInvestigacion + 调查研究 + + + + + ResearchSubject + ResearchSubject + SujetoDeInvestigacion + 研究主题 + + + + + Resource + Resource + Recurso + 资源 + + + + + RiskAssessment + RiskAssessment + ÉvaluationRisques + EvaluacionDeRiesgo + 风险评估 + + + + + RiskEvidenceSynthesis + RiskEvidenceSynthesis + + + + + Schedule + Schedule + Agenda + 日程安排 + + + + + SearchParameter + SearchParameter + ParametroDiRicerca + ParamètreRecherche + ParametroDeBusqueda + 搜索参数 + + + + + ServiceRequest + ServiceRequest + RichiestaDiServizio + DemandeService + PeticiónServicio + 服务项目请求 + + + + + Slot + Slot + Slot + 槽位 + Hueco / Zocalo / Espacio + + + + + Specimen + Specimen + Campione + Spécimen + 标本 + Especimen + + + + + SpecimenDefinition + SpecimenDefinition + DefinizioneCampione + DefinicionDeEspecimen + 标本定义 + + + + + StructureDefinition + StructureDefinition + DefinizioneStruttura + DéfinitionStructure + DefinicionDeEstructura + 结构定义 + + + + + StructureMap + StructureMap + MapaDeEstructura + 结构映射 + + + + + Subscription + Subscription + Sottoscrizione + Souscription + 订阅 + Suscripción + + + + + Substance + Substance + Sostanza + Substance + 物质 + Sustancia + + + + + SubstanceDefinition + SubstanceDefinition + + + + + SubstanceNucleicAcid + SubstanceNucleicAcid + + + + + SubstancePolymer + SubstancePolymer + + + + + SubstanceProtein + SubstanceProtein + + + + + SubstanceReferenceInformation + SubstanceReferenceInformation + + + + + SubstanceSourceMaterial + SubstanceSourceMaterial + + + + + SupplyDelivery + SupplyDelivery + Supply Livraison + 供应交付 + Entrega de Suministro + + + + + SupplyRequest + SupplyRequest + Demande d'approvisionnement + 供应请求 + Solicitud de Suministro + + + + + Task + Task + Tarea + 任务 + + + + + TerminologyCapabilities + TerminologyCapabilities + CapacidadTerminologica + 术语服务能力 + + + + + TestReport + TestReport + RapportTest + ReporteDePrueba + 测试报告 + + + + + TestScript + TestScript + ScriptTest + ScriptDePrueba + 测试脚本 + + + + + ValueSet + ValueSet + EnsembleValeurs + 取值集合 + ConjuntoValores / ConjuntoDeValores + + + + + VerificationResult + VerificationResult + + + + + VisionPrescription + VisionPrescription + PrescriptionVision + PrescripcionDeVision + 视力处方 + + + + + + + The type of resource. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A unique identifier assigned to this explanation of benefit. + + + + + The status of the resource instance. + + + + + The category of claim, e.g. oral, pharmacy, vision, institutional, professional. + + + + + A finer grained suite of claim type codes which may convey additional information such as Inpatient vs Outpatient and/or a specialty service. + + + + + A code to indicate whether the nature of the request is: to request adjudication of products and services previously rendered; or requesting authorization and adjudication for provision in the future; or requesting the non-binding adjudication of the listed products and services which could be provided in the future. + + + + + The party to whom the professional services and/or products have been supplied or are being considered and for whom actual for forecast reimbursement is sought. + + + + + The period for which charges are being submitted. + + + + + The date this resource was created. + + + + + Individual who created the claim, predetermination or preauthorization. + + + + + The party responsible for authorization, adjudication and reimbursement. + + + + + The provider which is responsible for the claim, predetermination or preauthorization. + + + + + The provider-required urgency of processing the request. Typical values include: stat, routine deferred. + + + + + A code to indicate whether and for whom funds are to be reserved for future claims. + + + + + A code, used only on a response to a preauthorization, to indicate whether the benefits payable have been reserved and for whom. + + + + + Other claims which are related to this claim such as prior submissions or claims for related services or for the same event. + + + + + Prescription to support the dispensing of pharmacy, device or vision products. + + + + + Original prescription which has been superseded by this prescription to support the dispensing of pharmacy services, medications or products. + + + + + The party to be reimbursed for cost of the products and services according to the terms of the policy. + + + + + A reference to a referral resource. + + + + + Facility where the services were provided. + + + + + The business identifier for the instance of the adjudication request: claim predetermination or preauthorization. + + + + + The business identifier for the instance of the adjudication response: claim, predetermination or preauthorization response. + + + + + The outcome of the claim, predetermination, or preauthorization processing. + + + + + A human readable description of the status of the adjudication. + + + + + Reference from the Insurer which is used in later communications which refers to this adjudication. + + + + + The timeframe during which the supplied preauthorization reference may be quoted on claims to obtain the adjudication as provided. + + + + + The members of the team who provided the products and services. + + + + + Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. + + + + + Information about diagnoses relevant to the claim items. + + + + + Procedures performed on the patient relevant to the billing items with the claim. + + + + + This indicates the relative order of a series of EOBs related to different coverages for the same suite of services. + + + + + Financial instruments for reimbursement for the health care products and services specified on the claim. + + + + + Details of a accident which resulted in injuries which required the products and services listed in the claim. + + + + + A claim line. Either a simple (a product or service) or a 'group' of details which can also be a simple items or groups of sub-details. + + + + + The first-tier service adjudications for payor added product or service lines. + + + + + The adjudication results which are presented at the header level rather than at the line-item or add-item levels. + + + + + Categorized monetary totals for the adjudication. + + + + + Payment details for the adjudication of the claim. + + + + + A code for the form to be used for printing the content. + + + + + The actual form, by reference or inclusion, for printing the content or an EOB. + + + + + A note that describes or explains adjudication results in a human readable form. + + + + + The term of the benefits documented in this response. + + + + + Balance by Benefit Category. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + Reference to a related claim. + + + + + A code to convey how the claims are related. + + + + + An alternate organizational reference to the case or file to which this particular claim pertains. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + Type of Party to be reimbursed: Subscriber, provider, other. + + + + + Reference to the individual or organization to whom any payment will be made. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + A number to uniquely identify care team entries. + + + + + Member of the team who provided the product or service. + + + + + The party who is billing and/or responsible for the claimed products or services. + + + + + The lead, assisting or supervising practitioner and their discipline if a multidisciplinary team. + + + + + The qualification of the practitioner which is applicable for this service. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + A number to uniquely identify supporting information entries. + + + + + The general class of the information supplied: information; exception; accident, employment; onset, etc. + + + + + System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought. + + + + + The date when or period to which this information refers. + + + + + + + Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. + + + + + + + + + + Provides the reason in the situation where a reason code is required in addition to the content. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + A number to uniquely identify diagnosis entries. + + + + + The nature of illness or problem in a coded form or as a reference to an external defined Condition. + + + + + + + When the condition was observed or the relative ranking. + + + + + Indication of whether the diagnosis was present on admission to a facility. + + + + + A package billing code or bundle code used to group products and services to a particular health condition (such as heart attack) which is based on a predetermined grouping code system. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + A number to uniquely identify procedure entries. + + + + + When the condition was observed or the relative ranking. + + + + + Date and optionally time the procedure was performed. + + + + + The code or reference to a Procedure resource which identifies the clinical intervention performed. + + + + + + + Unique Device Identifiers associated with this line item. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + A flag to indicate that this Coverage is to be used for adjudication of this claim when set to true. + + + + + Reference to the insurance card level information contained in the Coverage resource. The coverage issuing insurer will use these details to locate the patient's actual coverage within the insurer's information system. + + + + + Reference numbers previously provided by the insurer to the provider to be quoted on subsequent claims containing services or products related to the prior authorization. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + Date of an accident event related to the products and services contained in the claim. + + + + + The type or context of the accident event for the purposes of selection of potential insurance coverages and determination of coordination between insurers. + + + + + The physical location of the accident event. + + + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + A number to uniquely identify item entries. + + + + + Care team members related to this service or product. + + + + + Diagnoses applicable for this service or product. + + + + + Procedures applicable for this service or product. + + + + + Exceptions, special conditions and supporting information applicable for this service or product. + + + + + The type of revenue or cost center providing the product and/or service. + + + + + Code to identify the general type of benefits under which products and services are provided. + + + + + When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. + + + + + Item typification or modifiers codes to convey additional context for the product or service. + + + + + Identifies the program under which this may be recovered. + + + + + The date or dates when the service or product was supplied, performed or completed. + + + + + + + Where the product or service was provided. + + + + + + + + The number of repetitions of a service or product. + + + + + If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group. + + + + + A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. + + + + + The quantity times the unit price for an additional service or product or charge. + + + + + Unique Device Identifiers associated with this line item. + + + + + Physical service site on the patient (limb, tooth, etc.). + + + + + A region or surface of the bodySite, e.g. limb region or tooth surface(s). + + + + + A billed item may include goods or services provided in multiple encounters. + + + + + The numbers associated with notes below which apply to the adjudication of this item. + + + + + If this item is a group then the values here are a summary of the adjudication of the detail items. If this item is a simple product or service then this is the result of the adjudication of this item. + + + + + Second-tier of goods and services. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + A code to indicate the information type of this adjudication record. Information types may include: the value submitted, maximum values or percentages allowed or payable under the plan, amounts that the patient is responsible for in-aggregate or pertaining to this item, amounts paid by other coverages, and the benefit payable for this item. + + + + + A code supporting the understanding of the adjudication result and explaining variance from expected amount. + + + + + Monetary amount associated with the category. + + + + + A non-monetary value associated with the category. Mutually exclusive to the amount element above. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + A claim detail line. Either a simple (a product or service) or a 'group' of sub-details which are simple items. + + + + + The type of revenue or cost center providing the product and/or service. + + + + + Code to identify the general type of benefits under which products and services are provided. + + + + + When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. + + + + + Item typification or modifiers codes to convey additional context for the product or service. + + + + + Identifies the program under which this may be recovered. + + + + + The number of repetitions of a service or product. + + + + + If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group. + + + + + A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. + + + + + The quantity times the unit price for an additional service or product or charge. + + + + + Unique Device Identifiers associated with this line item. + + + + + The numbers associated with notes below which apply to the adjudication of this item. + + + + + The adjudication results. + + + + + Third-tier of goods and services. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + A claim detail line. Either a simple (a product or service) or a 'group' of sub-details which are simple items. + + + + + The type of revenue or cost center providing the product and/or service. + + + + + Code to identify the general type of benefits under which products and services are provided. + + + + + When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. + + + + + Item typification or modifiers codes to convey additional context for the product or service. + + + + + Identifies the program under which this may be recovered. + + + + + The number of repetitions of a service or product. + + + + + If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group. + + + + + A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. + + + + + The quantity times the unit price for an additional service or product or charge. + + + + + Unique Device Identifiers associated with this line item. + + + + + The numbers associated with notes below which apply to the adjudication of this item. + + + + + The adjudication results. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + Claim items which this service line is intended to replace. + + + + + The sequence number of the details within the claim item which this line is intended to replace. + + + + + The sequence number of the sub-details woithin the details within the claim item which this line is intended to replace. + + + + + The providers who are authorized for the services rendered to the patient. + + + + + When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. + + + + + Item typification or modifiers codes to convey additional context for the product or service. + + + + + Identifies the program under which this may be recovered. + + + + + The date or dates when the service or product was supplied, performed or completed. + + + + + + + Where the product or service was provided. + + + + + + + + The number of repetitions of a service or product. + + + + + If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group. + + + + + A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. + + + + + The quantity times the unit price for an additional service or product or charge. + + + + + Physical service site on the patient (limb, tooth, etc.). + + + + + A region or surface of the bodySite, e.g. limb region or tooth surface(s). + + + + + The numbers associated with notes below which apply to the adjudication of this item. + + + + + The adjudication results. + + + + + The second-tier service adjudications for payor added services. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. + + + + + Item typification or modifiers codes to convey additional context for the product or service. + + + + + The number of repetitions of a service or product. + + + + + If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group. + + + + + A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. + + + + + The quantity times the unit price for an additional service or product or charge. + + + + + The numbers associated with notes below which apply to the adjudication of this item. + + + + + The adjudication results. + + + + + The third-tier service adjudications for payor added services. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. + + + + + Item typification or modifiers codes to convey additional context for the product or service. + + + + + The number of repetitions of a service or product. + + + + + If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group. + + + + + A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. + + + + + The quantity times the unit price for an additional service or product or charge. + + + + + The numbers associated with notes below which apply to the adjudication of this item. + + + + + The adjudication results. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + A code to indicate the information type of this adjudication record. Information types may include: the value submitted, maximum values or percentages allowed or payable under the plan, amounts that the patient is responsible for in aggregate or pertaining to this item, amounts paid by other coverages, and the benefit payable for this item. + + + + + Monetary total amount associated with the category. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + Whether this represents partial or complete payment of the benefits payable. + + + + + Total amount of all adjustments to this payment included in this transaction which are not related to this claim's adjudication. + + + + + Reason for the payment adjustment. + + + + + Estimated date the payment will be issued or the actual issue date of payment. + + + + + Benefits payable less any payment adjustment. + + + + + Issuer's unique identifier for the payment instrument. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + A number to uniquely identify a note entry. + + + + + The business purpose of the note text. + + + + + The explanation or description associated with the processing. + + + + + A code to define the language used in the text of the note. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + Code to identify the general type of benefits under which products and services are provided. + + + + + True if the indicated class of service is excluded from the plan, missing or False indicates the product or service is included in the coverage. + + + + + A short name or tag for the benefit. + + + + + A richer description of the benefit or services covered. + + + + + Is a flag to indicate whether the benefits refer to in-network providers or out-of-network providers. + + + + + Indicates if the benefits apply to an individual or to the family. + + + + + The term or period of the values such as 'maximum lifetime benefit' or 'maximum annual visits'. + + + + + Benefits Used to date. + + + + + + + + + This resource provides: the claim details; adjudication details from the processing of a Claim; and optionally account balance information, for informing the subscriber of the benefits provided. + + + + + + + Classification of benefit being provided. + + + + + The quantity of the benefit which is permitted under the coverage. + + + + + + + + The quantity of the benefit which have been consumed to date. + + + + + + + + + + + + + Active + + + + + Cancelled + + + + + Draft + + + + + Entered In Error + + + + + + + A code specifying the state of the resource instance. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Significant health conditions for a person related to the patient relevant in the context of care for the patient. + + + + + Significant health conditions for a person related to the patient relevant in the context of care for the patient. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifiers assigned to this family member history by the performer or other systems which remain constant as the resource is updated and propagates from server to server. + + + + + The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this FamilyMemberHistory. + + + + + The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this FamilyMemberHistory. + + + + + A code specifying the status of the record of the family history of a specific family member. + + + + + Describes why the family member's history is not available. + + + + + The person who this history concerns. + + + + + The date (and possibly time) when the family member history was recorded or last updated. + + + + + This will either be a name or a description; e.g. "Aunt Susan", "my cousin with the red hair". + + + + + The type of relationship this person has to the patient (father, mother, brother etc.). + + + + + The birth sex of the family member. + + + + + The actual or approximate date of birth of the relative. + + + + + + + + The age of the relative at the time the family member history is recorded. + + + + + + + + If true, indicates that the age value specified is an estimated value. + + + + + Deceased flag or the actual or approximate age of the relative at the time of death for the family member history record. + + + + + + + + + + Describes why the family member history occurred in coded or textual form. + + + + + Indicates a Condition, Observation, AllergyIntolerance, or QuestionnaireResponse that justifies this family member history event. + + + + + This property allows a non condition-specific note to the made about the related person. Ideally, the note would be in the condition property, but this is not always possible. + + + + + The significant Conditions (or condition) that the family member had. This is a repeating section to allow a system to represent more than one condition per resource, though there is nothing stopping multiple resources - one per condition. + + + + + + + + + Significant health conditions for a person related to the patient relevant in the context of care for the patient. + + + + + + + The actual condition specified. Could be a coded condition (like MI or Diabetes) or a less specific string like 'cancer' depending on how much is known about the condition and the capabilities of the creating system. + + + + + Indicates what happened following the condition. If the condition resulted in death, deceased date is captured on the relation. + + + + + This condition contributed to the cause of death of the related person. If contributedToDeath is not populated, then it is unknown. + + + + + Either the age of onset, range of approximate age or descriptive string can be recorded. For conditions with multiple occurrences, this describes the first known occurrence. + + + + + + + + + An area where general notes can be placed about this specific condition. + + + + + + + + + + + Partial + + + + + Completed + + + + + Entered in Error + + + + + Health Unknown + + + + + + + A code that identifies the status of the family history record. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Prospective warnings of potential issues when providing care to the patient. + + + + + Prospective warnings of potential issues when providing care to the patient. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifiers assigned to this flag by the performer or other systems which remain constant as the resource is updated and propagates from server to server. + + + + + Supports basic workflow. + + + + + Allows a flag to be divided into different categories like clinical, administrative etc. Intended to be used as a means of filtering which flags are displayed to particular user or in a given context. + + + + + The coded value or textual component of the flag to display to the user. + + + + + The patient, location, group, organization, or practitioner etc. this is about record this flag is associated with. + + + + + The period of time from the activation of the flag to inactivation of the flag. If the flag is active, the end of the period should be unspecified. + + + + + This alert is only relevant during the encounter. + + + + + The person, organization or device that created the flag. + + + + + + + + + + + Active + + + + + Inactive + + + + + Entered in Error + + + + + + + Indicates whether this flag is active and needs to be displayed to a user, or whether it is no longer needed or was entered in error. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Describes the intended objective(s) for a patient, group or organization care, for example, weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, etc. + + + + + Describes the intended objective(s) for a patient, group or organization care, for example, weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, etc. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifiers assigned to this goal by the performer or other systems which remain constant as the resource is updated and propagates from server to server. + + + + + The state of the goal throughout its lifecycle. + + + + + Describes the progression, or lack thereof, towards the goal against the target. + + + + + Indicates a category the goal falls within. + + + + + Identifies the mutually agreed level of importance associated with reaching/sustaining the goal. + + + + + Human-readable and/or coded description of a specific desired objective of care, such as "control blood pressure" or "negotiate an obstacle course" or "dance with child at wedding". + + + + + Identifies the patient, group or organization for whom the goal is being established. + + + + + The date or event after which the goal should begin being pursued. + + + + + + + Indicates what should be done by when. + + + + + Identifies when the current status. I.e. When initially created, when achieved, when cancelled, etc. + + + + + Captures the reason for the current status. + + + + + Indicates whose goal this is - patient goal, practitioner goal, etc. + + + + + The identified conditions and other health record elements that are intended to be addressed by the goal. + + + + + Any comments related to the goal. + + + + + Identifies the change (or lack of change) at the point when the status of the goal is assessed. + + + + + Details of what's changed (or not changed). + + + + + + + + + Describes the intended objective(s) for a patient, group or organization care, for example, weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, etc. + + + + + + + The parameter whose value is being tracked, e.g. body weight, blood pressure, or hemoglobin A1c level. + + + + + The target value of the focus to be achieved to signify the fulfillment of the goal, e.g. 150 pounds, 7.0%. Either the high or low or both values of the range can be specified. When a low value is missing, it indicates that the goal is achieved at any focus value at or below the high value. Similarly, if the high value is missing, it indicates that the goal is achieved at any focus value at or above the low value. + + + + + + + + + + + + Indicates either the date or the duration after start by which the goal should be met. + + + + + + + + + + + + + Proposed + + + + + Planned + + + + + Accepted + + + + + Active + + + + + On Hold + + + + + Completed + + + + + Cancelled + + + + + Entered in Error + + + + + Rejected + + + + + + + Codes that reflect the current state of a goal and whether the goal is still being targeted. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A formal computable definition of a graph of resources - that is, a coherent set of resources that form a graph by following references. The Graph Definition resource defines a set and makes rules about the set. + + + + + A formal computable definition of a graph of resources - that is, a coherent set of resources that form a graph by following references. The Graph Definition resource defines a set and makes rules about the set. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this graph definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this graph definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the graph definition is stored on different servers. + + + + + The identifier that is used to identify this version of the graph definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the graph definition 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. + + + + + A natural language name identifying the graph definition. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + The status of this graph definition. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this graph definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The date (and optionally time) when the graph definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the graph definition changes. + + + + + The name of the organization or individual that published the graph definition. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the graph definition from a consumer's perspective. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate graph definition instances. + + + + + A legal or geographic region in which the graph definition is intended to be used. + + + + + Explanation of why this graph definition is needed and why it has been designed as it has. + + + + + The type of FHIR resource at which instances of this graph start. + + + + + The profile that describes the use of the base resource. + + + + + Links this graph makes rules about. + + + + + + + + + A formal computable definition of a graph of resources - that is, a coherent set of resources that form a graph by following references. The Graph Definition resource defines a set and makes rules about the set. + + + + + + + A FHIR expression that identifies one of FHIR References to other resources. + + + + + Which slice (if profiled). + + + + + Minimum occurrences for this link. + + + + + Maximum occurrences for this link. + + + + + Information about why this link is of interest in this graph definition. + + + + + Potential target for the link. + + + + + + + + + A formal computable definition of a graph of resources - that is, a coherent set of resources that form a graph by following references. The Graph Definition resource defines a set and makes rules about the set. + + + + + + + Type of resource this link refers to. + + + + + A set of parameters to look up. + + + + + Profile for the target resource. + + + + + Compartment Consistency Rules. + + + + + Additional links from target resource. + + + + + + + + + A formal computable definition of a graph of resources - that is, a coherent set of resources that form a graph by following references. The Graph Definition resource defines a set and makes rules about the set. + + + + + + + Defines how the compartment rule is used - whether it it is used to test whether resources are subject to the rule, or whether it is a rule that must be followed. + + + + + Identifies the compartment. + + + + + identical | matching | different | no-rule | custom. + + + + + Custom rule, as a FHIRPath expression. + + + + + Documentation for FHIRPath expression. + + + + + + + + + + + Condition + + + + + Requirement + + + + + + + Defines how a compartment rule is used. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Identical + + + + + Matching + + + + + Different + + + + + Custom + + + + + + + How a compartment must be linked. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Represents a defined collection of entities that may be discussed or acted upon collectively but which are not expected to act collectively, and are not formally or legally recognized; i.e. a collection of entities that isn't an Organization. + + + + + Represents a defined collection of entities that may be discussed or acted upon collectively but which are not expected to act collectively, and are not formally or legally recognized; i.e. a collection of entities that isn't an Organization. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A unique business identifier for this group. + + + + + Indicates whether the record for the group is available for use or is merely being retained for historical purposes. + + + + + Identifies the broad classification of the kind of resources the group includes. + + + + + If true, indicates that the resource refers to a specific group of real individuals. If false, the group defines a set of intended individuals. + + + + + Provides a specific type of resource the group includes; e.g. "cow", "syringe", etc. + + + + + A label assigned to the group for human identification and communication. + + + + + A count of the number of resource instances that are part of the group. + + + + + Entity responsible for defining and maintaining Group characteristics and/or registered members. + + + + + Identifies traits whose presence r absence is shared by members of the group. + + + + + Identifies the resource instances that are members of the group. + + + + + + + + + Represents a defined collection of entities that may be discussed or acted upon collectively but which are not expected to act collectively, and are not formally or legally recognized; i.e. a collection of entities that isn't an Organization. + + + + + + + A code that identifies the kind of trait being asserted. + + + + + The value of the trait that holds (or does not hold - see 'exclude') for members of the group. + + + + + + + + + + If true, indicates the characteristic is one that is NOT held by members of the group. + + + + + The period over which the characteristic is tested; e.g. the patient had an operation during the month of June. + + + + + + + + + Represents a defined collection of entities that may be discussed or acted upon collectively but which are not expected to act collectively, and are not formally or legally recognized; i.e. a collection of entities that isn't an Organization. + + + + + + + A reference to the entity that is a member of the group. Must be consistent with Group.type. If the entity is another group, then the type must be the same. + + + + + The period that the member was in the group, if known. + + + + + A flag to indicate that the member is no longer in the group, but previously may have been a member. + + + + + + + + + + + Person + + + + + Animal + + + + + Practitioner + + + + + Device + + + + + Medication + + + + + Substance + + + + + + + Types of resources that are part of group. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A guidance response is the formal response to a guidance request, including any output parameters returned by the evaluation, as well as the description of any proposed actions to be taken. + + + + + A guidance response is the formal response to a guidance request, including any output parameters returned by the evaluation, as well as the description of any proposed actions to be taken. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + The identifier of the request associated with this response. If an identifier was given as part of the request, it will be reproduced here to enable the requester to more easily identify the response in a multi-request scenario. + + + + + Allows a service to provide unique, business identifiers for the response. + + + + + An identifier, CodeableConcept or canonical reference to the guidance that was requested. + + + + + + + + The status of the response. If the evaluation is completed successfully, the status will indicate success. However, in order to complete the evaluation, the engine may require more information. In this case, the status will be data-required, and the response will contain a description of the additional required information. If the evaluation completed successfully, but the engine determines that a potentially more accurate response could be provided if more data was available, the status will be data-requested, and the response will contain a description of the additional requested information. + + + + + The patient for which the request was processed. + + + + + The encounter during which this response was created or to which the creation of this record is tightly associated. + + + + + Indicates when the guidance response was processed. + + + + + Provides a reference to the device that performed the guidance. + + + + + Describes the reason for the guidance response in coded or textual form. + + + + + Indicates the reason the request was initiated. This is typically provided as a parameter to the evaluation and echoed by the service, although for some use cases, such as subscription- or event-based scenarios, it may provide an indication of the cause for the response. + + + + + Provides a mechanism to communicate additional information about the response. + + + + + Messages resulting from the evaluation of the artifact or artifacts. As part of evaluating the request, the engine may produce informational or warning messages. These messages will be provided by this element. + + + + + The output parameters of the evaluation, if any. Many modules will result in the return of specific resources such as procedure or communication requests that are returned as part of the operation result. However, modules may define specific outputs that would be returned as the result of the evaluation, and these would be returned in this element. + + + + + The actions, if any, produced by the evaluation of the artifact. + + + + + If the evaluation could not be completed due to lack of information, or additional information would potentially result in a more accurate response, this element will a description of the data required in order to proceed with the evaluation. A subsequent request to the service should include this data. + + + + + + + + + + + Success + + + + + Data Requested + + + + + Data Required + + + + + In Progress + + + + + Failure + + + + + Entered In Error + + + + + + + The status of a guidance response. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + The details of a healthcare service available at a location. + + + + + The details of a healthcare service available at a location. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + External identifiers for this item. + + + + + This flag is used to mark the record to not be used. This is not used when a center is closed for maintenance, or for holidays, the notAvailable period is to be used for this. + + + + + The organization that provides this healthcare service. + + + + + Identifies the broad category of service being performed or delivered. + + + + + The specific type of service that may be delivered or performed. + + + + + Collection of specialties handled by the service site. This is more of a medical term. + + + + + The location(s) where this healthcare service may be provided. + + + + + Further description of the service as it would be presented to a consumer while searching. + + + + + Any additional description of the service and/or any specific issues not covered by the other attributes, which can be displayed as further detail under the serviceName. + + + + + Extra details about the service that can't be placed in the other fields. + + + + + If there is a photo/symbol associated with this HealthcareService, it may be included here to facilitate quick identification of the service in a list. + + + + + List of contacts related to this specific healthcare service. + + + + + The location(s) that this service is available to (not where the service is provided). + + + + + The code(s) that detail the conditions under which the healthcare service is available/offered. + + + + + Does this service have specific eligibility requirements that need to be met in order to use the service? + + + + + Programs that this service is applicable to. + + + + + Collection of characteristics (attributes). + + + + + Some services are specifically made available in multiple languages, this property permits a directory to declare the languages this is offered in. Typically this is only provided where a service operates in communities with mixed languages used. + + + + + Ways that the service accepts referrals, if this is not provided then it is implied that no referral is required. + + + + + Indicates whether or not a prospective consumer will require an appointment for a particular service at a site to be provided by the Organization. Indicates if an appointment is required for access to this service. + + + + + A collection of times that the Service Site is available. + + + + + The HealthcareService is not available during this period of time due to the provided reason. + + + + + A description of site availability exceptions, e.g. public holiday availability. Succinctly describing all possible exceptions to normal site availability as details in the available Times and not available Times. + + + + + Technical endpoints providing access to services operated for the specific healthcare services defined at this resource. + + + + + + + + + The details of a healthcare service available at a location. + + + + + + + Coded value for the eligibility. + + + + + Describes the eligibility conditions for the service. + + + + + + + + + The details of a healthcare service available at a location. + + + + + + + Indicates which days of the week are available between the start and end Times. + + + + + Is this always available? (hence times are irrelevant) e.g. 24 hour service. + + + + + The opening time of day. Note: If the AllDay flag is set, then this time is ignored. + + + + + The closing time of day. Note: If the AllDay flag is set, then this time is ignored. + + + + + + + + + The details of a healthcare service available at a location. + + + + + + + The reason that can be presented to the user as to why this time is not available. + + + + + Service is not available (seasonally or for a public holiday) from this date. + + + + + + + + + + + Monday + + + + + Tuesday + + + + + Wednesday + + + + + Thursday + + + + + Friday + + + + + Saturday + + + + + Sunday + + + + + + + The days of the week. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Representation of the content produced in a DICOM imaging study. A study comprises a set of series, each of which includes a set of Service-Object Pair Instances (SOP Instances - images or other data) acquired or produced in a common context. A series is of only one modality (e.g. X-ray, CT, MR, ultrasound), but a study may have multiple series of different modalities. + + + + + Representation of the content produced in a DICOM imaging study. A study comprises a set of series, each of which includes a set of Service-Object Pair Instances (SOP Instances - images or other data) acquired or produced in a common context. A series is of only one modality (e.g. X-ray, CT, MR, ultrasound), but a study may have multiple series of different modalities. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifiers for the ImagingStudy such as DICOM Study Instance UID, and Accession Number. + + + + + The current state of the ImagingStudy. + + + + + A list of all the series.modality values that are actual acquisition modalities, i.e. those in the DICOM Context Group 29 (value set OID 1.2.840.10008.6.1.19). + + + + + The subject, typically a patient, of the imaging study. + + + + + The healthcare event (e.g. a patient and healthcare provider interaction) during which this ImagingStudy is made. + + + + + Date and time the study started. + + + + + A list of the diagnostic requests that resulted in this imaging study being performed. + + + + + The requesting/referring physician. + + + + + Who read the study and interpreted the images or other content. + + + + + The network service providing access (e.g., query, view, or retrieval) for the study. See implementation notes for information about using DICOM endpoints. A study-level endpoint applies to each series in the study, unless overridden by a series-level endpoint with the same Endpoint.connectionType. + + + + + Number of Series in the Study. This value given may be larger than the number of series elements this Resource contains due to resource availability, security, or other factors. This element should be present if any series elements are present. + + + + + Number of SOP Instances in Study. This value given may be larger than the number of instance elements this resource contains due to resource availability, security, or other factors. This element should be present if any instance elements are present. + + + + + The procedure which this ImagingStudy was part of. + + + + + The code for the performed procedure type. + + + + + The principal physical location where the ImagingStudy was performed. + + + + + Description of clinical condition indicating why the ImagingStudy was requested. + + + + + Indicates another resource whose existence justifies this Study. + + + + + Per the recommended DICOM mapping, this element is derived from the Study Description attribute (0008,1030). Observations or findings about the imaging study should be recorded in another resource, e.g. Observation, and not in this element. + + + + + The Imaging Manager description of the study. Institution-generated description or classification of the Study (component) performed. + + + + + Each study has one or more series of images or other content. + + + + + + + + + Representation of the content produced in a DICOM imaging study. A study comprises a set of series, each of which includes a set of Service-Object Pair Instances (SOP Instances - images or other data) acquired or produced in a common context. A series is of only one modality (e.g. X-ray, CT, MR, ultrasound), but a study may have multiple series of different modalities. + + + + + + + The DICOM Series Instance UID for the series. + + + + + The numeric identifier of this series in the study. + + + + + The modality of this series sequence. + + + + + A description of the series. + + + + + Number of SOP Instances in the Study. The value given may be larger than the number of instance elements this resource contains due to resource availability, security, or other factors. This element should be present if any instance elements are present. + + + + + The network service providing access (e.g., query, view, or retrieval) for this series. See implementation notes for information about using DICOM endpoints. A series-level endpoint, if present, has precedence over a study-level endpoint with the same Endpoint.connectionType. + + + + + The anatomic structures examined. See DICOM Part 16 Annex L (http://dicom.nema.org/medical/dicom/current/output/chtml/part16/chapter_L.html) for DICOM to SNOMED-CT mappings. The bodySite may indicate the laterality of body part imaged; if so, it shall be consistent with any content of ImagingStudy.series.laterality. + + + + + The laterality of the (possibly paired) anatomic structures examined. E.g., the left knee, both lungs, or unpaired abdomen. If present, shall be consistent with any laterality information indicated in ImagingStudy.series.bodySite. + + + + + The specimen imaged, e.g., for whole slide imaging of a biopsy. + + + + + The date and time the series was started. + + + + + Indicates who or what performed the series and how they were involved. + + + + + A single SOP instance within the series, e.g. an image, or presentation state. + + + + + + + + + Representation of the content produced in a DICOM imaging study. A study comprises a set of series, each of which includes a set of Service-Object Pair Instances (SOP Instances - images or other data) acquired or produced in a common context. A series is of only one modality (e.g. X-ray, CT, MR, ultrasound), but a study may have multiple series of different modalities. + + + + + + + Distinguishes the type of involvement of the performer in the series. + + + + + Indicates who or what performed the series. + + + + + + + + + Representation of the content produced in a DICOM imaging study. A study comprises a set of series, each of which includes a set of Service-Object Pair Instances (SOP Instances - images or other data) acquired or produced in a common context. A series is of only one modality (e.g. X-ray, CT, MR, ultrasound), but a study may have multiple series of different modalities. + + + + + + + The DICOM SOP Instance UID for this image or other DICOM content. + + + + + DICOM instance type. + + + + + The number of instance in the series. + + + + + The description of the instance. + + + + + + + + + + + Registered + + + + + Available + + + + + Cancelled + + + + + Entered in Error + + + + + Unknown + + + + + + + The status of the ImagingStudy. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party. + + + + + Describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A unique identifier assigned to this immunization record. + + + + + Indicates the current status of the immunization event. + + + + + Indicates the reason the immunization event was not performed. + + + + + Vaccine that was administered or was to be administered. + + + + + The patient who either received or did not receive the immunization. + + + + + The visit or admission or other contact between patient and health care provider the immunization was performed as part of. + + + + + Date vaccine administered or was to be administered. + + + + + + + The date the occurrence of the immunization was first captured in the record - potentially significantly after the occurrence of the event. + + + + + An indication that the content of the record is based on information from the person who administered the vaccine. This reflects the context under which the data was originally recorded. + + + + + The source of the data when the report of the immunization event is not based on information from the person who administered the vaccine. + + + + + The service delivery location where the vaccine administration occurred. + + + + + Name of vaccine manufacturer. + + + + + Lot number of the vaccine product. + + + + + Date vaccine batch expires. + + + + + Body site where vaccine was administered. + + + + + The path by which the vaccine product is taken into the body. + + + + + The quantity of vaccine product that was administered. + + + + + Indicates who performed the immunization event. + + + + + Extra information about the immunization that is not conveyed by the other attributes. + + + + + Reasons why the vaccine was administered. + + + + + Condition, Observation or DiagnosticReport that supports why the immunization was administered. + + + + + Indication if a dose is considered to be subpotent. By default, a dose should be considered to be potent. + + + + + Reason why a dose is considered to be subpotent. + + + + + Educational material presented to the patient (or guardian) at the time of vaccine administration. + + + + + Indicates a patient's eligibility for a funding program. + + + + + Indicates the source of the vaccine actually administered. This may be different than the patient eligibility (e.g. the patient may be eligible for a publically purchased vaccine but due to inventory issues, vaccine purchased with private funds was actually administered). + + + + + Categorical data indicating that an adverse event is associated in time to an immunization. + + + + + The protocol (set of recommendations) being followed by the provider who administered the dose. + + + + + + + + + Describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party. + + + + + + + Describes the type of performance (e.g. ordering provider, administering provider, etc.). + + + + + The practitioner or organization who performed the action. + + + + + + + + + Describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party. + + + + + + + Identifier of the material presented to the patient. + + + + + Reference pointer to the educational material given to the patient if the information was on line. + + + + + Date the educational material was published. + + + + + Date the educational material was given to the patient. + + + + + + + + + Describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party. + + + + + + + Date of reaction to the immunization. + + + + + Details of the reaction. + + + + + Self-reported indicator. + + + + + + + + + Describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party. + + + + + + + One possible path to achieve presumed immunity against a disease - within the context of an authority. + + + + + Indicates the authority who published the protocol (e.g. ACIP) that is being followed. + + + + + The vaccine preventable disease the dose is being administered against. + + + + + Nominal position in a series. + + + + + + + The recommended number of doses to achieve immunity. + + + + + + + + + + + + + Completed + + + + + Entered in Error + + + + + Not Done + + + + + + + A set of codes indicating the current status of an Immunization. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Describes a comparison of an immunization event against published recommendations to determine if the administration is "valid" in relation to those recommendations. + + + + + Describes a comparison of an immunization event against published recommendations to determine if the administration is "valid" in relation to those recommendations. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A unique identifier assigned to this immunization evaluation record. + + + + + Indicates the current status of the evaluation of the vaccination administration event. + + + + + The individual for whom the evaluation is being done. + + + + + The date the evaluation of the vaccine administration event was performed. + + + + + Indicates the authority who published the protocol (e.g. ACIP). + + + + + The vaccine preventable disease the dose is being evaluated against. + + + + + The vaccine administration event being evaluated. + + + + + Indicates if the dose is valid or not valid with respect to the published recommendations. + + + + + Provides an explanation as to why the vaccine administration event is valid or not relative to the published recommendations. + + + + + Additional information about the evaluation. + + + + + One possible path to achieve presumed immunity against a disease - within the context of an authority. + + + + + Nominal position in a series. + + + + + + + The recommended number of doses to achieve immunity. + + + + + + + + + + + + + Completed + + + + + Entered in Error + + + + + + + The status of the evaluation being done. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A patient's point-in-time set of recommendations (i.e. forecasting) according to a published schedule with optional supporting justification. + + + + + A patient's point-in-time set of recommendations (i.e. forecasting) according to a published schedule with optional supporting justification. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A unique identifier assigned to this particular recommendation record. + + + + + The patient the recommendation(s) are for. + + + + + The date the immunization recommendation(s) were created. + + + + + Indicates the authority who published the protocol (e.g. ACIP). + + + + + Vaccine administration recommendations. + + + + + + + + + A patient's point-in-time set of recommendations (i.e. forecasting) according to a published schedule with optional supporting justification. + + + + + + + Vaccine(s) or vaccine group that pertain to the recommendation. + + + + + The targeted disease for the recommendation. + + + + + Vaccine(s) which should not be used to fulfill the recommendation. + + + + + Indicates the patient status with respect to the path to immunity for the target disease. + + + + + The reason for the assigned forecast status. + + + + + Vaccine date recommendations. For example, earliest date to administer, latest date to administer, etc. + + + + + Contains the description about the protocol under which the vaccine was administered. + + + + + One possible path to achieve presumed immunity against a disease - within the context of an authority. + + + + + Nominal position of the recommended dose in a series (e.g. dose 2 is the next recommended dose). + + + + + + + The recommended number of doses to achieve immunity. + + + + + + + Immunization event history and/or evaluation that supports the status and recommendation. + + + + + Patient Information that supports the status and recommendation. This includes patient observations, adverse reactions and allergy/intolerance information. + + + + + + + + + A patient's point-in-time set of recommendations (i.e. forecasting) according to a published schedule with optional supporting justification. + + + + + + + Date classification of recommendation. For example, earliest date to give, latest date to give, etc. + + + + + The date whose meaning is specified by dateCriterion.code. + + + + + + + + + A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts. + + + + + A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this implementation guide when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this implementation guide is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the implementation guide is stored on different servers. + + + + + The identifier that is used to identify this version of the implementation guide when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the implementation guide 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. + + + + + A natural language name identifying the implementation guide. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the implementation guide. + + + + + The status of this implementation guide. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this implementation guide is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The date (and optionally time) when the implementation guide was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the implementation guide changes. + + + + + The name of the organization or individual that published the implementation guide. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the implementation guide from a consumer's perspective. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate implementation guide instances. + + + + + A legal or geographic region in which the implementation guide is intended to be used. + + + + + A copyright statement relating to the implementation guide and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the implementation guide. + + + + + The NPM package name for this Implementation Guide, used in the NPM package distribution, which is the primary mechanism by which FHIR based tooling manages IG dependencies. This value must be globally unique, and should be assigned with care. + + + + + The license that applies to this Implementation Guide, using an SPDX license code, or 'not-open-source'. + + + + + The version(s) of the FHIR specification that this ImplementationGuide targets - e.g. describes how to use. The value of this element is the formal version of the specification, without the revision number, e.g. [publication].[major].[minor], which is 4.0.0. for this version. + + + + + Another implementation guide that this implementation depends on. Typically, an implementation guide uses value sets, profiles etc.defined in other implementation guides. + + + + + A set of profiles that all resources covered by this implementation guide must conform to. + + + + + The information needed by an IG publisher tool to publish the whole implementation guide. + + + + + Information about an assembled implementation guide, created by the publication tooling. + + + + + + + + + A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts. + + + + + + + A canonical reference to the Implementation guide for the dependency. + + + + + The NPM package name for the Implementation Guide that this IG depends on. + + + + + The version of the IG that is depended on, when the correct version is required to understand the IG correctly. + + + + + + + + + A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts. + + + + + + + The type of resource that all instances must conform to. + + + + + A reference to the profile that all instances must conform to. + + + + + + + + + A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts. + + + + + + + A logical group of resources. Logical groups can be used when building pages. + + + + + A resource that is part of the implementation guide. Conformance resources (value set, structure definition, capability statements etc.) are obvious candidates for inclusion, but any kind of resource can be included as an example resource. + + + + + A page / section in the implementation guide. The root page is the implementation guide home page. + + + + + Defines how IG is built by tools. + + + + + A template for building resources. + + + + + + + + + A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts. + + + + + + + The human-readable title to display for the package of resources when rendering the implementation guide. + + + + + Human readable text describing the package. + + + + + + + + + A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts. + + + + + + + Where this resource is found. + + + + + Indicates the FHIR Version(s) this artifact is intended to apply to. If no versions are specified, the resource is assumed to apply to all the versions stated in ImplementationGuide.fhirVersion. + + + + + A human assigned name for the resource. All resources SHOULD have a name, but the name may be extracted from the resource (e.g. ValueSet.name). + + + + + A description of the reason that a resource has been included in the implementation guide. + + + + + If true or a reference, indicates the resource is an example instance. If a reference is present, indicates that the example is an example of the specified profile. + + + + + + + Reference to the id of the grouping this resource appears in. + + + + + + + + + A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts. + + + + + + + The source address for the page. + + + + + + + A short title used to represent this page in navigational structures such as table of contents, bread crumbs, etc. + + + + + A code that indicates how the page is generated. + + + + + Nested Pages/Sections under this page. + + + + + + + + + A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts. + + + + + + + apply | path-resource | path-pages | path-tx-cache | expansion-parameter | rule-broken-links | generate-xml | generate-json | generate-turtle | html-template. + + + + + Value for named type. + + + + + + + + + A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts. + + + + + + + Type of template specified. + + + + + The source location for the template. + + + + + The scope in which the template applies. + + + + + + + + + A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts. + + + + + + + A pointer to official web page, PDF or other rendering of the implementation guide. + + + + + A resource that is part of the implementation guide. Conformance resources (value set, structure definition, capability statements etc.) are obvious candidates for inclusion, but any kind of resource can be included as an example resource. + + + + + Information about a page within the IG. + + + + + Indicates a relative path to an image that exists within the IG. + + + + + Indicates the relative path of an additional non-page, non-image file that is part of the IG - e.g. zip, jar and similar files that could be the target of a hyperlink in a derived IG. + + + + + + + + + A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts. + + + + + + + Where this resource is found. + + + + + If true or a reference, indicates the resource is an example instance. If a reference is present, indicates that the example is an example of the specified profile. + + + + + + + The relative path for primary page for this resource within the IG. + + + + + + + + + A set of rules of how a particular interoperability or standards problem is solved - typically through the use of FHIR resources. This resource is used to gather all the parts of an implementation guide into a logical whole and to publish a computable definition of all the parts. + + + + + + + Relative path to the page. + + + + + Label for the page intended for human display. + + + + + The name of an anchor available on the page. + + + + + + + + + + + Apply Metadata Value + + + + + Resource Path + + + + + Pages Path + + + + + Terminology Cache Path + + + + + Expansion Profile + + + + + Broken Links Rule + + + + + Generate XML + + + + + Generate JSON + + + + + Generate Turtle + + + + + HTML Template + + + + + + + Code of parameter that is input to the guide. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Not open source + + + + + BSD Zero Clause License + + + + + Attribution Assurance License + + + + + Abstyles License + + + + + Adobe Systems Incorporated Source Code License Agreement + + + + + Adobe Glyph List License + + + + + Amazon Digital Services License + + + + + Academic Free License v1.1 + + + + + Academic Free License v1.2 + + + + + Academic Free License v2.0 + + + + + Academic Free License v2.1 + + + + + Academic Free License v3.0 + + + + + Afmparse License + + + + + Affero General Public License v1.0 only + + + + + Affero General Public License v1.0 or later + + + + + GNU Affero General Public License v3.0 only + + + + + GNU Affero General Public License v3.0 or later + + + + + Aladdin Free Public License + + + + + AMD's plpa_map.c License + + + + + Apple MIT License + + + + + Academy of Motion Picture Arts and Sciences BSD + + + + + ANTLR Software Rights Notice + + + + + Apache License 1.0 + + + + + Apache License 1.1 + + + + + Apache License 2.0 + + + + + Adobe Postscript AFM License + + + + + Adaptive Public License 1.0 + + + + + Apple Public Source License 1.0 + + + + + Apple Public Source License 1.1 + + + + + Apple Public Source License 1.2 + + + + + Apple Public Source License 2.0 + + + + + Artistic License 1.0 w/clause 8 + + + + + Artistic License 1.0 (Perl) + + + + + Artistic License 1.0 + + + + + Artistic License 2.0 + + + + + Bahyph License + + + + + Barr License + + + + + Beerware License + + + + + BitTorrent Open Source License v1.0 + + + + + BitTorrent Open Source License v1.1 + + + + + Borceux license + + + + + BSD 1-Clause License + + + + + BSD 2-Clause FreeBSD License + + + + + BSD 2-Clause NetBSD License + + + + + BSD-2-Clause Plus Patent License + + + + + BSD 2-Clause "Simplified" License + + + + + BSD with attribution + + + + + BSD 3-Clause Clear License + + + + + Lawrence Berkeley National Labs BSD variant license + + + + + BSD 3-Clause No Nuclear License 2014 + + + + + BSD 3-Clause No Nuclear License + + + + + BSD 3-Clause No Nuclear Warranty + + + + + BSD 3-Clause "New" or "Revised" License + + + + + BSD-4-Clause (University of California-Specific) + + + + + BSD 4-Clause "Original" or "Old" License + + + + + BSD Protection License + + + + + BSD Source Code Attribution + + + + + Boost Software License 1.0 + + + + + bzip2 and libbzip2 License v1.0.5 + + + + + bzip2 and libbzip2 License v1.0.6 + + + + + Caldera License + + + + + Computer Associates Trusted Open Source License 1.1 + + + + + Creative Commons Attribution 1.0 Generic + + + + + Creative Commons Attribution 2.0 Generic + + + + + Creative Commons Attribution 2.5 Generic + + + + + Creative Commons Attribution 3.0 Unported + + + + + Creative Commons Attribution 4.0 International + + + + + Creative Commons Attribution Non Commercial 1.0 Generic + + + + + Creative Commons Attribution Non Commercial 2.0 Generic + + + + + Creative Commons Attribution Non Commercial 2.5 Generic + + + + + Creative Commons Attribution Non Commercial 3.0 Unported + + + + + Creative Commons Attribution Non Commercial 4.0 International + + + + + Creative Commons Attribution Non Commercial No Derivatives 1.0 Generic + + + + + Creative Commons Attribution Non Commercial No Derivatives 2.0 Generic + + + + + Creative Commons Attribution Non Commercial No Derivatives 2.5 Generic + + + + + Creative Commons Attribution Non Commercial No Derivatives 3.0 Unported + + + + + Creative Commons Attribution Non Commercial No Derivatives 4.0 International + + + + + Creative Commons Attribution Non Commercial Share Alike 1.0 Generic + + + + + Creative Commons Attribution Non Commercial Share Alike 2.0 Generic + + + + + Creative Commons Attribution Non Commercial Share Alike 2.5 Generic + + + + + Creative Commons Attribution Non Commercial Share Alike 3.0 Unported + + + + + Creative Commons Attribution Non Commercial Share Alike 4.0 International + + + + + Creative Commons Attribution No Derivatives 1.0 Generic + + + + + Creative Commons Attribution No Derivatives 2.0 Generic + + + + + Creative Commons Attribution No Derivatives 2.5 Generic + + + + + Creative Commons Attribution No Derivatives 3.0 Unported + + + + + Creative Commons Attribution No Derivatives 4.0 International + + + + + Creative Commons Attribution Share Alike 1.0 Generic + + + + + Creative Commons Attribution Share Alike 2.0 Generic + + + + + Creative Commons Attribution Share Alike 2.5 Generic + + + + + Creative Commons Attribution Share Alike 3.0 Unported + + + + + Creative Commons Attribution Share Alike 4.0 International + + + + + Creative Commons Zero v1.0 Universal + + + + + Common Development and Distribution License 1.0 + + + + + Common Development and Distribution License 1.1 + + + + + Community Data License Agreement Permissive 1.0 + + + + + Community Data License Agreement Sharing 1.0 + + + + + CeCILL Free Software License Agreement v1.0 + + + + + CeCILL Free Software License Agreement v1.1 + + + + + CeCILL Free Software License Agreement v2.0 + + + + + CeCILL Free Software License Agreement v2.1 + + + + + CeCILL-B Free Software License Agreement + + + + + CeCILL-C Free Software License Agreement + + + + + Clarified Artistic License + + + + + CNRI Jython License + + + + + CNRI Python Open Source GPL Compatible License Agreement + + + + + CNRI Python License + + + + + Condor Public License v1.1 + + + + + Common Public Attribution License 1.0 + + + + + Common Public License 1.0 + + + + + Code Project Open License 1.02 + + + + + Crossword License + + + + + CrystalStacker License + + + + + CUA Office Public License v1.0 + + + + + Cube License + + + + + curl License + + + + + Deutsche Freie Software Lizenz + + + + + diffmark license + + + + + DOC License + + + + + Dotseqn License + + + + + DSDP License + + + + + dvipdfm License + + + + + Educational Community License v1.0 + + + + + Educational Community License v2.0 + + + + + Eiffel Forum License v1.0 + + + + + Eiffel Forum License v2.0 + + + + + eGenix.com Public License 1.1.0 + + + + + Entessa Public License v1.0 + + + + + Eclipse Public License 1.0 + + + + + Eclipse Public License 2.0 + + + + + Erlang Public License v1.1 + + + + + EU DataGrid Software License + + + + + European Union Public License 1.0 + + + + + European Union Public License 1.1 + + + + + European Union Public License 1.2 + + + + + Eurosym License + + + + + Fair License + + + + + Frameworx Open License 1.0 + + + + + FreeImage Public License v1.0 + + + + + FSF All Permissive License + + + + + FSF Unlimited License + + + + + FSF Unlimited License (with License Retention) + + + + + Freetype Project License + + + + + GNU Free Documentation License v1.1 only + + + + + GNU Free Documentation License v1.1 or later + + + + + GNU Free Documentation License v1.2 only + + + + + GNU Free Documentation License v1.2 or later + + + + + GNU Free Documentation License v1.3 only + + + + + GNU Free Documentation License v1.3 or later + + + + + Giftware License + + + + + GL2PS License + + + + + 3dfx Glide License + + + + + Glulxe License + + + + + gnuplot License + + + + + GNU General Public License v1.0 only + + + + + GNU General Public License v1.0 or later + + + + + GNU General Public License v2.0 only + + + + + GNU General Public License v2.0 or later + + + + + GNU General Public License v3.0 only + + + + + GNU General Public License v3.0 or later + + + + + gSOAP Public License v1.3b + + + + + Haskell Language Report License + + + + + Historical Permission Notice and Disclaimer + + + + + IBM PowerPC Initialization and Boot Software + + + + + ICU License + + + + + Independent JPEG Group License + + + + + ImageMagick License + + + + + iMatix Standard Function Library Agreement + + + + + Imlib2 License + + + + + Info-ZIP License + + + + + Intel ACPI Software License Agreement + + + + + Intel Open Source License + + + + + Interbase Public License v1.0 + + + + + IPA Font License + + + + + IBM Public License v1.0 + + + + + ISC License + + + + + JasPer License + + + + + JSON License + + + + + Licence Art Libre 1.2 + + + + + Licence Art Libre 1.3 + + + + + Latex2e License + + + + + Leptonica License + + + + + GNU Library General Public License v2 only + + + + + GNU Library General Public License v2 or later + + + + + GNU Lesser General Public License v2.1 only + + + + + GNU Lesser General Public License v2.1 or later + + + + + GNU Lesser General Public License v3.0 only + + + + + GNU Lesser General Public License v3.0 or later + + + + + Lesser General Public License For Linguistic Resources + + + + + libpng License + + + + + libtiff License + + + + + Licence Libre du Québec – Permissive version 1.1 + + + + + Licence Libre du Québec – Réciprocité version 1.1 + + + + + Licence Libre du Québec – Réciprocité forte version 1.1 + + + + + Linux Kernel Variant of OpenIB.org license + + + + + Lucent Public License Version 1.0 + + + + + Lucent Public License v1.02 + + + + + LaTeX Project Public License v1.0 + + + + + LaTeX Project Public License v1.1 + + + + + LaTeX Project Public License v1.2 + + + + + LaTeX Project Public License v1.3a + + + + + LaTeX Project Public License v1.3c + + + + + MakeIndex License + + + + + MirOS License + + + + + MIT No Attribution + + + + + Enlightenment License (e16) + + + + + CMU License + + + + + enna License + + + + + feh License + + + + + MIT License + + + + + MIT +no-false-attribs license + + + + + Motosoto License + + + + + mpich2 License + + + + + Mozilla Public License 1.0 + + + + + Mozilla Public License 1.1 + + + + + Mozilla Public License 2.0 (no copyleft exception) + + + + + Mozilla Public License 2.0 + + + + + Microsoft Public License + + + + + Microsoft Reciprocal License + + + + + Matrix Template Library License + + + + + Multics License + + + + + Mup License + + + + + NASA Open Source Agreement 1.3 + + + + + Naumen Public License + + + + + Net Boolean Public License v1 + + + + + University of Illinois/NCSA Open Source License + + + + + Net-SNMP License + + + + + NetCDF license + + + + + Newsletr License + + + + + Nethack General Public License + + + + + Norwegian Licence for Open Government Data + + + + + No Limit Public License + + + + + Nokia Open Source License + + + + + Netizen Open Source License + + + + + Noweb License + + + + + Netscape Public License v1.0 + + + + + Netscape Public License v1.1 + + + + + Non-Profit Open Software License 3.0 + + + + + NRL License + + + + + NTP License + + + + + Open CASCADE Technology Public License + + + + + OCLC Research Public License 2.0 + + + + + ODC Open Database License v1.0 + + + + + SIL Open Font License 1.0 + + + + + SIL Open Font License 1.1 + + + + + Open Group Test Suite License + + + + + Open LDAP Public License v1.1 + + + + + Open LDAP Public License v1.2 + + + + + Open LDAP Public License v1.3 + + + + + Open LDAP Public License v1.4 + + + + + Open LDAP Public License v2.0.1 + + + + + Open LDAP Public License v2.0 (or possibly 2.0A and 2.0B) + + + + + Open LDAP Public License v2.1 + + + + + Open LDAP Public License v2.2.1 + + + + + Open LDAP Public License 2.2.2 + + + + + Open LDAP Public License v2.2 + + + + + Open LDAP Public License v2.3 + + + + + Open LDAP Public License v2.4 + + + + + Open LDAP Public License v2.5 + + + + + Open LDAP Public License v2.6 + + + + + Open LDAP Public License v2.7 + + + + + Open LDAP Public License v2.8 + + + + + Open Market License + + + + + OpenSSL License + + + + + Open Public License v1.0 + + + + + OSET Public License version 2.1 + + + + + Open Software License 1.0 + + + + + Open Software License 1.1 + + + + + Open Software License 2.0 + + + + + Open Software License 2.1 + + + + + Open Software License 3.0 + + + + + ODC Public Domain Dedication & License 1.0 + + + + + PHP License v3.0 + + + + + PHP License v3.01 + + + + + Plexus Classworlds License + + + + + PostgreSQL License + + + + + psfrag License + + + + + psutils License + + + + + Python License 2.0 + + + + + Qhull License + + + + + Q Public License 1.0 + + + + + Rdisc License + + + + + Red Hat eCos Public License v1.1 + + + + + Reciprocal Public License 1.1 + + + + + Reciprocal Public License 1.5 + + + + + RealNetworks Public Source License v1.0 + + + + + RSA Message-Digest License + + + + + Ricoh Source Code Public License + + + + + Ruby License + + + + + Sax Public Domain Notice + + + + + Saxpath License + + + + + SCEA Shared Source License + + + + + Sendmail License + + + + + SGI Free Software License B v1.0 + + + + + SGI Free Software License B v1.1 + + + + + SGI Free Software License B v2.0 + + + + + Simple Public License 2.0 + + + + + Sun Industry Standards Source License v1.2 + + + + + Sun Industry Standards Source License v1.1 + + + + + Sleepycat License + + + + + Standard ML of New Jersey License + + + + + Secure Messaging Protocol Public License + + + + + SNIA Public License 1.1 + + + + + Spencer License 86 + + + + + Spencer License 94 + + + + + Spencer License 99 + + + + + Sun Public License v1.0 + + + + + SugarCRM Public License v1.1.3 + + + + + Scheme Widget Library (SWL) Software License Agreement + + + + + TCL/TK License + + + + + TCP Wrappers License + + + + + TMate Open Source License + + + + + TORQUE v2.5+ Software License v1.1 + + + + + Trusster Open Source License + + + + + Unicode License Agreement - Data Files and Software (2015) + + + + + Unicode License Agreement - Data Files and Software (2016) + + + + + Unicode Terms of Use + + + + + The Unlicense + + + + + Universal Permissive License v1.0 + + + + + Vim License + + + + + VOSTROM Public License for Open Source + + + + + Vovida Software License v1.0 + + + + + W3C Software Notice and License (1998-07-20) + + + + + W3C Software Notice and Document License (2015-05-13) + + + + + W3C Software Notice and License (2002-12-31) + + + + + Sybase Open Watcom Public License 1.0 + + + + + Wsuipa License + + + + + Do What The F*ck You Want To Public License + + + + + X11 License + + + + + Xerox License + + + + + XFree86 License 1.1 + + + + + xinetd License + + + + + X.Net License + + + + + XPP License + + + + + XSkat License + + + + + Yahoo! Public License v1.0 + + + + + Yahoo! Public License v1.1 + + + + + Zed License + + + + + Zend License v2.0 + + + + + Zimbra Public License v1.3 + + + + + Zimbra Public License v1.4 + + + + + zlib/libpng License with Acknowledgement + + + + + zlib License + + + + + Zope Public License 1.1 + + + + + Zope Public License 2.0 + + + + + Zope Public License 2.1 + + + + + + + The license that applies to an Implementation Guide (using an SPDX license Identifiers, or 'not-open-source'). The binding is required but new SPDX license Identifiers are allowed to be used (https://spdx.org/licenses/). + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + HTML + + + + + Markdown + + + + + XML + + + + + Generated + + + + + + + A code that indicates how the page is generated. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Details of a Health Insurance product/plan provided by an organization. + + + + + Details of a Health Insurance product/plan provided by an organization. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifiers assigned to this health insurance product which remain constant as the resource is updated and propagates from server to server. + + + + + The current state of the health insurance product. + + + + + The kind of health insurance product. + + + + + Official name of the health insurance product as designated by the owner. + + + + + A list of alternate names that the product is known as, or was known as in the past. + + + + + The period of time that the health insurance product is available. + + + + + The entity that is providing the health insurance product and underwriting the risk. This is typically an insurance carriers, other third-party payers, or health plan sponsors comonly referred to as 'payers'. + + + + + An organization which administer other services such as underwriting, customer service and/or claims processing on behalf of the health insurance product owner. + + + + + The geographic region in which a health insurance product's benefits apply. + + + + + The contact for the health insurance product for a certain purpose. + + + + + The technical endpoints providing access to services operated for the health insurance product. + + + + + Reference to the network included in the health insurance product. + + + + + Details about the coverage offered by the insurance product. + + + + + Details about an insurance plan. + + + + + + + + + Details of a Health Insurance product/plan provided by an organization. + + + + + + + Indicates a purpose for which the contact can be reached. + + + + + A name associated with the contact. + + + + + A contact detail (e.g. a telephone number or an email address) by which the party may be contacted. + + + + + Visiting or postal addresses for the contact. + + + + + + + + + Details of a Health Insurance product/plan provided by an organization. + + + + + + + Type of coverage (Medical; Dental; Mental Health; Substance Abuse; Vision; Drug; Short Term; Long Term Care; Hospice; Home Health). + + + + + Reference to the network that providing the type of coverage. + + + + + Specific benefits under this type of coverage. + + + + + + + + + Details of a Health Insurance product/plan provided by an organization. + + + + + + + Type of benefit (primary care; speciality care; inpatient; outpatient). + + + + + The referral requirements to have access/coverage for this benefit. + + + + + The specific limits on the benefit. + + + + + + + + + Details of a Health Insurance product/plan provided by an organization. + + + + + + + The maximum amount of a service item a plan will pay for a covered benefit. For examples. wellness visits, or eyeglasses. + + + + + The specific limit on the benefit. + + + + + + + + + Details of a Health Insurance product/plan provided by an organization. + + + + + + + Business identifiers assigned to this health insurance plan which remain constant as the resource is updated and propagates from server to server. + + + + + Type of plan. For example, "Platinum" or "High Deductable". + + + + + The geographic region in which a health insurance plan's benefits apply. + + + + + Reference to the network that providing the type of coverage. + + + + + Overall costs associated with the plan. + + + + + Costs associated with the coverage provided by the product. + + + + + + + + + Details of a Health Insurance product/plan provided by an organization. + + + + + + + Type of cost. + + + + + Number of participants enrolled in the plan. + + + + + Value of the cost. + + + + + Additional information about the general costs associated with this plan. + + + + + + + + + Details of a Health Insurance product/plan provided by an organization. + + + + + + + General category of benefit (Medical; Dental; Vision; Drug; Mental Health; Substance Abuse; Hospice, Home Health). + + + + + List of the specific benefits under this category of benefit. + + + + + + + + + Details of a Health Insurance product/plan provided by an organization. + + + + + + + Type of specific benefit (preventative; primary care office visit; speciality office visit; hospitalization; emergency room; urgent care). + + + + + List of the costs associated with a specific benefit. + + + + + + + + + Details of a Health Insurance product/plan provided by an organization. + + + + + + + Type of cost (copay; individual cap; family cap; coinsurance; deductible). + + + + + Whether the cost applies to in-network or out-of-network providers (in-network; out-of-network; other). + + + + + Additional information about the cost, such as information about funding sources (e.g. HSA, HRA, FSA, RRA). + + + + + The actual cost value. (some of the costs may be represented as percentages rather than currency, e.g. 10% coinsurance). + + + + + + + + + Invoice containing collected ChargeItems from an Account with calculated individual and total price for Billing purpose. + + + + + Invoice containing collected ChargeItems from an Account with calculated individual and total price for Billing purpose. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifier of this Invoice, often used for reference in correspondence about this invoice or for tracking of payments. + + + + + The current state of the Invoice. + + + + + In case of Invoice cancellation a reason must be given (entered in error, superseded by corrected invoice etc.). + + + + + Type of Invoice depending on domain, realm an usage (e.g. internal/external, dental, preliminary). + + + + + The individual or set of individuals receiving the goods and services billed in this invoice. + + + + + The individual or Organization responsible for balancing of this invoice. + + + + + Date/time(s) of when this Invoice was posted. + + + + + Indicates who or what performed or participated in the charged service. + + + + + The organizationissuing the Invoice. + + + + + Account which is supposed to be balanced with this Invoice. + + + + + Each line item represents one charge for goods and services rendered. Details such as date, code and amount are found in the referenced ChargeItem resource. + + + + + The total amount for the Invoice may be calculated as the sum of the line items with surcharges/deductions that apply in certain conditions. The priceComponent element can be used to offer transparency to the recipient of the Invoice of how the total price was calculated. + + + + + Invoice total , taxes excluded. + + + + + Invoice total, tax included. + + + + + Payment details such as banking details, period of payment, deductibles, methods of payment. + + + + + Comments made about the invoice by the issuer, subject, or other participants. + + + + + + + + + Invoice containing collected ChargeItems from an Account with calculated individual and total price for Billing purpose. + + + + + + + Describes the type of involvement (e.g. transcriptionist, creator etc.). If the invoice has been created automatically, the Participant may be a billing engine or another kind of device. + + + + + The device, practitioner, etc. who performed or participated in the service. + + + + + + + + + Invoice containing collected ChargeItems from an Account with calculated individual and total price for Billing purpose. + + + + + + + Sequence in which the items appear on the invoice. + + + + + The ChargeItem contains information such as the billing code, date, amount etc. If no further details are required for the lineItem, inline billing codes can be added using the CodeableConcept data type instead of the Reference. + + + + + + + The price for a ChargeItem may be calculated as a base price with surcharges/deductions that apply in certain conditions. A ChargeItemDefinition resource that defines the prices, factors and conditions that apply to a billing code is currently under development. The priceComponent element can be used to offer transparency to the recipient of the Invoice as to how the prices have been calculated. + + + + + + + + + Invoice containing collected ChargeItems from an Account with calculated individual and total price for Billing purpose. + + + + + + + This code identifies the type of the component. + + + + + A code that identifies the component. Codes may be used to differentiate between kinds of taxes, surcharges, discounts etc. + + + + + The factor that has been applied on the base price for calculating this component. + + + + + The amount calculated for this component. + + + + + + + + + + + draft + + + + + issued + + + + + balanced + + + + + cancelled + + + + + entered in error + + + + + + + Codes identifying the lifecycle stage of an Invoice. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + The Library resource is a general-purpose container for knowledge asset definitions. It can be used to describe and expose existing knowledge assets such as logic libraries and information model descriptions, as well as to describe a collection of knowledge assets. + + + + + The Library resource is a general-purpose container for knowledge asset definitions. It can be used to describe and expose existing knowledge assets such as logic libraries and information model descriptions, as well as to describe a collection of knowledge assets. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this library when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this library is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the library is stored on different servers. + + + + + A formal identifier that is used to identify this library when it is represented in other formats, or referenced in a specification, model, design or an instance. e.g. CMS or NQF identifiers for a measure artifact. Note that at least one identifier is required for non-experimental active artifacts. + + + + + The identifier that is used to identify this version of the library when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the library 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. To provide a version consistent with the Decision Support Service specification, use the format Major.Minor.Revision (e.g. 1.0.0). For more information on versioning knowledge assets, refer to the Decision Support Service specification. Note that a version is required for non-experimental active artifacts. + + + + + A natural language name identifying the library. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the library. + + + + + An explanatory or alternate title for the library giving additional information about its content. + + + + + The status of this library. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this library is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + Identifies the type of library such as a Logic Library, Model Definition, Asset Collection, or Module Definition. + + + + + A code or group definition that describes the intended subject of the contents of the library. + + + + + + + The date (and optionally time) when the library was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the library changes. + + + + + The name of the organization or individual that published the library. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the library from a consumer's perspective. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate library instances. + + + + + A legal or geographic region in which the library is intended to be used. + + + + + Explanation of why this library is needed and why it has been designed as it has. + + + + + A detailed description of how the library is used from a clinical perspective. + + + + + A copyright statement relating to the library and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the library. + + + + + The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. + + + + + The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. + + + + + The period during which the library content was or is planned to be in active use. + + + + + Descriptive topics related to the content of the library. Topics provide a high-level categorization of the library that can be useful for filtering and searching. + + + + + An individiual or organization primarily involved in the creation and maintenance of the content. + + + + + An individual or organization primarily responsible for internal coherence of the content. + + + + + An individual or organization primarily responsible for review of some aspect of the content. + + + + + An individual or organization responsible for officially endorsing the content for use in some setting. + + + + + Related artifacts such as additional documentation, justification, or bibliographic references. + + + + + The parameter element defines parameters used by the library. + + + + + Describes a set of data that must be provided in order to be able to successfully perform the computations defined by the library. + + + + + The content of the library as an Attachment. The content may be a reference to a url, or may be directly embedded as a base-64 string. Either way, the contentType of the attachment determines how to interpret the content. + + + + + + + + + Identifies two or more records (resource instances) that refer to the same real-world "occurrence". + + + + + Identifies two or more records (resource instances) that refer to the same real-world "occurrence". + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Indicates whether the asserted set of linkages are considered to be "in effect". + + + + + Identifies the user or organization responsible for asserting the linkages as well as the user or organization who establishes the context in which the nature of each linkage is evaluated. + + + + + Identifies which record considered as the reference to the same real-world occurrence as well as how the items should be evaluated within the collection of linked items. + + + + + + + + + Identifies two or more records (resource instances) that refer to the same real-world "occurrence". + + + + + + + Distinguishes which item is "source of truth" (if any) and which items are no longer considered to be current representations. + + + + + The resource instance being linked as part of the group. + + + + + + + + + + + Source of Truth + + + + + Alternate Record + + + + + Historical/Obsolete Record + + + + + + + Used to distinguish different roles a resource can play within a set of linked resources. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A list is a curated collection of resources. + + + + + A list is a curated collection of resources. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifier for the List assigned for business purposes outside the context of FHIR. + + + + + Indicates the current state of this list. + + + + + How this list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. + + + + + A label for the list assigned by the author. + + + + + This code defines the purpose of the list - why it was created. + + + + + The common subject (or patient) of the resources that are in the list if there is one. + + + + + The encounter that is the context in which this list was created. + + + + + The date that the list was prepared. + + + + + The entity responsible for deciding what the contents of the list were. Where the list was created by a human, this is the same as the author of the list. + + + + + What order applies to the items in the list. + + + + + Comments that apply to the overall list. + + + + + Entries in this list. + + + + + If the list is empty, why the list is empty. + + + + + + + + + A list is a curated collection of resources. + + + + + + + The flag allows the system constructing the list to indicate the role and significance of the item in the list. + + + + + True if this item is marked as deleted in the list. + + + + + When this item was added to the list. + + + + + A reference to the actual resource from which data was derived. + + + + + + + + + + + Current + + + + + Retired + + + + + Entered In Error + + + + + + + The current state of the list. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated. + + + + + Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Unique code or number identifying the location to its users. + + + + + The status property covers the general availability of the resource, not the current value which may be covered by the operationStatus, or by a schedule/slots if they are configured for the location. + + + + + The operational status covers operation values most relevant to beds (but can also apply to rooms/units/chairs/etc. such as an isolation unit/dialysis chair). This typically covers concepts such as contamination, housekeeping, and other activities like maintenance. + + + + + Name of the location as used by humans. Does not need to be unique. + + + + + A list of alternate names that the location is known as, or was known as, in the past. + + + + + Description of the Location, which helps in finding or referencing the place. + + + + + Indicates whether a resource instance represents a specific location or a class of locations. + + + + + Indicates the type of function performed at the location. + + + + + The contact details of communication devices available at the location. This can include phone numbers, fax numbers, mobile numbers, email addresses and web sites. + + + + + Physical location. + + + + + Physical form of the location, e.g. building, room, vehicle, road. + + + + + The absolute geographic location of the Location, expressed using the WGS84 datum (This is the same co-ordinate system used in KML). + + + + + The organization responsible for the provisioning and upkeep of the location. + + + + + Another Location of which this Location is physically a part of. + + + + + What days/times during a week is this location usually open. + + + + + A description of when the locations opening ours are different to normal, e.g. public holiday availability. Succinctly describing all possible exceptions to normal site availability as detailed in the opening hours Times. + + + + + Technical endpoints providing access to services operated for the location. + + + + + + + + + Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated. + + + + + + + Longitude. The value domain and the interpretation are the same as for the text of the longitude element in KML (see notes below). + + + + + Latitude. The value domain and the interpretation are the same as for the text of the latitude element in KML (see notes below). + + + + + Altitude. The value domain and the interpretation are the same as for the text of the altitude element in KML (see notes below). + + + + + + + + + Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated. + + + + + + + Indicates which days of the week are available between the start and end Times. + + + + + The Location is open all day. + + + + + Time that the Location opens. + + + + + Time that the Location closes. + + + + + + + + + + + Instance + + + + + Kind + + + + + + + Indicates whether a resource instance represents a specific location or a class of locations. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Active + + + + + Suspended + + + + + Inactive + + + + + + + Indicates whether the location is still in use. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + The Measure resource provides the definition of a quality measure. + + + + + The Measure resource provides the definition of a quality measure. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this measure when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this measure is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the measure is stored on different servers. + + + + + A formal identifier that is used to identify this measure when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the measure when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the measure 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. To provide a version consistent with the Decision Support Service specification, use the format Major.Minor.Revision (e.g. 1.0.0). For more information on versioning knowledge assets, refer to the Decision Support Service specification. Note that a version is required for non-experimental active artifacts. + + + + + A natural language name identifying the measure. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the measure. + + + + + An explanatory or alternate title for the measure giving additional information about its content. + + + + + The status of this measure. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this measure is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The intended subjects for the measure. If this element is not provided, a Patient subject is assumed, but the subject of the measure can be anything. + + + + + + + The date (and optionally time) when the measure was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the measure changes. + + + + + The name of the organization or individual that published the measure. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the measure from a consumer's perspective. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate measure instances. + + + + + A legal or geographic region in which the measure is intended to be used. + + + + + Explanation of why this measure is needed and why it has been designed as it has. + + + + + A detailed description, from a clinical perspective, of how the measure is used. + + + + + A copyright statement relating to the measure and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the measure. + + + + + The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. + + + + + The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. + + + + + The period during which the measure content was or is planned to be in active use. + + + + + Descriptive topics related to the content of the measure. Topics provide a high-level categorization grouping types of measures that can be useful for filtering and searching. + + + + + An individiual or organization primarily involved in the creation and maintenance of the content. + + + + + An individual or organization primarily responsible for internal coherence of the content. + + + + + An individual or organization primarily responsible for review of some aspect of the content. + + + + + An individual or organization responsible for officially endorsing the content for use in some setting. + + + + + Related artifacts such as additional documentation, justification, or bibliographic references. + + + + + A reference to a Library resource containing the formal logic used by the measure. + + + + + Notices and disclaimers regarding the use of the measure or related to intellectual property (such as code systems) referenced by the measure. + + + + + Indicates how the calculation is performed for the measure, including proportion, ratio, continuous-variable, and cohort. The value set is extensible, allowing additional measure scoring types to be represented. + + + + + If this is a composite measure, the scoring method used to combine the component measures to determine the composite score. + + + + + Indicates whether the measure is used to examine a process, an outcome over time, a patient-reported outcome, or a structure measure such as utilization. + + + + + A description of the risk adjustment factors that may impact the resulting score for the measure and how they may be accounted for when computing and reporting measure results. + + + + + Describes how to combine the information calculated, based on logic in each of several populations, into one summarized result. + + + + + Provides a succinct statement of the need for the measure. Usually includes statements pertaining to importance criterion: impact, gap in care, and evidence. + + + + + Provides a summary of relevant clinical guidelines or other clinical recommendations supporting the measure. + + + + + Information on whether an increase or decrease in score is the preferred result (e.g., a higher score indicates better quality OR a lower score indicates better quality OR quality is within a range). + + + + + Provides a description of an individual term used within the measure. + + + + + Additional guidance for the measure including how it can be used in a clinical context, and the intent of the measure. + + + + + A group of population criteria for the measure. + + + + + The supplemental data criteria for the measure report, specified as either the name of a valid CQL expression within a referenced library, or a valid FHIR Resource Path. + + + + + + + + + The Measure resource provides the definition of a quality measure. + + + + + + + Indicates a meaning for the group. This can be as simple as a unique identifier, or it can establish meaning in a broader context by drawing from a terminology, allowing groups to be correlated across measures. + + + + + The human readable description of this population group. + + + + + A population criteria for the measure. + + + + + The stratifier criteria for the measure report, specified as either the name of a valid CQL expression defined within a referenced library or a valid FHIR Resource Path. + + + + + + + + + The Measure resource provides the definition of a quality measure. + + + + + + + The type of population criteria. + + + + + The human readable description of this population criteria. + + + + + An expression that specifies the criteria for the population, typically the name of an expression in a library. + + + + + + + + + The Measure resource provides the definition of a quality measure. + + + + + + + Indicates a meaning for the stratifier. This can be as simple as a unique identifier, or it can establish meaning in a broader context by drawing from a terminology, allowing stratifiers to be correlated across measures. + + + + + The human readable description of this stratifier criteria. + + + + + An expression that specifies the criteria for the stratifier. This is typically the name of an expression defined within a referenced library, but it may also be a path to a stratifier element. + + + + + A component of the stratifier criteria for the measure report, specified as either the name of a valid CQL expression defined within a referenced library or a valid FHIR Resource Path. + + + + + + + + + The Measure resource provides the definition of a quality measure. + + + + + + + Indicates a meaning for the stratifier component. This can be as simple as a unique identifier, or it can establish meaning in a broader context by drawing from a terminology, allowing stratifiers to be correlated across measures. + + + + + The human readable description of this stratifier criteria component. + + + + + An expression that specifies the criteria for this component of the stratifier. This is typically the name of an expression defined within a referenced library, but it may also be a path to a stratifier element. + + + + + + + + + The Measure resource provides the definition of a quality measure. + + + + + + + Indicates a meaning for the supplemental data. This can be as simple as a unique identifier, or it can establish meaning in a broader context by drawing from a terminology, allowing supplemental data to be correlated across measures. + + + + + An indicator of the intended usage for the supplemental data element. Supplemental data indicates the data is additional information requested to augment the measure information. Risk adjustment factor indicates the data is additional information used to calculate risk adjustment factors when applying a risk model to the measure calculation. + + + + + The human readable description of this supplemental data. + + + + + The criteria for the supplemental data. This is typically the name of a valid expression defined within a referenced library, but it may also be a path to a specific data element. The criteria defines the data to be returned for this element. + + + + + + + + + The MeasureReport resource contains the results of the calculation of a measure; and optionally a reference to the resources involved in that calculation. + + + + + The MeasureReport resource contains the results of the calculation of a measure; and optionally a reference to the resources involved in that calculation. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A formal identifier that is used to identify this MeasureReport when it is represented in other formats or referenced in a specification, model, design or an instance. + + + + + The MeasureReport status. No data will be available until the MeasureReport status is complete. + + + + + The type of measure report. This may be an individual report, which provides the score for the measure for an individual member of the population; a subject-listing, which returns the list of members that meet the various criteria in the measure; a summary report, which returns a population count for each of the criteria in the measure; or a data-collection, which enables the MeasureReport to be used to exchange the data-of-interest for a quality measure. + + + + + A reference to the Measure that was calculated to produce this report. + + + + + Optional subject identifying the individual or individuals the report is for. + + + + + The date this measure report was generated. + + + + + The individual, location, or organization that is reporting the data. + + + + + The reporting period for which the report was calculated. + + + + + Whether improvement in the measure is noted by an increase or decrease in the measure score. + + + + + The results of the calculation, one for each population group in the measure. + + + + + A reference to a Bundle containing the Resources that were used in the calculation of this measure. + + + + + + + + + The MeasureReport resource contains the results of the calculation of a measure; and optionally a reference to the resources involved in that calculation. + + + + + + + The meaning of the population group as defined in the measure definition. + + + + + The populations that make up the population group, one for each type of population appropriate for the measure. + + + + + The measure score for this population group, calculated as appropriate for the measure type and scoring method, and based on the contents of the populations defined in the group. + + + + + When a measure includes multiple stratifiers, there will be a stratifier group for each stratifier defined by the measure. + + + + + + + + + The MeasureReport resource contains the results of the calculation of a measure; and optionally a reference to the resources involved in that calculation. + + + + + + + The type of the population. + + + + + The number of members of the population. + + + + + This element refers to a List of subject level MeasureReport resources, one for each subject in this population. + + + + + + + + + The MeasureReport resource contains the results of the calculation of a measure; and optionally a reference to the resources involved in that calculation. + + + + + + + The meaning of this stratifier, as defined in the measure definition. + + + + + This element contains the results for a single stratum within the stratifier. For example, when stratifying on administrative gender, there will be four strata, one for each possible gender value. + + + + + + + + + The MeasureReport resource contains the results of the calculation of a measure; and optionally a reference to the resources involved in that calculation. + + + + + + + The value for this stratum, expressed as a CodeableConcept. When defining stratifiers on complex values, the value must be rendered such that the value for each stratum within the stratifier is unique. + + + + + A stratifier component value. + + + + + The populations that make up the stratum, one for each type of population appropriate to the measure. + + + + + The measure score for this stratum, calculated as appropriate for the measure type and scoring method, and based on only the members of this stratum. + + + + + + + + + The MeasureReport resource contains the results of the calculation of a measure; and optionally a reference to the resources involved in that calculation. + + + + + + + The code for the stratum component value. + + + + + The stratum component value. + + + + + + + + + The MeasureReport resource contains the results of the calculation of a measure; and optionally a reference to the resources involved in that calculation. + + + + + + + The type of the population. + + + + + The number of members of the population in this stratum. + + + + + This element refers to a List of subject level MeasureReport resources, one for each subject in this population in this stratum. + + + + + + + + + + + Complete + + + + + Pending + + + + + Error + + + + + + + The status of the measure report. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Individual + + + + + Subject List + + + + + Summary + + + + + Data Collection + + + + + + + The type of the measure report. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A photo, video, or audio recording acquired or used in healthcare. The actual content may be inline or provided by direct reference. + + + + + A photo, video, or audio recording acquired or used in healthcare. The actual content may be inline or provided by direct reference. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifiers associated with the image - these may include identifiers for the image itself, identifiers for the context of its collection (e.g. series ids) and context ids such as accession numbers or other workflow identifiers. + + + + + A procedure that is fulfilled in whole or in part by the creation of this media. + + + + + A larger event of which this particular event is a component or step. + + + + + The current state of the {{title}}. + + + + + A code that classifies whether the media is an image, video or audio recording or some other media category. + + + + + Details of the type of the media - usually, how it was acquired (what type of device). If images sourced from a DICOM system, are wrapped in a Media resource, then this is the modality. + + + + + The name of the imaging view e.g. Lateral or Antero-posterior (AP). + + + + + Who/What this Media is a record of. + + + + + The encounter that establishes the context for this media. + + + + + The date and time(s) at which the media was collected. + + + + + + + The date and time this version of the media was made available to providers, typically after having been reviewed. + + + + + The person who administered the collection of the image. + + + + + Describes why the event occurred in coded or textual form. + + + + + Indicates the site on the subject's body where the observation was made (i.e. the target site). + + + + + The name of the device / manufacturer of the device that was used to make the recording. + + + + + The device used to collect the media. + + + + + Height of the image in pixels (photo/video). + + + + + Width of the image in pixels (photo/video). + + + + + The number of frames in a photo. This is used with a multi-page fax, or an imaging acquisition context that takes multiple slices in a single image, or an animated gif. If there is more than one frame, this SHALL have a value in order to alert interface software that a multi-frame capable rendering widget is required. + + + + + The duration of the recording in seconds - for audio and video. + + + + + The actual content of the media - inline or by direct reference to the media source file. + + + + + Comments made about the media by the performer, subject or other participants. + + + + + + + + + This resource is primarily used for the identification and definition of a medication for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use. + + + + + This resource is primarily used for the identification and definition of a medication for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifier for this medication. + + + + + A code (or set of codes) that specify this medication, or a textual description if no code is available. Usage note: This could be a standard medication code such as a code from RxNorm, SNOMED CT, IDMP etc. It could also be a national or local formulary code, optionally with translations to other code systems. + + + + + A code to indicate if the medication is in active use. + + + + + Describes the details of the manufacturer of the medication product. This is not intended to represent the distributor of a medication product. + + + + + Describes the form of the item. Powder; tablets; capsule. + + + + + Specific amount of the drug in the packaged product. For example, when specifying a product that has the same strength (For example, Insulin glargine 100 unit per mL solution for injection), this attribute provides additional clarification of the package amount (For example, 3 mL, 10mL, etc.). + + + + + Identifies a particular constituent of interest in the product. + + + + + Information that only applies to packages (not products). + + + + + + + + + This resource is primarily used for the identification and definition of a medication for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use. + + + + + + + The actual ingredient - either a substance (simple ingredient) or another medication of a medication. + + + + + + + Indication of whether this ingredient affects the therapeutic action of the drug. + + + + + Specifies how many (or how much) of the items there are in this Medication. For example, 250 mg per tablet. This is expressed as a ratio where the numerator is 250mg and the denominator is 1 tablet. + + + + + + + + + This resource is primarily used for the identification and definition of a medication for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use. + + + + + + + The assigned lot number of a batch of the specified product. + + + + + When this specific batch of product will expire. + + + + + + + + + + + Active + + + + + Inactive + + + + + Entered in Error + + + + + + + A coded concept defining if the medication is in active use. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Describes the event of a patient consuming or otherwise being administered a medication. This may be as simple as swallowing a tablet or it may be a long running infusion. Related resources tie this event to the authorizing prescription, and the specific encounter between patient and health care practitioner. + + + + + Describes the event of a patient consuming or otherwise being administered a medication. This may be as simple as swallowing a tablet or it may be a long running infusion. Related resources tie this event to the authorizing prescription, and the specific encounter between patient and health care practitioner. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifiers associated with this Medication Administration that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server. + + + + + A protocol, guideline, orderset, or other definition that was adhered to in whole or in part by this event. + + + + + A larger event of which this particular event is a component or step. + + + + + Will generally be set to show that the administration has been completed. For some long running administrations such as infusions, it is possible for an administration to be started but not completed or it may be paused while some other process is under way. + + + + + A code indicating why the administration was not performed. + + + + + Indicates where the medication is expected to be consumed or administered. + + + + + Identifies the medication that was administered. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code that identifies the medication from a known list of medications. + + + + + + + The person or animal or group receiving the medication. + + + + + The visit, admission, or other contact between patient and health care provider during which the medication administration was performed. + + + + + Additional information (for example, patient height and weight) that supports the administration of the medication. + + + + + A specific date/time or interval of time during which the administration took place (or did not take place, when the 'notGiven' attribute is true). For many administrations, such as swallowing a tablet the use of dateTime is more appropriate. + + + + + + + Indicates who or what performed the medication administration and how they were involved. + + + + + A code indicating why the medication was given. + + + + + Condition or observation that supports why the medication was administered. + + + + + The original request, instruction or authority to perform the administration. + + + + + The device used in administering the medication to the patient. For example, a particular infusion pump. + + + + + Extra information about the medication administration that is not conveyed by the other attributes. + + + + + Describes the medication dosage information details e.g. dose, rate, site, route, etc. + + + + + A summary of the events of interest that have occurred, such as when the administration was verified. + + + + + + + + + Describes the event of a patient consuming or otherwise being administered a medication. This may be as simple as swallowing a tablet or it may be a long running infusion. Related resources tie this event to the authorizing prescription, and the specific encounter between patient and health care practitioner. + + + + + + + Distinguishes the type of involvement of the performer in the medication administration. + + + + + Indicates who or what performed the medication administration. + + + + + + + + + Describes the event of a patient consuming or otherwise being administered a medication. This may be as simple as swallowing a tablet or it may be a long running infusion. Related resources tie this event to the authorizing prescription, and the specific encounter between patient and health care practitioner. + + + + + + + Free text dosage can be used for cases where the dosage administered is too complex to code. When coded dosage is present, the free text dosage may still be present for display to humans. The dosage instructions should reflect the dosage of the medication that was administered. + + + + + A coded specification of the anatomic site where the medication first entered the body. For example, "left arm". + + + + + A code specifying the route or physiological path of administration of a therapeutic agent into or onto the patient. For example, topical, intravenous, etc. + + + + + A coded value indicating the method by which the medication is intended to be or was introduced into or on the body. This attribute will most often NOT be populated. It is most commonly used for injections. For example, Slow Push, Deep IV. + + + + + The amount of the medication given at one administration event. Use this value when the administration is essentially an instantaneous event such as a swallowing a tablet or giving an injection. + + + + + Identifies the speed with which the medication was or will be introduced into the patient. Typically, the rate for an infusion e.g. 100 ml per 1 hour or 100 ml/hr. May also be expressed as a rate per unit of time, e.g. 500 ml per 2 hours. Other examples: 200 mcg/min or 200 mcg/1 minute; 1 liter/8 hours. + + + + + + + + + + + Indicates that a medication product is to be or has been dispensed for a named person/patient. This includes a description of the medication product (supply) provided and the instructions for administering the medication. The medication dispense is the result of a pharmacy system responding to a medication order. + + + + + Indicates that a medication product is to be or has been dispensed for a named person/patient. This includes a description of the medication product (supply) provided and the instructions for administering the medication. The medication dispense is the result of a pharmacy system responding to a medication order. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifiers associated with this Medication Dispense that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server. + + + + + The procedure that trigger the dispense. + + + + + A code specifying the state of the set of dispense events. + + + + + Indicates the reason why a dispense was not performed. + + + + + + + Indicates the type of medication dispense (for example, where the medication is expected to be consumed or administered (i.e. inpatient or outpatient)). + + + + + Identifies the medication being administered. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code that identifies the medication from a known list of medications. + + + + + + + A link to a resource representing the person or the group to whom the medication will be given. + + + + + The encounter or episode of care that establishes the context for this event. + + + + + Additional information that supports the medication being dispensed. + + + + + Indicates who or what performed the event. + + + + + The principal physical location where the dispense was performed. + + + + + Indicates the medication order that is being dispensed against. + + + + + Indicates the type of dispensing event that is performed. For example, Trial Fill, Completion of Trial, Partial Fill, Emergency Fill, Samples, etc. + + + + + The amount of medication that has been dispensed. Includes unit of measure. + + + + + The amount of medication expressed as a timing amount. + + + + + The time when the dispensed product was packaged and reviewed. + + + + + The time the dispensed product was provided to the patient or their representative. + + + + + Identification of the facility/location where the medication was shipped to, as part of the dispense event. + + + + + Identifies the person who picked up the medication. This will usually be a patient or their caregiver, but some cases exist where it can be a healthcare professional. + + + + + Extra information about the dispense that could not be conveyed in the other attributes. + + + + + Indicates how the medication is to be used by the patient. + + + + + Indicates whether or not substitution was made as part of the dispense. In some cases, substitution will be expected but does not happen, in other cases substitution is not expected but does happen. This block explains what substitution did or did not happen and why. If nothing is specified, substitution was not done. + + + + + Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. drug-drug interaction, duplicate therapy, dosage alert etc. + + + + + A summary of the events of interest that have occurred, such as when the dispense was verified. + + + + + + + + + Indicates that a medication product is to be or has been dispensed for a named person/patient. This includes a description of the medication product (supply) provided and the instructions for administering the medication. The medication dispense is the result of a pharmacy system responding to a medication order. + + + + + + + Distinguishes the type of performer in the dispense. For example, date enterer, packager, final checker. + + + + + The device, practitioner, etc. who performed the action. It should be assumed that the actor is the dispenser of the medication. + + + + + + + + + Indicates that a medication product is to be or has been dispensed for a named person/patient. This includes a description of the medication product (supply) provided and the instructions for administering the medication. The medication dispense is the result of a pharmacy system responding to a medication order. + + + + + + + True if the dispenser dispensed a different drug or product from what was prescribed. + + + + + A code signifying whether a different drug was dispensed from what was prescribed. + + + + + Indicates the reason for the substitution (or lack of substitution) from what was prescribed. + + + + + The person or organization that has primary responsibility for the substitution. + + + + + + + + + Information about a medication that is used to support knowledge. + + + + + Information about a medication that is used to support knowledge. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A code that specifies this medication, or a textual description if no code is available. Usage note: This could be a standard medication code such as a code from RxNorm, SNOMED CT, IDMP etc. It could also be a national or local formulary code, optionally with translations to other code systems. + + + + + A code to indicate if the medication is in active use. The status refers to the validity about the information of the medication and not to its medicinal properties. + + + + + Describes the details of the manufacturer of the medication product. This is not intended to represent the distributor of a medication product. + + + + + Describes the form of the item. Powder; tablets; capsule. + + + + + Specific amount of the drug in the packaged product. For example, when specifying a product that has the same strength (For example, Insulin glargine 100 unit per mL solution for injection), this attribute provides additional clarification of the package amount (For example, 3 mL, 10mL, etc.). + + + + + Additional names for a medication, for example, the name(s) given to a medication in different countries. For example, acetaminophen and paracetamol or salbutamol and albuterol. + + + + + Associated or related knowledge about a medication. + + + + + Associated or related medications. For example, if the medication is a branded product (e.g. Crestor), this is the Therapeutic Moeity (e.g. Rosuvastatin) or if this is a generic medication (e.g. Rosuvastatin), this would link to a branded product (e.g. Crestor). + + + + + Category of the medication or product (e.g. branded product, therapeutic moeity, generic product, innovator product, etc.). + + + + + Associated documentation about the medication. + + + + + Identifies a particular constituent of interest in the product. + + + + + The instructions for preparing the medication. + + + + + The intended or approved route of administration. + + + + + The price of the medication. + + + + + The program under which the medication is reviewed. + + + + + Guidelines for the administration of the medication. + + + + + Categorization of the medication within a formulary or classification system. + + + + + Information that only applies to packages (not products). + + + + + Specifies descriptive properties of the medicine, such as color, shape, imprints, etc. + + + + + Potential clinical issue with or between medication(s) (for example, drug-drug interaction, drug-disease contraindication, drug-allergy interaction, etc.). + + + + + Regulatory information about a medication. + + + + + The time course of drug absorption, distribution, metabolism and excretion of a medication from the body. + + + + + + + + + Information about a medication that is used to support knowledge. + + + + + + + The category of the associated medication knowledge reference. + + + + + Associated documentation about the associated medication knowledge. + + + + + + + + + Information about a medication that is used to support knowledge. + + + + + + + The category of documentation about the medication. (e.g. professional monograph, patient education monograph). + + + + + Associated documentation about the medication. + + + + + + + + + Information about a medication that is used to support knowledge. + + + + + + + The actual ingredient - either a substance (simple ingredient) or another medication. + + + + + + + Indication of whether this ingredient affects the therapeutic action of the drug. + + + + + Specifies how many (or how much) of the items there are in this Medication. For example, 250 mg per tablet. This is expressed as a ratio where the numerator is 250mg and the denominator is 1 tablet. + + + + + + + + + Information about a medication that is used to support knowledge. + + + + + + + The category of the cost information. For example, manufacturers' cost, patient cost, claim reimbursement cost, actual acquisition cost. + + + + + The source or owner that assigns the price to the medication. + + + + + The price of the medication. + + + + + + + + + Information about a medication that is used to support knowledge. + + + + + + + Type of program under which the medication is monitored. + + + + + Name of the reviewing program. + + + + + + + + + Information about a medication that is used to support knowledge. + + + + + + + Dosage for the medication for the specific guidelines. + + + + + Indication for use that apply to the specific administration guidelines. + + + + + + + Characteristics of the patient that are relevant to the administration guidelines (for example, height, weight, gender, etc.). + + + + + + + + + Information about a medication that is used to support knowledge. + + + + + + + The type of dosage (for example, prophylaxis, maintenance, therapeutic, etc.). + + + + + Dosage for the medication for the specific guidelines. + + + + + + + + + Information about a medication that is used to support knowledge. + + + + + + + Specific characteristic that is relevant to the administration guideline (e.g. height, weight, gender). + + + + + + + The specific characteristic (e.g. height, weight, gender, etc.). + + + + + + + + + Information about a medication that is used to support knowledge. + + + + + + + The type of category for the medication (for example, therapeutic classification, therapeutic sub-classification). + + + + + Specific category assigned to the medication (e.g. anti-infective, anti-hypertensive, antibiotic, etc.). + + + + + + + + + Information about a medication that is used to support knowledge. + + + + + + + A code that defines the specific type of packaging that the medication can be found in (e.g. blister sleeve, tube, bottle). + + + + + The number of product units the package would contain if fully loaded. + + + + + + + + + Information about a medication that is used to support knowledge. + + + + + + + A code specifying which characteristic of the medicine is being described (for example, colour, shape, imprint). + + + + + Description of the characteristic. + + + + + + + + + + + + + Information about a medication that is used to support knowledge. + + + + + + + The authority that is specifying the regulations. + + + + + Specifies if changes are allowed when dispensing a medication from a regulatory perspective. + + + + + Specifies the schedule of a medication in jurisdiction. + + + + + The maximum number of units of the medication that can be dispensed in a period. + + + + + + + + + Information about a medication that is used to support knowledge. + + + + + + + Specifies the type of substitution allowed. + + + + + Specifies if regulation allows for changes in the medication when dispensing. + + + + + + + + + Information about a medication that is used to support knowledge. + + + + + + + Specifies the specific drug schedule. + + + + + + + + + Information about a medication that is used to support knowledge. + + + + + + + The maximum number of units of the medication that can be dispensed. + + + + + The period that applies to the maximum number of units. + + + + + + + + + Information about a medication that is used to support knowledge. + + + + + + + The drug concentration measured at certain discrete points in time. + + + + + The median lethal dose of a drug. + + + + + The time required for any specified property (e.g., the concentration of a substance in the body) to decrease by half. + + + + + + + + + An order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns. + + + + + An order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifiers associated with this medication request that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server. + + + + + A code specifying the current state of the order. Generally, this will be active or completed state. + + + + + Captures the reason for the current state of the MedicationRequest. + + + + + Whether the request is a proposal, plan, or an original order. + + + + + Indicates the type of medication request (for example, where the medication is expected to be consumed or administered (i.e. inpatient or outpatient)). + + + + + Indicates how quickly the Medication Request should be addressed with respect to other requests. + + + + + If true indicates that the provider is asking for the medication request not to occur. + + + + + Indicates if this record was captured as a secondary 'reported' record rather than as an original primary source-of-truth record. It may also indicate the source of the report. + + + + + + + Identifies the medication being requested. This is a link to a resource that represents the medication which may be the details of the medication or simply an attribute carrying a code that identifies the medication from a known list of medications. + + + + + + + A link to a resource representing the person or set of individuals to whom the medication will be given. + + + + + The Encounter during which this [x] was created or to which the creation of this record is tightly associated. + + + + + Include additional information (for example, patient height and weight) that supports the ordering of the medication. + + + + + The date (and perhaps time) when the prescription was initially written or authored on. + + + + + The individual, organization, or device that initiated the request and has responsibility for its activation. + + + + + The specified desired performer of the medication treatment (e.g. the performer of the medication administration). + + + + + Indicates the type of performer of the administration of the medication. + + + + + The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order. + + + + + The reason or the indication for ordering or not ordering the medication. + + + + + Condition or observation that supports why the medication was ordered. + + + + + The URL pointing to a protocol, guideline, orderset, or other definition that is adhered to in whole or in part by this MedicationRequest. + + + + + The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this MedicationRequest. + + + + + A plan or request that is fulfilled in whole or in part by this medication request. + + + + + A shared identifier common to all requests that were authorized more or less simultaneously by a single author, representing the identifier of the requisition or prescription. + + + + + The description of the overall patte3rn of the administration of the medication to the patient. + + + + + Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service. + + + + + Extra information about the prescription that could not be conveyed by the other attributes. + + + + + Indicates how the medication is to be used by the patient. + + + + + Indicates the specific details for the dispense or medication supply part of a medication request (also known as a Medication Prescription or Medication Order). Note that this information is not always sent with the order. There may be in some settings (e.g. hospitals) institutional or system support for completing the dispense details in the pharmacy department. + + + + + Indicates whether or not substitution can or should be part of the dispense. In some cases, substitution must happen, in other cases substitution must not happen. This block explains the prescriber's intent. If nothing is specified substitution may be done. + + + + + A link to a resource representing an earlier order related order or prescription. + + + + + Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, duplicate therapy, dosage alert etc. + + + + + Links to Provenance records for past versions of this resource or fulfilling request or event resources that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the resource. + + + + + + + + + An order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns. + + + + + + + Indicates the quantity or duration for the first dispense of the medication. + + + + + The minimum period of time that must occur between dispenses of the medication. + + + + + This indicates the validity period of a prescription (stale dating the Prescription). + + + + + An integer indicating the number of times, in addition to the original dispense, (aka refills or repeats) that the patient can receive the prescribed medication. Usage Notes: This integer does not include the original order dispense. This means that if an order indicates dispense 30 tablets plus "3 repeats", then the order can be dispensed a total of 4 times and the patient can receive a total of 120 tablets. A prescriber may explicitly say that zero refills are permitted after the initial dispense. + + + + + The amount that is to be dispensed for one fill. + + + + + Identifies the period time over which the supplied product is expected to be used, or the length of time the dispense is expected to last. + + + + + Indicates the intended dispensing Organization specified by the prescriber. + + + + + + + + + An order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns. + + + + + + + The amount or quantity to provide as part of the first dispense. + + + + + The length of time that the first dispense is expected to last. + + + + + + + + + An order or request for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings, including care plans, etc., and to harmonize with workflow patterns. + + + + + + + True if the prescriber allows a different drug to be dispensed from what was prescribed. + + + + + + + Indicates the reason for the substitution, or why substitution must or must not be performed. + + + + + + + + + + + Active + + + + + On Hold + + + + + Cancelled + + + + + Completed + + + + + Entered in Error + + + + + Stopped + + + + + Draft + + + + + Unknown + + + + + + + A coded concept specifying the state of the prescribing event. Describes the lifecycle of the prescription. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Proposal + + + + + Plan + + + + + Order + + + + + Original Order + + + + + Reflex Order + + + + + Filler Order + + + + + Instance Order + + + + + Option + + + + + + + The kind of medication order. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A record of a medication that is being consumed by a patient. A MedicationStatement may indicate that the patient may be taking the medication now or has taken the medication in the past or will be taking the medication in the future. The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay. The medication information may come from sources such as the patient's memory, from a prescription bottle, or from a list of medications the patient, clinician or other party maintains. + +The primary difference between a medication statement and a medication administration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication. A medication statement is often, if not always, less specific. There is no required date/time when the medication was administered, in fact we only know that a source has reported the patient is taking this medication, where details such as time, quantity, or rate or even medication product may be incomplete or missing or less precise. As stated earlier, the medication statement information may come from the patient's memory, from a prescription bottle or from a list of medications the patient, clinician or other party maintains. Medication administration is more formal and is not missing detailed information. + + + + + A record of a medication that is being consumed by a patient. A MedicationStatement may indicate that the patient may be taking the medication now or has taken the medication in the past or will be taking the medication in the future. The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay. The medication information may come from sources such as the patient's memory, from a prescription bottle, or from a list of medications the patient, clinician or other party maintains. + +The primary difference between a medication statement and a medication administration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication. A medication statement is often, if not always, less specific. There is no required date/time when the medication was administered, in fact we only know that a source has reported the patient is taking this medication, where details such as time, quantity, or rate or even medication product may be incomplete or missing or less precise. As stated earlier, the medication statement information may come from the patient's memory, from a prescription bottle or from a list of medications the patient, clinician or other party maintains. Medication administration is more formal and is not missing detailed information. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifiers associated with this Medication Statement that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server. + + + + + A plan, proposal or order that is fulfilled in whole or in part by this event. + + + + + A larger event of which this particular event is a component or step. + + + + + A code representing the patient or other source's judgment about the state of the medication used that this statement is about. Generally, this will be active or completed. + + + + + Captures the reason for the current state of the MedicationStatement. + + + + + Indicates where the medication is expected to be consumed or administered. + + + + + Identifies the medication being administered. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code that identifies the medication from a known list of medications. + + + + + + + The person, animal or group who is/was taking the medication. + + + + + The encounter or episode of care that establishes the context for this MedicationStatement. + + + + + The interval of time during which it is being asserted that the patient is/was/will be taking the medication (or was not taking, when the MedicationStatement.taken element is No). + + + + + + + The date when the medication statement was asserted by the information source. + + + + + The person or organization that provided the information about the taking of this medication. Note: Use derivedFrom when a MedicationStatement is derived from other resources, e.g. Claim or MedicationRequest. + + + + + Allows linking the MedicationStatement to the underlying MedicationRequest, or to other information that supports or is used to derive the MedicationStatement. + + + + + A reason for why the medication is being/was taken. + + + + + Condition or observation that supports why the medication is being/was taken. + + + + + Provides extra information about the medication statement that is not conveyed by the other attributes. + + + + + Indicates how the medication is/was or should be taken by the patient. + + + + + + + + + Detailed definition of a medicinal product, typically for uses other than direct patient care (e.g. regulatory use). + + + + + Detailed definition of a medicinal product, typically for uses other than direct patient care (e.g. regulatory use). + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifier for this product. Could be an MPID. + + + + + Regulatory type, e.g. Investigational or Authorized. + + + + + If this medicine applies to human or veterinary uses. + + + + + The dose form for a single part product, or combined form of a multiple part product. + + + + + General combined description of indication(s) for this product. See also MedicinalProductIndication. + + + + + The legal status of supply of the medicinal product as classified by the regulator. + + + + + Whether the Medicinal Product is subject to additional monitoring for regulatory reasons. + + + + + Whether the Medicinal Product is subject to special measures for regulatory reasons. + + + + + If authorised for use in children. + + + + + Allows the product to be classified by various systems. + + + + + Marketing status of the medicinal product, in contrast to marketing authorizaton. + + + + + Pharmaceutical aspects of product. + + + + + Package representation for the product. + + + + + Supporting documentation, typically for regulatory submission. + + + + + A master file for to the medicinal product (e.g. Pharmacovigilance System Master File). + + + + + A product specific contact, person (in a role), or an organization. + + + + + Clinical trials or studies that this product is involved in. + + + + + The product's name, including full name and possibly coded parts. + + + + + Reference to another product, e.g. for linking authorised to investigational product. + + + + + An operation applied to the product, for manufacturing or adminsitrative purpose. + + + + + Indicates if the medicinal product has an orphan designation for the treatment of a rare disease. + + + + + + + + + Detailed definition of a medicinal product, typically for uses other than direct patient care (e.g. regulatory use). + + + + + + + Allows the contact to be classified, for example QPPV, Pharmacovigilence Enquiry Information. + + + + + A product specific contact, person (in a role), or an organization. + + + + + + + + + Detailed definition of a medicinal product, typically for uses other than direct patient care (e.g. regulatory use). + + + + + + + The full product name. + + + + + Coding words or phrases of the name. + + + + + Country where the name applies. + + + + + + + + + Detailed definition of a medicinal product, typically for uses other than direct patient care (e.g. regulatory use). + + + + + + + A fragment of a product name. + + + + + Idenifying type for this part of the name (e.g. strength part). + + + + + + + + + Detailed definition of a medicinal product, typically for uses other than direct patient care (e.g. regulatory use). + + + + + + + Country code for where this name applies. + + + + + Jurisdiction code for where this name applies. + + + + + Language code for this name. + + + + + + + + + Detailed definition of a medicinal product, typically for uses other than direct patient care (e.g. regulatory use). + + + + + + + The type of manufacturing operation. + + + + + Regulatory authorization reference number. + + + + + Regulatory authorization date. + + + + + To indicate if this proces is commercially confidential. + + + + + The manufacturer or establishment associated with the process. + + + + + A regulator which oversees the operation. + + + + + + + + + Detailed definition of a medicinal product, typically for uses other than direct patient care (e.g. regulatory use). + + + + + + + Identifier for the designation, or procedure number. + + + + + The type of special designation, e.g. orphan drug, minor use. + + + + + The intended use of the product, e.g. prevention, treatment. + + + + + Condition for which the medicinal use applies. + + + + + + + For example granted, pending, expired or withdrawn. + + + + + Date when the designation was granted. + + + + + Animal species for which this applies. + + + + + + + + + The regulatory authorization of a medicinal product. + + + + + The regulatory authorization of a medicinal product. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifier for the marketing authorization, as assigned by a regulator. + + + + + The medicinal product that is being authorized. + + + + + The country in which the marketing authorization has been granted. + + + + + Jurisdiction within a country. + + + + + The status of the marketing authorization. + + + + + The date at which the given status has become applicable. + + + + + The date when a suspended the marketing or the marketing authorization of the product is anticipated to be restored. + + + + + The beginning of the time period in which the marketing authorization is in the specific status shall be specified A complete date consisting of day, month and year shall be specified using the ISO 8601 date format. + + + + + A period of time after authorization before generic product applicatiosn can be submitted. + + + + + The date when the first authorization was granted by a Medicines Regulatory Agency. + + + + + Date of first marketing authorization for a company's new medicinal product in any country in the World. + + + + + The legal framework against which this authorization is granted. + + + + + Authorization in areas within a country. + + + + + Marketing Authorization Holder. + + + + + Medicines Regulatory Agency. + + + + + The regulatory procedure for granting or amending a marketing authorization. + + + + + + + + + The regulatory authorization of a medicinal product. + + + + + + + The assigned number for the marketing authorization. + + + + + Country of authorization. + + + + + Jurisdiction within a country. + + + + + The legal status of supply in a jurisdiction or region. + + + + + The start and expected end date of the authorization. + + + + + + + + + The regulatory authorization of a medicinal product. + + + + + + + Identifier for this procedure. + + + + + Type of procedure. + + + + + Date of procedure. + + + + + + + Applcations submitted to obtain a marketing authorization. + + + + + + + + + The clinical particulars - indications, contraindications etc. of a medicinal product, including for regulatory purposes. + + + + + The clinical particulars - indications, contraindications etc. of a medicinal product, including for regulatory purposes. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + The medication for which this is an indication. + + + + + The disease, symptom or procedure for the contraindication. + + + + + The status of the disease or symptom for the contraindication. + + + + + A comorbidity (concurrent condition) or coinfection. + + + + + Information about the use of the medicinal product in relation to other therapies as part of the indication. + + + + + Information about the use of the medicinal product in relation to other therapies described as part of the indication. + + + + + The population group to which this applies. + + + + + + + + + The clinical particulars - indications, contraindications etc. of a medicinal product, including for regulatory purposes. + + + + + + + The type of relationship between the medicinal product indication or contraindication and another therapy. + + + + + Reference to a specific medication (active substance, medicinal product or class of products) as part of an indication or contraindication. + + + + + + + + + + + Indication for the Medicinal Product. + + + + + Indication for the Medicinal Product. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + The medication for which this is an indication. + + + + + The disease, symptom or procedure that is the indication for treatment. + + + + + The status of the disease or symptom for which the indication applies. + + + + + Comorbidity (concurrent condition) or co-infection as part of the indication. + + + + + The intended effect, aim or strategy to be achieved by the indication. + + + + + Timing or duration information as part of the indication. + + + + + Information about the use of the medicinal product in relation to other therapies described as part of the indication. + + + + + Describe the undesirable effects of the medicinal product. + + + + + The population group to which this applies. + + + + + + + + + Indication for the Medicinal Product. + + + + + + + The type of relationship between the medicinal product indication or contraindication and another therapy. + + + + + Reference to a specific medication (active substance, medicinal product or class of products) as part of an indication or contraindication. + + + + + + + + + + + An ingredient of a manufactured item or pharmaceutical product. + + + + + An ingredient of a manufactured item or pharmaceutical product. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + The identifier(s) of this Ingredient that are assigned by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. + + + + + Ingredient role e.g. Active ingredient, excipient. + + + + + If the ingredient is a known or suspected allergen. + + + + + Manufacturer of this Ingredient. + + + + + A specified substance that comprises this ingredient. + + + + + The ingredient substance. + + + + + + + + + An ingredient of a manufactured item or pharmaceutical product. + + + + + + + The specified substance. + + + + + The group of specified substance, e.g. group 1 to 4. + + + + + Confidentiality level of the specified substance as the ingredient. + + + + + Quantity of the substance or specified substance present in the manufactured item or pharmaceutical product. + + + + + + + + + An ingredient of a manufactured item or pharmaceutical product. + + + + + + + The quantity of substance in the unit of presentation, or in the volume (or mass) of the single pharmaceutical product or manufactured item. + + + + + A lower limit for the quantity of substance in the unit of presentation. For use when there is a range of strengths, this is the lower limit, with the presentation attribute becoming the upper limit. + + + + + The strength per unitary volume (or mass). + + + + + A lower limit for the strength per unitary volume (or mass), for when there is a range. The concentration attribute then becomes the upper limit. + + + + + For when strength is measured at a particular point or distance. + + + + + The country or countries for which the strength range applies. + + + + + Strength expressed in terms of a reference substance. + + + + + + + + + An ingredient of a manufactured item or pharmaceutical product. + + + + + + + Relevant reference substance. + + + + + Strength expressed in terms of a reference substance. + + + + + Strength expressed in terms of a reference substance. + + + + + For when strength is measured at a particular point or distance. + + + + + The country or countries for which the strength range applies. + + + + + + + + + An ingredient of a manufactured item or pharmaceutical product. + + + + + + + The ingredient substance. + + + + + Quantity of the substance or specified substance present in the manufactured item or pharmaceutical product. + + + + + + + + + The interactions of the medicinal product with other medicinal products, or other forms of interactions. + + + + + The interactions of the medicinal product with other medicinal products, or other forms of interactions. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + The medication for which this is a described interaction. + + + + + The interaction described. + + + + + The specific medication, food or laboratory test that interacts. + + + + + The type of the interaction e.g. drug-drug interaction, drug-food interaction, drug-lab test interaction. + + + + + The effect of the interaction, for example "reduced gastric absorption of primary medication". + + + + + The incidence of the interaction, e.g. theoretical, observed. + + + + + Actions for managing the interaction. + + + + + + + + + The interactions of the medicinal product with other medicinal products, or other forms of interactions. + + + + + + + The specific medication, food or laboratory test that interacts. + + + + + + + + + + + The manufactured item as contained in the packaged medicinal product. + + + + + The manufactured item as contained in the packaged medicinal product. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Dose form as manufactured and before any transformation into the pharmaceutical product. + + + + + The “real world” units in which the quantity of the manufactured item is described. + + + + + The quantity or "count number" of the manufactured item. + + + + + Manufacturer of the item (Note that this should be named "manufacturer" but it currently causes technical issues). + + + + + Ingredient. + + + + + Dimensions, color etc. + + + + + Other codeable characteristics. + + + + + + + + + A medicinal product in a container or package. + + + + + A medicinal product in a container or package. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Unique identifier. + + + + + The product that this is a pack for. + + + + + Textual description. + + + + + The legal status of supply of the medicinal product as classified by the regulator. + + + + + Marketing information. + + + + + Manufacturer of this Package Item. + + + + + Manufacturer of this Package Item. + + + + + Batch numbering. + + + + + A packaging item, as a contained for medicine, possibly with other packaging items within. + + + + + + + + + A medicinal product in a container or package. + + + + + + + A number appearing on the outer packaging of a specific batch. + + + + + A number appearing on the immediate packaging (and not the outer packaging). + + + + + + + + + A medicinal product in a container or package. + + + + + + + Including possibly Data Carrier Identifier. + + + + + The physical type of the container of the medicine. + + + + + The quantity of this package in the medicinal product, at the current level of packaging. The outermost is always 1. + + + + + Material type of the package item. + + + + + A possible alternate material for the packaging. + + + + + A device accompanying a medicinal product. + + + + + The manufactured item as contained in the packaged medicinal product. + + + + + Allows containers within containers. + + + + + Dimensions, color etc. + + + + + Other codeable characteristics. + + + + + Shelf Life and storage information. + + + + + Manufacturer of this Package Item. + + + + + + + + + A pharmaceutical product described in terms of its composition and dose form. + + + + + A pharmaceutical product described in terms of its composition and dose form. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An identifier for the pharmaceutical medicinal product. + + + + + The product that this is a pharmaceutical product of. + + + + + The administrable dose form, after necessary reconstitution. + + + + + Todo. + + + + + Ingredient. + + + + + Accompanying device. + + + + + Characteristics e.g. a products onset of action. + + + + + The path by which the pharmaceutical product is taken into or makes contact with the body. + + + + + + + + + A pharmaceutical product described in terms of its composition and dose form. + + + + + + + A coded characteristic. + + + + + The status of characteristic e.g. assigned or pending. + + + + + + + + + A pharmaceutical product described in terms of its composition and dose form. + + + + + + + Coded expression for the route. + + + + + The first dose (dose quantity) administered in humans can be specified, for a product under investigation, using a numerical value and its unit of measurement. + + + + + The maximum single dose that can be administered as per the protocol of a clinical trial can be specified using a numerical value and its unit of measurement. + + + + + The maximum dose per day (maximum dose quantity to be administered in any one 24-h period) that can be administered as per the protocol referenced in the clinical trial authorisation. + + + + + The maximum dose per treatment period that can be administered as per the protocol referenced in the clinical trial authorisation. + + + + + The maximum treatment period during which an Investigational Medicinal Product can be administered as per the protocol referenced in the clinical trial authorisation. + + + + + A species for which this route applies. + + + + + + + + + A pharmaceutical product described in terms of its composition and dose form. + + + + + + + Coded expression for the species. + + + + + A species specific time during which consumption of animal product is not appropriate. + + + + + + + + + A pharmaceutical product described in terms of its composition and dose form. + + + + + + + Coded expression for the type of tissue for which the withdrawal period applues, e.g. meat, milk. + + + + + A value for the time. + + + + + Extra information about the withdrawal period. + + + + + + + + + Describe the undesirable effects of the medicinal product. + + + + + Describe the undesirable effects of the medicinal product. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + The medication for which this is an indication. + + + + + The symptom, condition or undesirable effect. + + + + + Classification of the effect. + + + + + The frequency of occurrence of the effect. + + + + + The population group to which this applies. + + + + + + + + + Defines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted. + + + + + Defines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + The business identifier that is used to reference the MessageDefinition and *is* expected to be consistent from server to server. + + + + + A formal identifier that is used to identify this message definition when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the message definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the message definition 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. + + + + + A natural language name identifying the message definition. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the message definition. + + + + + A MessageDefinition that is superseded by this definition. + + + + + The status of this message definition. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this message definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The date (and optionally time) when the message definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the message definition changes. + + + + + The name of the organization or individual that published the message definition. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the message definition from a consumer's perspective. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate message definition instances. + + + + + A legal or geographic region in which the message definition is intended to be used. + + + + + Explanation of why this message definition is needed and why it has been designed as it has. + + + + + A copyright statement relating to the message definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the message definition. + + + + + The MessageDefinition that is the basis for the contents of this resource. + + + + + Identifies a protocol or workflow that this MessageDefinition represents a step in. + + + + + Event code or link to the EventDefinition. + + + + + + + The impact of the content of the message. + + + + + Identifies the resource (or resources) that are being addressed by the event. For example, the Encounter for an admit message or two Account records for a merge. + + + + + Declare at a message definition level whether a response is required or only upon error or success, or never. + + + + + Indicates what types of messages may be sent as an application-level response to this message. + + + + + Canonical reference to a GraphDefinition. If a URL is provided, it is the canonical reference to a [[[GraphDefinition]]] that it controls what resources are to be added to the bundle when building the document. The GraphDefinition can also specify profiles that apply to the various resources. + + + + + + + + + Defines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted. + + + + + + + The kind of resource that must be the focus for this message. + + + + + A profile that reflects constraints for the focal resource (and potentially for related resources). + + + + + Identifies the minimum number of resources of this type that must be pointed to by a message in order for it to be valid against this MessageDefinition. + + + + + Identifies the maximum number of resources of this type that must be pointed to by a message in order for it to be valid against this MessageDefinition. + + + + + + + + + Defines the characteristics of a message that can be shared between systems, including the type of event that initiates the message, the content to be transmitted and what response(s), if any, are permitted. + + + + + + + A reference to the message definition that must be adhered to by this supported response. + + + + + Provides a description of the circumstances in which this response should be used (as opposed to one of the alternative responses). + + + + + + + + + + + Consequence + + + + + Currency + + + + + Notification + + + + + + + The impact of the content of a message. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Always + + + + + Error/reject conditions only + + + + + Never + + + + + Successful completion only + + + + + + + HL7-defined table of codes which identify conditions under which acknowledgments are required to be returned in response to a message. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + The header for a message exchange that is either requesting or responding to an action. The reference(s) that are the subject of the action as well as other information related to the action are typically transmitted in a bundle in which the MessageHeader resource instance is the first resource in the bundle. + + + + + The header for a message exchange that is either requesting or responding to an action. The reference(s) that are the subject of the action as well as other information related to the action are typically transmitted in a bundle in which the MessageHeader resource instance is the first resource in the bundle. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Code that identifies the event this message represents and connects it with its definition. Events defined as part of the FHIR specification have the system value "http://terminology.hl7.org/CodeSystem/message-events". Alternatively uri to the EventDefinition. + + + + + + + The destination application which the message is intended for. + + + + + Identifies the sending system to allow the use of a trust relationship. + + + + + The person or device that performed the data entry leading to this message. When there is more than one candidate, pick the most proximal to the message. Can provide other enterers in extensions. + + + + + The logical author of the message - the person or device that decided the described event should happen. When there is more than one candidate, pick the most proximal to the MessageHeader. Can provide other authors in extensions. + + + + + The source application from which this message originated. + + + + + The person or organization that accepts overall responsibility for the contents of the message. The implication is that the message event happened under the policies of the responsible party. + + + + + Coded indication of the cause for the event - indicates a reason for the occurrence of the event that is a focus of this message. + + + + + Information about the message that this message is a response to. Only present if this message is a response. + + + + + The actual data of the message - a reference to the root/focus class of the event. + + + + + Permanent link to the MessageDefinition for this message. + + + + + + + + + The header for a message exchange that is either requesting or responding to an action. The reference(s) that are the subject of the action as well as other information related to the action are typically transmitted in a bundle in which the MessageHeader resource instance is the first resource in the bundle. + + + + + + + Human-readable name for the target system. + + + + + Identifies the target end system in situations where the initial message transmission is to an intermediary system. + + + + + Indicates where the message should be routed to. + + + + + Allows data conveyed by a message to be addressed to a particular person or department when routing to a specific application isn't sufficient. + + + + + + + + + The header for a message exchange that is either requesting or responding to an action. The reference(s) that are the subject of the action as well as other information related to the action are typically transmitted in a bundle in which the MessageHeader resource instance is the first resource in the bundle. + + + + + + + Human-readable name for the source system. + + + + + May include configuration or other information useful in debugging. + + + + + Can convey versions of multiple systems in situations where a message passes through multiple hands. + + + + + An e-mail, phone, website or other contact point to use to resolve issues with message communications. + + + + + Identifies the routing target to send acknowledgements to. + + + + + + + + + The header for a message exchange that is either requesting or responding to an action. The reference(s) that are the subject of the action as well as other information related to the action are typically transmitted in a bundle in which the MessageHeader resource instance is the first resource in the bundle. + + + + + + + The MessageHeader.id of the message to which this message is a response. + + + + + Code that identifies the type of response to the message - whether it was successful or not, and whether it should be resent or not. + + + + + Full details of any issues found in the message. + + + + + + + + + + + OK + + + + + Transient Error + + + + + Fatal Error + + + + + + + The kind of response to a message. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Raw data describing a biological sequence. + + + + + Raw data describing a biological sequence. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A unique identifier for this particular sequence instance. This is a FHIR-defined id. + + + + + Amino Acid Sequence/ DNA Sequence / RNA Sequence. + + + + + Whether the sequence is numbered starting at 0 (0-based numbering or coordinates, inclusive start, exclusive end) or starting at 1 (1-based numbering, inclusive start and inclusive end). + + + + + The patient whose sequencing results are described by this resource. + + + + + Specimen used for sequencing. + + + + + The method for sequencing, for example, chip information. + + + + + The organization or lab that should be responsible for this result. + + + + + The number of copies of the sequence of interest. (RNASeq). + + + + + A sequence that is used as a reference to describe variants that are present in a sequence analyzed. + + + + + The definition of variant here originates from Sequence ontology ([variant_of](http://www.sequenceontology.org/browser/current_svn/term/variant_of)). This element can represent amino acid or nucleic sequence change(including insertion,deletion,SNP,etc.) It can represent some complex mutation or segment variation with the assist of CIGAR string. + + + + + Sequence that was observed. It is the result marked by referenceSeq along with variant records on referenceSeq. This shall start from referenceSeq.windowStart and end by referenceSeq.windowEnd. + + + + + An experimental feature attribute that defines the quality of the feature in a quantitative way, such as a phred quality score ([SO:0001686](http://www.sequenceontology.org/browser/current_svn/term/SO:0001686)). + + + + + Coverage (read depth or depth) is the average number of reads representing a given nucleotide in the reconstructed sequence. + + + + + Configurations of the external repository. The repository shall store target's observedSeq or records related with target's observedSeq. + + + + + Pointer to next atomic sequence which at most contains one variant. + + + + + Information about chromosome structure variation. + + + + + + + + + Raw data describing a biological sequence. + + + + + + + Structural unit composed of a nucleic acid molecule which controls its own replication through the interaction of specific proteins at one or more origins of replication ([SO:0000340](http://www.sequenceontology.org/browser/current_svn/term/SO:0000340)). + + + + + The Genome Build used for reference, following GRCh build versions e.g. 'GRCh 37'. Version number must be included if a versioned release of a primary build was used. + + + + + A relative reference to a DNA strand based on gene orientation. The strand that contains the open reading frame of the gene is the "sense" strand, and the opposite complementary strand is the "antisense" strand. + + + + + Reference identifier of reference sequence submitted to NCBI. It must match the type in the MolecularSequence.type field. For example, the prefix, “NG_” identifies reference sequence for genes, “NM_” for messenger RNA transcripts, and “NP_” for amino acid sequences. + + + + + A pointer to another MolecularSequence entity as reference sequence. + + + + + A string like "ACGT". + + + + + An absolute reference to a strand. The Watson strand is the strand whose 5'-end is on the short arm of the chromosome, and the Crick strand as the one whose 5'-end is on the long arm. + + + + + Start position of the window on the reference sequence. If the coordinate system is either 0-based or 1-based, then start position is inclusive. + + + + + End position of the window on the reference sequence. If the coordinate system is 0-based then end is exclusive and does not include the last position. If the coordinate system is 1-base, then end is inclusive and includes the last position. + + + + + + + + + Raw data describing a biological sequence. + + + + + + + Start position of the variant on the reference sequence. If the coordinate system is either 0-based or 1-based, then start position is inclusive. + + + + + End position of the variant on the reference sequence. If the coordinate system is 0-based then end is exclusive and does not include the last position. If the coordinate system is 1-base, then end is inclusive and includes the last position. + + + + + An allele is one of a set of coexisting sequence variants of a gene ([SO:0001023](http://www.sequenceontology.org/browser/current_svn/term/SO:0001023)). Nucleotide(s)/amino acids from start position of sequence to stop position of sequence on the positive (+) strand of the observed sequence. When the sequence type is DNA, it should be the sequence on the positive (+) strand. This will lay in the range between variant.start and variant.end. + + + + + An allele is one of a set of coexisting sequence variants of a gene ([SO:0001023](http://www.sequenceontology.org/browser/current_svn/term/SO:0001023)). Nucleotide(s)/amino acids from start position of sequence to stop position of sequence on the positive (+) strand of the reference sequence. When the sequence type is DNA, it should be the sequence on the positive (+) strand. This will lay in the range between variant.start and variant.end. + + + + + Extended CIGAR string for aligning the sequence with reference bases. See detailed documentation [here](http://support.illumina.com/help/SequencingAnalysisWorkflow/Content/Vault/Informatics/Sequencing_Analysis/CASAVA/swSEQ_mCA_ExtendedCIGARFormat.htm). + + + + + A pointer to an Observation containing variant information. + + + + + + + + + Raw data describing a biological sequence. + + + + + + + INDEL / SNP / Undefined variant. + + + + + Gold standard sequence used for comparing against. + + + + + Start position of the sequence. If the coordinate system is either 0-based or 1-based, then start position is inclusive. + + + + + End position of the sequence. If the coordinate system is 0-based then end is exclusive and does not include the last position. If the coordinate system is 1-base, then end is inclusive and includes the last position. + + + + + The score of an experimentally derived feature such as a p-value ([SO:0001685](http://www.sequenceontology.org/browser/current_svn/term/SO:0001685)). + + + + + Which method is used to get sequence quality. + + + + + True positives, from the perspective of the truth data, i.e. the number of sites in the Truth Call Set for which there are paths through the Query Call Set that are consistent with all of the alleles at this site, and for which there is an accurate genotype call for the event. + + + + + True positives, from the perspective of the query data, i.e. the number of sites in the Query Call Set for which there are paths through the Truth Call Set that are consistent with all of the alleles at this site, and for which there is an accurate genotype call for the event. + + + + + False negatives, i.e. the number of sites in the Truth Call Set for which there is no path through the Query Call Set that is consistent with all of the alleles at this site, or sites for which there is an inaccurate genotype call for the event. Sites with correct variant but incorrect genotype are counted here. + + + + + False positives, i.e. the number of sites in the Query Call Set for which there is no path through the Truth Call Set that is consistent with this site. Sites with correct variant but incorrect genotype are counted here. + + + + + The number of false positives where the non-REF alleles in the Truth and Query Call Sets match (i.e. cases where the truth is 1/1 and the query is 0/1 or similar). + + + + + QUERY.TP / (QUERY.TP + QUERY.FP). + + + + + TRUTH.TP / (TRUTH.TP + TRUTH.FN). + + + + + Harmonic mean of Recall and Precision, computed as: 2 * precision * recall / (precision + recall). + + + + + Receiver Operator Characteristic (ROC) Curve to give sensitivity/specificity tradeoff. + + + + + + + + + Raw data describing a biological sequence. + + + + + + + Invidual data point representing the GQ (genotype quality) score threshold. + + + + + The number of true positives if the GQ score threshold was set to "score" field value. + + + + + The number of false positives if the GQ score threshold was set to "score" field value. + + + + + The number of false negatives if the GQ score threshold was set to "score" field value. + + + + + Calculated precision if the GQ score threshold was set to "score" field value. + + + + + Calculated sensitivity if the GQ score threshold was set to "score" field value. + + + + + Calculated fScore if the GQ score threshold was set to "score" field value. + + + + + + + + + Raw data describing a biological sequence. + + + + + + + Click and see / RESTful API / Need login to see / RESTful API with authentication / Other ways to see resource. + + + + + URI of an external repository which contains further details about the genetics data. + + + + + URI of an external repository which contains further details about the genetics data. + + + + + Id of the variant in this external repository. The server will understand how to use this id to call for more info about datasets in external repository. + + + + + Id of the variantset in this external repository. The server will understand how to use this id to call for more info about variantsets in external repository. + + + + + Id of the read in this external repository. + + + + + + + + + Raw data describing a biological sequence. + + + + + + + Information about chromosome structure variation DNA change type. + + + + + Used to indicate if the outer and inner start-end values have the same meaning. + + + + + Length of the variant chromosome. + + + + + Structural variant outer. + + + + + Structural variant inner. + + + + + + + + + Raw data describing a biological sequence. + + + + + + + Structural variant outer start. If the coordinate system is either 0-based or 1-based, then start position is inclusive. + + + + + Structural variant outer end. If the coordinate system is 0-based then end is exclusive and does not include the last position. If the coordinate system is 1-base, then end is inclusive and includes the last position. + + + + + + + + + Raw data describing a biological sequence. + + + + + + + Structural variant inner start. If the coordinate system is either 0-based or 1-based, then start position is inclusive. + + + + + Structural variant inner end. If the coordinate system is 0-based then end is exclusive and does not include the last position. If the coordinate system is 1-base, then end is inclusive and includes the last position. + + + + + + + + + + + Watson strand of referenceSeq + + + + + Crick strand of referenceSeq + + + + + + + Type for strand. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Sense orientation of referenceSeq + + + + + Antisense orientation of referenceSeq + + + + + + + Type for orientation. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Click and see + + + + + The URL is the RESTful or other kind of API that can access to the result. + + + + + Result cannot be access unless an account is logged in + + + + + Result need to be fetched with API and need LOGIN( or cookies are required when visiting the link of resource) + + + + + Some other complicated or particular way to get resource from URL. + + + + + + + Type for access of external URI. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + INDEL Comparison + + + + + SNP Comparison + + + + + UNKNOWN Comparison + + + + + + + Type for quality report. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + AA Sequence + + + + + DNA Sequence + + + + + RNA Sequence + + + + + + + Type if a sequence -- DNA, RNA, or amino acid sequence. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A curated namespace that issues unique symbols within that namespace for the identification of concepts, people, devices, etc. Represents a "System" used within the Identifier and Coding data types. + + + + + A curated namespace that issues unique symbols within that namespace for the identification of concepts, people, devices, etc. Represents a "System" used within the Identifier and Coding data types. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A natural language name identifying the naming system. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + The status of this naming system. Enables tracking the life-cycle of the content. + + + + + Indicates the purpose for the naming system - what kinds of things does it make unique? + + + + + The date (and optionally time) when the naming system was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the naming system changes. + + + + + The name of the organization or individual that published the naming system. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + The name of the organization that is responsible for issuing identifiers or codes for this namespace and ensuring their non-collision. + + + + + Categorizes a naming system for easier search by grouping related naming systems. + + + + + A free text natural language description of the naming system from a consumer's perspective. Details about what the namespace identifies including scope, granularity, version labeling, etc. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate naming system instances. + + + + + A legal or geographic region in which the naming system is intended to be used. + + + + + Provides guidance on the use of the namespace, including the handling of formatting characters, use of upper vs. lower case, etc. + + + + + Indicates how the system may be identified when referenced in electronic exchange. + + + + + + + + + A curated namespace that issues unique symbols within that namespace for the identification of concepts, people, devices, etc. Represents a "System" used within the Identifier and Coding data types. + + + + + + + Identifies the unique identifier scheme used for this particular identifier. + + + + + The string that should be sent over the wire to identify the code system or identifier system. + + + + + Indicates whether this identifier is the "preferred" identifier of this type. + + + + + Notes about the past or intended usage of this identifier. + + + + + Identifies the period of time over which this identifier is considered appropriate to refer to the naming system. Outside of this window, the identifier might be non-deterministic. + + + + + + + + + + + OID + + + + + UUID + + + + + URI + + + + + Other + + + + + + + Identifies the style of unique identifier used to identify a namespace. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Code System + + + + + Identifier + + + + + Root + + + + + + + Identifies the purpose of the naming system. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident. + + + + + A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifiers assigned to this order by the order sender or by the order receiver. + + + + + The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this NutritionOrder. + + + + + The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this NutritionOrder. + + + + + The URL pointing to a protocol, guideline, orderset or other definition that is adhered to in whole or in part by this NutritionOrder. + + + + + The workflow status of the nutrition order/request. + + + + + Indicates the level of authority/intentionality associated with the NutrionOrder and where the request fits into the workflow chain. + + + + + The person (patient) who needs the nutrition order for an oral diet, nutritional supplement and/or enteral or formula feeding. + + + + + An encounter that provides additional information about the healthcare context in which this request is made. + + + + + The date and time that this nutrition order was requested. + + + + + The practitioner that holds legal responsibility for ordering the diet, nutritional supplement, or formula feedings. + + + + + A link to a record of allergies or intolerances which should be included in the nutrition order. + + + + + This modifier is used to convey order-specific modifiers about the type of food that should be given. These can be derived from patient allergies, intolerances, or preferences such as Halal, Vegan or Kosher. This modifier applies to the entire nutrition order inclusive of the oral diet, nutritional supplements and enteral formula feedings. + + + + + This modifier is used to convey Order-specific modifier about the type of oral food or oral fluids that should not be given. These can be derived from patient allergies, intolerances, or preferences such as No Red Meat, No Soy or No Wheat or Gluten-Free. While it should not be necessary to repeat allergy or intolerance information captured in the referenced AllergyIntolerance resource in the excludeFoodModifier, this element may be used to convey additional specificity related to foods that should be eliminated from the patient’s diet for any reason. This modifier applies to the entire nutrition order inclusive of the oral diet, nutritional supplements and enteral formula feedings. + + + + + Diet given orally in contrast to enteral (tube) feeding. + + + + + Oral nutritional products given in order to add further nutritional value to the patient's diet. + + + + + Feeding provided through the gastrointestinal tract via a tube, catheter, or stoma that delivers nutrition distal to the oral cavity. + + + + + Comments made about the {{title}} by the requester, performer, subject or other participants. + + + + + + + + + A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident. + + + + + + + The kind of diet or dietary restriction such as fiber restricted diet or diabetic diet. + + + + + The time period and frequency at which the diet should be given. The diet should be given for the combination of all schedules if more than one schedule is present. + + + + + Class that defines the quantity and type of nutrient modifications (for example carbohydrate, fiber or sodium) required for the oral diet. + + + + + Class that describes any texture modifications required for the patient to safely consume various types of solid foods. + + + + + The required consistency (e.g. honey-thick, nectar-thick, thin, thickened.) of liquids or fluids served to the patient. + + + + + Free text or additional instructions or information pertaining to the oral diet. + + + + + + + + + A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident. + + + + + + + The nutrient that is being modified such as carbohydrate or sodium. + + + + + The quantity of the specified nutrient to include in diet. + + + + + + + + + A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident. + + + + + + + Any texture modifications (for solid foods) that should be made, e.g. easy to chew, chopped, ground, and pureed. + + + + + The food type(s) (e.g. meats, all foods) that the texture modification applies to. This could be all foods types. + + + + + + + + + A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident. + + + + + + + The kind of nutritional supplement product required such as a high protein or pediatric clear liquid supplement. + + + + + The product or brand name of the nutritional supplement such as "Acme Protein Shake". + + + + + The time period and frequency at which the supplement(s) should be given. The supplement should be given for the combination of all schedules if more than one schedule is present. + + + + + The amount of the nutritional supplement to be given. + + + + + Free text or additional instructions or information pertaining to the oral supplement. + + + + + + + + + A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident. + + + + + + + The type of enteral or infant formula such as an adult standard formula with fiber or a soy-based infant formula. + + + + + The product or brand name of the enteral or infant formula product such as "ACME Adult Standard Formula". + + + + + Indicates the type of modular component such as protein, carbohydrate, fat or fiber to be provided in addition to or mixed with the base formula. + + + + + The product or brand name of the type of modular component to be added to the formula. + + + + + The amount of energy (calories) that the formula should provide per specified volume, typically per mL or fluid oz. For example, an infant may require a formula that provides 24 calories per fluid ounce or an adult may require an enteral formula that provides 1.5 calorie/mL. + + + + + The route or physiological path of administration into the patient's gastrointestinal tract for purposes of providing the formula feeding, e.g. nasogastric tube. + + + + + Formula administration instructions as structured data. This repeating structure allows for changing the administration rate or volume over time for both bolus and continuous feeding. An example of this would be an instruction to increase the rate of continuous feeding every 2 hours. + + + + + The maximum total quantity of formula that may be administered to a subject over the period of time, e.g. 1440 mL over 24 hours. + + + + + Free text formula administration, feeding instructions or additional instructions or information. + + + + + + + + + A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident. + + + + + + + The time period and frequency at which the enteral formula should be delivered to the patient. + + + + + The volume of formula to provide to the patient per the specified administration schedule. + + + + + The rate of administration of formula via a feeding pump, e.g. 60 mL per hour, according to the specified schedule. + + + + + + + + + + + Measurements and simple assertions made about a patient, device or other subject. + + + + + Measurements and simple assertions made about a patient, device or other subject. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A unique identifier assigned to this observation. + + + + + A plan, proposal or order that is fulfilled in whole or in part by this event. For example, a MedicationRequest may require a patient to have laboratory test performed before it is dispensed. + + + + + A larger event of which this particular Observation is a component or step. For example, an observation as part of a procedure. + + + + + The status of the result value. + + + + + A code that classifies the general type of observation being made. + + + + + Describes what was observed. Sometimes this is called the observation "name". + + + + + The patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the `focus` element or the `code` itself specifies the actual focus of the observation. + + + + + The actual focus of an observation when it is not the patient of record representing something or someone associated with the patient such as a spouse, parent, fetus, or donor. For example, fetus observations in a mother's record. The focus of an observation could also be an existing condition, an intervention, the subject's diet, another observation of the subject, or a body structure such as tumor or implanted device. An example use case would be using the Observation resource to capture whether the mother is trained to change her child's tracheostomy tube. In this example, the child is the patient of record and the mother is the focus. + + + + + The healthcare event (e.g. a patient and healthcare provider interaction) during which this observation is made. + + + + + The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the "physiologically relevant time". This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself. + + + + + + + + + The date and time this version of the observation was made available to providers, typically after the results have been reviewed and verified. + + + + + Who was responsible for asserting the observed value as "true". + + + + + The information determined as a result of making the observation, if the information has a simple value. + + + + + + + + + + + + + + + + Provides a reason why the expected value in the element Observation.value[x] is missing. + + + + + A categorical assessment of an observation value. For example, high, low, normal. + + + + + Comments about the observation or the results. + + + + + Indicates the site on the subject's body where the observation was made (i.e. the target site). + + + + + Indicates the mechanism used to perform the observation. + + + + + The specimen that was used when this observation was made. + + + + + The device used to generate the observation data. + + + + + Guidance on how to interpret the value by comparison to a normal or recommended range. Multiple reference ranges are interpreted as an "OR". In other words, to represent two distinct target populations, two `referenceRange` elements would be used. + + + + + This observation is a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group. + + + + + The target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image. + + + + + Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes. Examples include systolic and diastolic component observations for blood pressure measurement and multiple component observations for genetics observations. + + + + + + + + + Measurements and simple assertions made about a patient, device or other subject. + + + + + + + The value of the low bound of the reference range. The low bound of the reference range endpoint is inclusive of the value (e.g. reference range is >=5 - <=9). If the low bound is omitted, it is assumed to be meaningless (e.g. reference range is <=2.3). + + + + + The value of the high bound of the reference range. The high bound of the reference range endpoint is inclusive of the value (e.g. reference range is >=5 - <=9). If the high bound is omitted, it is assumed to be meaningless (e.g. reference range is >= 2.3). + + + + + Codes to indicate the what part of the targeted reference population it applies to. For example, the normal or therapeutic range. + + + + + Codes to indicate the target population this reference range applies to. For example, a reference range may be based on the normal population or a particular sex or race. Multiple `appliesTo` are interpreted as an "AND" of the target populations. For example, to represent a target population of African American females, both a code of female and a code for African American would be used. + + + + + The age at which this reference range is applicable. This is a neonatal age (e.g. number of weeks at term) if the meaning says so. + + + + + Text based reference range in an observation which may be used when a quantitative range is not appropriate for an observation. An example would be a reference value of "Negative" or a list or table of "normals". + + + + + + + + + Measurements and simple assertions made about a patient, device or other subject. + + + + + + + Describes what was observed. Sometimes this is called the observation "code". + + + + + The information determined as a result of making the observation, if the information has a simple value. + + + + + + + + + + + + + + + + Provides a reason why the expected value in the element Observation.component.value[x] is missing. + + + + + A categorical assessment of an observation value. For example, high, low, normal. + + + + + Guidance on how to interpret the value by comparison to a normal or recommended range. + + + + + + + + + Set of definitional characteristics for a kind of observation or measurement produced or consumed by an orderable health care service. + + + + + Set of definitional characteristics for a kind of observation or measurement produced or consumed by an orderable health care service. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A code that classifies the general type of observation. + + + + + Describes what will be observed. Sometimes this is called the observation "name". + + + + + A unique identifier assigned to this ObservationDefinition artifact. + + + + + The data types allowed for the value element of the instance observations conforming to this ObservationDefinition. + + + + + Multiple results allowed for observations conforming to this ObservationDefinition. + + + + + The method or technique used to perform the observation. + + + + + The preferred name to be used when reporting the results of observations conforming to this ObservationDefinition. + + + + + Characteristics for quantitative results of this observation. + + + + + Multiple ranges of results qualified by different contexts for ordinal or continuous observations conforming to this ObservationDefinition. + + + + + The set of valid coded results for the observations conforming to this ObservationDefinition. + + + + + The set of normal coded results for the observations conforming to this ObservationDefinition. + + + + + The set of abnormal coded results for the observation conforming to this ObservationDefinition. + + + + + The set of critical coded results for the observation conforming to this ObservationDefinition. + + + + + + + + + Set of definitional characteristics for a kind of observation or measurement produced or consumed by an orderable health care service. + + + + + + + Customary unit used to report quantitative results of observations conforming to this ObservationDefinition. + + + + + SI unit used to report quantitative results of observations conforming to this ObservationDefinition. + + + + + Factor for converting value expressed with SI unit to value expressed with customary unit. + + + + + Number of digits after decimal separator when the results of such observations are of type Quantity. + + + + + + + + + Set of definitional characteristics for a kind of observation or measurement produced or consumed by an orderable health care service. + + + + + + + The category of interval of values for continuous or ordinal observations conforming to this ObservationDefinition. + + + + + The low and high values determining the interval. There may be only one of the two. + + + + + Codes to indicate the health context the range applies to. For example, the normal or therapeutic range. + + + + + Codes to indicate the target population this reference range applies to. + + + + + Sex of the population the range applies to. + + + + + The age at which this reference range is applicable. This is a neonatal age (e.g. number of weeks at term) if the meaning says so. + + + + + The gestational age to which this reference range is applicable, in the context of pregnancy. + + + + + Text based condition for which the reference range is valid. + + + + + + + + + + + Quantity + + + + + CodeableConcept + + + + + string + + + + + boolean + + + + + integer + + + + + Range + + + + + Ratio + + + + + SampledData + + + + + time + + + + + dateTime + + + + + Period + + + + + + + Permitted data type for observation value. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + reference range + + + + + critical range + + + + + absolute range + + + + + + + Codes identifying the category of observation range. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction). + + + + + A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction). + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this operation definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this operation definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the operation definition is stored on different servers. + + + + + The identifier that is used to identify this version of the operation definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the operation definition 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. + + + + + A natural language name identifying the operation definition. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the operation definition. + + + + + The status of this operation definition. Enables tracking the life-cycle of the content. + + + + + Whether this is an operation or a named query. + + + + + A Boolean value to indicate that this operation definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The date (and optionally time) when the operation definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the operation definition changes. + + + + + The name of the organization or individual that published the operation definition. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the operation definition from a consumer's perspective. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate operation definition instances. + + + + + A legal or geographic region in which the operation definition is intended to be used. + + + + + Explanation of why this operation definition is needed and why it has been designed as it has. + + + + + Whether the operation affects state. Side effects such as producing audit trail entries do not count as 'affecting state'. + + + + + The name used to invoke the operation. + + + + + Additional information about how to use this operation or named query. + + + + + Indicates that this operation definition is a constraining profile on the base. + + + + + The types on which this operation can be executed. + + + + + Indicates whether this operation or named query can be invoked at the system level (e.g. without needing to choose a resource type for the context). + + + + + Indicates whether this operation or named query can be invoked at the resource type level for any given resource type level (e.g. without needing to choose a specific resource id for the context). + + + + + Indicates whether this operation can be invoked on a particular instance of one of the given types. + + + + + Additional validation information for the in parameters - a single profile that covers all the parameters. The profile is a constraint on the parameters resource as a whole. + + + + + Additional validation information for the out parameters - a single profile that covers all the parameters. The profile is a constraint on the parameters resource. + + + + + The parameters for the operation/query. + + + + + Defines an appropriate combination of parameters to use when invoking this operation, to help code generators when generating overloaded parameter sets for this operation. + + + + + + + + + A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction). + + + + + + + The name of used to identify the parameter. + + + + + Whether this is an input or an output parameter. + + + + + The minimum number of times this parameter SHALL appear in the request or response. + + + + + The maximum number of times this element is permitted to appear in the request or response. + + + + + Describes the meaning or use of this parameter. + + + + + The type for this parameter. + + + + + Used when the type is "Reference" or "canonical", and identifies a profile structure or implementation Guide that applies to the target of the reference this parameter refers to. If any profiles are specified, then the content must conform to at least one of them. The URL can be a local reference - to a contained StructureDefinition, or a reference to another StructureDefinition or Implementation Guide by a canonical URL. When an implementation guide is specified, the target resource SHALL conform to at least one profile defined in the implementation guide. + + + + + How the parameter is understood as a search parameter. This is only used if the parameter type is 'string'. + + + + + Binds to a value set if this parameter is coded (code, Coding, CodeableConcept). + + + + + Identifies other resource parameters within the operation invocation that are expected to resolve to this resource. + + + + + The parts of a nested Parameter. + + + + + + + + + A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction). + + + + + + + Indicates the degree of conformance expectations associated with this binding - that is, the degree to which the provided value set must be adhered to in the instances. + + + + + Points to the value set or external definition (e.g. implicit value set) that identifies the set of codes to be used. + + + + + + + + + A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction). + + + + + + + The name of the parameter or dot-separated path of parameter names pointing to the resource parameter that is expected to contain a reference to this resource. + + + + + The id of the element in the referencing resource that is expected to resolve to this resource. + + + + + + + + + A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction). + + + + + + + Name of parameter to include in overload. + + + + + Comments to go on overload. + + + + + + + + + + + In + + + + + Out + + + + + + + Whether an operation parameter is an input or an output parameter. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Operation + + + + + Query + + + + + + + Whether an operation is a normal operation or a query. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A collection of error, warning, or information messages that result from a system action. + + + + + A collection of error, warning, or information messages that result from a system action. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An error, warning, or information message that results from a system action. + + + + + + + + + A collection of error, warning, or information messages that result from a system action. + + + + + + + Indicates whether the issue indicates a variation from successful processing. + + + + + Describes the type of the issue. The system that creates an OperationOutcome SHALL choose the most applicable code from the IssueType value set, and may additional provide its own code for the error in the details element. + + + + + Additional details about the error. This may be a text description of the error or a system code that identifies the error. + + + + + Additional diagnostic information about the issue. + + + + + This element is deprecated because it is XML specific. It is replaced by issue.expression, which is format independent, and simpler to parse. + +For resource issues, this will be a simple XPath limited to element names, repetition indicators and the default child accessor that identifies one of the elements in the resource that caused this issue to be raised. For HTTP errors, will be "http." + the parameter name. + + + + + A [simple subset of FHIRPath](fhirpath.html#simple) limited to element names, repetition indicators and the default child accessor that identifies one of the elements in the resource that caused this issue to be raised. + + + + + + + + + + + Invalid Content + + + + + Structural Issue + + + + + Required element missing + + + + + Element value invalid + + + + + Validation rule failed + + + + + Security Problem + + + + + Login Required + + + + + Unknown User + + + + + Session Expired + + + + + Forbidden + + + + + Information Suppressed + + + + + Processing Failure + + + + + Content not supported + + + + + Duplicate + + + + + Multiple Matches + + + + + Not Found + + + + + Deleted + + + + + Content Too Long + + + + + Invalid Code + + + + + Unacceptable Extension + + + + + Operation Too Costly + + + + + Business Rule Violation + + + + + Edit Version Conflict + + + + + Transient Issue + + + + + Lock Error + + + + + No Store Available + + + + + Exception + + + + + Timeout + + + + + Incomplete Results + + + + + Throttled + + + + + Informational Note + + + + + + + A code that describes the type of issue. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Fatal + + + + + Error + + + + + Warning + + + + + Information + + + + + + + How the issue affects the success of the action. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes companies, institutions, corporations, departments, community groups, healthcare practice groups, payer/insurer, etc. + + + + + A formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes companies, institutions, corporations, departments, community groups, healthcare practice groups, payer/insurer, etc. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifier for the organization that is used to identify the organization across multiple disparate systems. + + + + + Whether the organization's record is still in active use. + + + + + The kind(s) of organization that this is. + + + + + A name associated with the organization. + + + + + A list of alternate names that the organization is known as, or was known as in the past. + + + + + A contact detail for the organization. + + + + + An address for the organization. + + + + + The organization of which this organization forms a part. + + + + + Contact for the organization for a certain purpose. + + + + + Technical endpoints providing access to services operated for the organization. + + + + + + + + + A formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes companies, institutions, corporations, departments, community groups, healthcare practice groups, payer/insurer, etc. + + + + + + + Indicates a purpose for which the contact can be reached. + + + + + A name associated with the contact. + + + + + A contact detail (e.g. a telephone number or an email address) by which the party may be contacted. + + + + + Visiting or postal addresses for the contact. + + + + + + + + + Defines an affiliation/assotiation/relationship between 2 distinct oganizations, that is not a part-of relationship/sub-division relationship. + + + + + Defines an affiliation/assotiation/relationship between 2 distinct oganizations, that is not a part-of relationship/sub-division relationship. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifiers that are specific to this role. + + + + + Whether this organization affiliation record is in active use. + + + + + The period during which the participatingOrganization is affiliated with the primary organization. + + + + + Organization where the role is available (primary organization/has members). + + + + + The Participating Organization provides/performs the role(s) defined by the code to the Primary Organization (e.g. providing services or is a member of). + + + + + Health insurance provider network in which the participatingOrganization provides the role's services (if defined) at the indicated locations (if defined). + + + + + Definition of the role the participatingOrganization plays in the association. + + + + + Specific specialty of the participatingOrganization in the context of the role. + + + + + The location(s) at which the role occurs. + + + + + Healthcare services provided through the role. + + + + + Contact details at the participatingOrganization relevant to this Affiliation. + + + + + Technical endpoints providing access to services operated for this role. + + + + + + + + + This resource is a non-persisted resource used to pass information into and back from an [operation](operations.html). It has no other use, and there is no RESTful endpoint associated with it. + + + + + This resource is a non-persisted resource used to pass information into and back from an [operation](operations.html). It has no other use, and there is no RESTful endpoint associated with it. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A parameter passed to or received from the operation. + + + + + + + + + This resource is a non-persisted resource used to pass information into and back from an [operation](operations.html). It has no other use, and there is no RESTful endpoint associated with it. + + + + + + + The name of the parameter (reference to the operation definition). + + + + + If the parameter is a data type. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + If the parameter is a whole resource. + + + + + A named part of a multi-part parameter. + + + + + + + + + Demographics and other administrative information about an individual or animal receiving care or other health-related services. + + + + + Demographics and other administrative information about an individual or animal receiving care or other health-related services. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An identifier for this patient. + + + + + Whether this patient record is in active use. +Many systems use this property to mark as non-current patients, such as those that have not been seen for a period of time based on an organization's business rules. + +It is often used to filter patient lists to exclude inactive patients + +Deceased patients may also be marked as inactive for the same reasons, but may be active for some time after death. + + + + + A name associated with the individual. + + + + + A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted. + + + + + Administrative Gender - the gender that the patient is considered to have for administration and record keeping purposes. + + + + + The date of birth for the individual. + + + + + Indicates if the individual is deceased or not. + + + + + + + An address for the individual. + + + + + This field contains a patient's most recent marital (civil) status. + + + + + Indicates whether the patient is part of a multiple (boolean) or indicates the actual birth order (integer). + + + + + + + Image of the patient. + + + + + A contact party (e.g. guardian, partner, friend) for the patient. + + + + + A language which may be used to communicate with the patient about his or her health. + + + + + Patient's nominated care provider. + + + + + Organization that is the custodian of the patient record. + + + + + Link to another patient resource that concerns the same actual patient. + + + + + + + + + Demographics and other administrative information about an individual or animal receiving care or other health-related services. + + + + + + + The nature of the relationship between the patient and the contact person. + + + + + A name associated with the contact person. + + + + + A contact detail for the person, e.g. a telephone number or an email address. + + + + + Address for the contact person. + + + + + Administrative Gender - the gender that the contact person is considered to have for administration and record keeping purposes. + + + + + Organization on behalf of which the contact is acting or for which the contact is working. + + + + + The period during which this contact person or organization is valid to be contacted relating to this patient. + + + + + + + + + Demographics and other administrative information about an individual or animal receiving care or other health-related services. + + + + + + + The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English. + + + + + Indicates whether or not the patient prefers this language (over other languages he masters up a certain level). + + + + + + + + + Demographics and other administrative information about an individual or animal receiving care or other health-related services. + + + + + + + The other patient resource that the link refers to. + + + + + The type of link between this patient resource and another patient resource. + + + + + + + + + + + Replaced-by + Vervangen door + + + + + Replaces + Vervangt + + + + + Refer + Verwijzing + + + + + See also + Zie ook + + + + + + + The type of link between this patient resource and another patient resource. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + This resource provides the status of the payment for goods and services rendered, and the request and response resource references. + + + + + This resource provides the status of the payment for goods and services rendered, and the request and response resource references. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A unique identifier assigned to this payment notice. + + + + + The status of the resource instance. + + + + + Reference of resource for which payment is being made. + + + + + Reference of response to resource for which payment is being made. + + + + + The date when this resource was created. + + + + + The practitioner who is responsible for the services rendered to the patient. + + + + + A reference to the payment which is the subject of this notice. + + + + + The date when the above payment action occurred. + + + + + The party who will receive or has received payment that is the subject of this notification. + + + + + The party who is notified of the payment status. + + + + + The amount sent to the payee. + + + + + A code indicating whether payment has been sent or cleared. + + + + + + + + + This resource provides the details including amount of a payment and allocates the payment items being paid. + + + + + This resource provides the details including amount of a payment and allocates the payment items being paid. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A unique identifier assigned to this payment reconciliation. + + + + + The status of the resource instance. + + + + + The period of time for which payments have been gathered into this bulk payment for settlement. + + + + + The date when the resource was created. + + + + + The party who generated the payment. + + + + + Original request resource reference. + + + + + The practitioner who is responsible for the services rendered to the patient. + + + + + The outcome of a request for a reconciliation. + + + + + A human readable description of the status of the request for the reconciliation. + + + + + The date of payment as indicated on the financial instrument. + + + + + Total payment amount as indicated on the financial instrument. + + + + + Issuer's unique identifier for the payment instrument. + + + + + Distribution of the payment amount for a previously acknowledged payable. + + + + + A code for the form to be used for printing the content. + + + + + A note that describes or explains the processing in a human readable form. + + + + + + + + + This resource provides the details including amount of a payment and allocates the payment items being paid. + + + + + + + Unique identifier for the current payment item for the referenced payable. + + + + + Unique identifier for the prior payment item for the referenced payable. + + + + + Code to indicate the nature of the payment. + + + + + A resource, such as a Claim, the evaluation of which could lead to payment. + + + + + The party which submitted the claim or financial transaction. + + + + + A resource, such as a ClaimResponse, which contains a commitment to payment. + + + + + The date from the response resource containing a commitment to pay. + + + + + A reference to the individual who is responsible for inquiries regarding the response and its payment. + + + + + The party which is receiving the payment. + + + + + The monetary amount allocated from the total payment to the payable. + + + + + + + + + This resource provides the details including amount of a payment and allocates the payment items being paid. + + + + + + + The business purpose of the note text. + + + + + The explanation or description associated with the processing. + + + + + + + + + Demographics and administrative information about a person independent of a specific health-related context. + + + + + Demographics and administrative information about a person independent of a specific health-related context. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifier for a person within a particular scope. + + + + + A name associated with the person. + + + + + A contact detail for the person, e.g. a telephone number or an email address. + + + + + Administrative Gender. + + + + + The birth date for the person. + + + + + One or more addresses for the person. + + + + + An image that can be displayed as a thumbnail of the person to enhance the identification of the individual. + + + + + The organization that is the custodian of the person record. + + + + + Whether this person's record is in active use. + + + + + Link to a resource that concerns the same actual person. + + + + + + + + + Demographics and administrative information about a person independent of a specific health-related context. + + + + + + + The resource to which this actual person is associated. + + + + + Level of assurance that this link is associated with the target resource. + + + + + + + + + + + Level 1 + + + + + Level 2 + + + + + Level 3 + + + + + Level 4 + + + + + + + The level of confidence that this link represents the same actual person, based on NIST Authentication Levels. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical artifacts such as clinical decision support rules, order sets and protocols. + + + + + This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical artifacts such as clinical decision support rules, order sets and protocols. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this plan definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this plan definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the plan definition is stored on different servers. + + + + + A formal identifier that is used to identify this plan definition when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the plan definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the plan definition 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. To provide a version consistent with the Decision Support Service specification, use the format Major.Minor.Revision (e.g. 1.0.0). For more information on versioning knowledge assets, refer to the Decision Support Service specification. Note that a version is required for non-experimental active artifacts. + + + + + A natural language name identifying the plan definition. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the plan definition. + + + + + An explanatory or alternate title for the plan definition giving additional information about its content. + + + + + A high-level category for the plan definition that distinguishes the kinds of systems that would be interested in the plan definition. + + + + + The status of this plan definition. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this plan definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + A code or group definition that describes the intended subject of the plan definition. + + + + + + + The date (and optionally time) when the plan definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the plan definition changes. + + + + + The name of the organization or individual that published the plan definition. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the plan definition from a consumer's perspective. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate plan definition instances. + + + + + A legal or geographic region in which the plan definition is intended to be used. + + + + + Explanation of why this plan definition is needed and why it has been designed as it has. + + + + + A detailed description of how the plan definition is used from a clinical perspective. + + + + + A copyright statement relating to the plan definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the plan definition. + + + + + The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. + + + + + The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. + + + + + The period during which the plan definition content was or is planned to be in active use. + + + + + Descriptive topics related to the content of the plan definition. Topics provide a high-level categorization of the definition that can be useful for filtering and searching. + + + + + An individiual or organization primarily involved in the creation and maintenance of the content. + + + + + An individual or organization primarily responsible for internal coherence of the content. + + + + + An individual or organization primarily responsible for review of some aspect of the content. + + + + + An individual or organization responsible for officially endorsing the content for use in some setting. + + + + + Related artifacts such as additional documentation, justification, or bibliographic references. + + + + + A reference to a Library resource containing any formal logic used by the plan definition. + + + + + Goals that describe what the activities within the plan are intended to achieve. For example, weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, etc. + + + + + An action or group of actions to be taken as part of the plan. + + + + + + + + + This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical artifacts such as clinical decision support rules, order sets and protocols. + + + + + + + Indicates a category the goal falls within. + + + + + Human-readable and/or coded description of a specific desired objective of care, such as "control blood pressure" or "negotiate an obstacle course" or "dance with child at wedding". + + + + + Identifies the expected level of importance associated with reaching/sustaining the defined goal. + + + + + The event after which the goal should begin being pursued. + + + + + Identifies problems, conditions, issues, or concerns the goal is intended to address. + + + + + Didactic or other informational resources associated with the goal that provide further supporting information about the goal. Information resources can include inline text commentary and links to web resources. + + + + + Indicates what should be done and within what timeframe. + + + + + + + + + This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical artifacts such as clinical decision support rules, order sets and protocols. + + + + + + + The parameter whose value is to be tracked, e.g. body weight, blood pressure, or hemoglobin A1c level. + + + + + The target value of the measure to be achieved to signify fulfillment of the goal, e.g. 150 pounds or 7.0%. Either the high or low or both values of the range can be specified. When a low value is missing, it indicates that the goal is achieved at any value at or below the high value. Similarly, if the high value is missing, it indicates that the goal is achieved at any value at or above the low value. + + + + + + + + Indicates the timeframe after the start of the goal in which the goal should be met. + + + + + + + + + This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical artifacts such as clinical decision support rules, order sets and protocols. + + + + + + + A user-visible prefix for the action. + + + + + The title of the action displayed to a user. + + + + + A brief description of the action used to provide a summary to display to the user. + + + + + A text equivalent of the action to be performed. This provides a human-interpretable description of the action when the definition is consumed by a system that might not be capable of interpreting it dynamically. + + + + + Indicates how quickly the action should be addressed with respect to other actions. + + + + + A code that provides meaning for the action or action group. For example, a section may have a LOINC code for the section of a documentation template. + + + + + A description of why this action is necessary or appropriate. + + + + + Didactic or other informational resources associated with the action that can be provided to the CDS recipient. Information resources can include inline text commentary and links to web resources. + + + + + Identifies goals that this action supports. The reference must be to a goal element defined within this plan definition. + + + + + A code or group definition that describes the intended subject of the action and its children, if any. + + + + + + + A description of when the action should be triggered. + + + + + An expression that describes applicability criteria or start/stop conditions for the action. + + + + + Defines input data requirements for the action. + + + + + Defines the outputs of the action, if any. + + + + + A relationship to another action such as "before" or "30-60 minutes after start of". + + + + + An optional value describing when the action should be performed. + + + + + + + + + + + Indicates who should participate in performing the action described. + + + + + The type of action to perform (create, update, remove). + + + + + Defines the grouping behavior for the action and its children. + + + + + Defines the selection behavior for the action and its children. + + + + + Defines the required behavior for the action. + + + + + Defines whether the action should usually be preselected. + + + + + Defines whether the action can be selected multiple times. + + + + + A reference to an ActivityDefinition that describes the action to be taken in detail, or a PlanDefinition that describes a series of actions to be taken. + + + + + + + A reference to a StructureMap resource that defines a transform that can be executed to produce the intent resource using the ActivityDefinition instance as the input. + + + + + Customizations that should be applied to the statically defined resource. For example, if the dosage of a medication must be computed based on the patient's weight, a customization would be used to specify an expression that calculated the weight, and the path on the resource that would contain the result. + + + + + Sub actions that are contained within the action. The behavior of this action determines the functionality of the sub-actions. For example, a selection behavior of at-most-one indicates that of the sub-actions, at most one may be chosen as part of realizing the action definition. + + + + + + + + + This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical artifacts such as clinical decision support rules, order sets and protocols. + + + + + + + The kind of condition. + + + + + An expression that returns true or false, indicating whether the condition is satisfied. + + + + + + + + + This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical artifacts such as clinical decision support rules, order sets and protocols. + + + + + + + The element id of the related action. + + + + + The relationship of this action to the related action. + + + + + A duration or range of durations to apply to the relationship. For example, 30-60 minutes before. + + + + + + + + + + + This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical artifacts such as clinical decision support rules, order sets and protocols. + + + + + + + The type of participant in the action. + + + + + The role the participant should play in performing the described action. + + + + + + + + + This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical artifacts such as clinical decision support rules, order sets and protocols. + + + + + + + The path to the element to be customized. This is the path on the resource that will hold the result of the calculation defined by the expression. The specified path SHALL be a FHIRPath resolveable on the specified target type of the ActivityDefinition, and SHALL consist only of identifiers, constant indexers, and a restricted subset of functions. The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements (see the [Simple FHIRPath Profile](fhirpath.html#simple) for full details). + + + + + An expression specifying the value of the customized element. + + + + + + + + + + + Must + + + + + Could + + + + + Must Unless Documented + + + + + + + Defines expectations around whether an action or action group is required. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Before Start + + + + + Before + + + + + Before End + + + + + Concurrent With Start + + + + + Concurrent + + + + + Concurrent With End + + + + + After Start + + + + + After + + + + + After End + + + + + + + Defines the types of relationships between actions. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Visual Group + + + + + Logical Group + + + + + Sentence Group + + + + + + + Defines organization behavior of a group. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Any + + + + + All + + + + + All Or None + + + + + Exactly One + + + + + At Most One + + + + + One Or More + + + + + + + Defines selection behavior of a group. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Single + + + + + Multiple + + + + + + + Defines behavior for an action or a group for how many times that item may be repeated. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Yes + + + + + No + + + + + + + Defines selection frequency behavior for an action or group. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Applicability + + + + + Start + + + + + Stop + + + + + + + Defines the kinds of conditions that can appear on actions. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A person who is directly or indirectly involved in the provisioning of healthcare. + + + + + A person who is directly or indirectly involved in the provisioning of healthcare. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An identifier that applies to this person in this role. + + + + + Whether this practitioner's record is in active use. + + + + + The name(s) associated with the practitioner. + + + + + A contact detail for the practitioner, e.g. a telephone number or an email address. + + + + + Address(es) of the practitioner that are not role specific (typically home address). Work addresses are not typically entered in this property as they are usually role dependent. + + + + + Administrative Gender - the gender that the person is considered to have for administration and record keeping purposes. + + + + + The date of birth for the practitioner. + + + + + Image of the person. + + + + + The official certifications, training, and licenses that authorize or otherwise pertain to the provision of care by the practitioner. For example, a medical license issued by a medical board authorizing the practitioner to practice medicine within a certian locality. + + + + + A language the practitioner can use in patient communication. + + + + + + + + + A person who is directly or indirectly involved in the provisioning of healthcare. + + + + + + + An identifier that applies to this person's qualification in this role. + + + + + Coded representation of the qualification. + + + + + Period during which the qualification is valid. + + + + + Organization that regulates and issues the qualification. + + + + + + + + + A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time. + + + + + A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business Identifiers that are specific to a role/location. + + + + + Whether this practitioner role record is in active use. + + + + + The period during which the person is authorized to act as a practitioner in these role(s) for the organization. + + + + + Practitioner that is able to provide the defined services for the organization. + + + + + The organization where the Practitioner performs the roles associated. + + + + + Roles which this practitioner is authorized to perform for the organization. + + + + + Specific specialty of the practitioner. + + + + + The location(s) at which this practitioner provides care. + + + + + The list of healthcare services that this worker provides for this role's Organization/Location(s). + + + + + Contact details that are specific to the role/location/service. + + + + + A collection of times the practitioner is available or performing this role at the location and/or healthcareservice. + + + + + The practitioner is not available or performing this role during this period of time due to the provided reason. + + + + + A description of site availability exceptions, e.g. public holiday availability. Succinctly describing all possible exceptions to normal site availability as details in the available Times and not available Times. + + + + + Technical endpoints providing access to services operated for the practitioner with this role. + + + + + + + + + A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time. + + + + + + + Indicates which days of the week are available between the start and end Times. + + + + + Is this always available? (hence times are irrelevant) e.g. 24 hour service. + + + + + The opening time of day. Note: If the AllDay flag is set, then this time is ignored. + + + + + The closing time of day. Note: If the AllDay flag is set, then this time is ignored. + + + + + + + + + A specific set of Roles/Locations/specialties/services that a practitioner may perform at an organization for a period of time. + + + + + + + The reason that can be presented to the user as to why this time is not available. + + + + + Service is not available (seasonally or for a public holiday) from this date. + + + + + + + + + An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy. + + + + + An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifiers assigned to this procedure by the performer or other systems which remain constant as the resource is updated and is propagated from server to server. + + + + + The URL pointing to a FHIR-defined protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure. + + + + + The URL pointing to an externally maintained protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure. + + + + + A reference to a resource that contains details of the request for this procedure. + + + + + A larger event of which this particular procedure is a component or step. + + + + + A code specifying the state of the procedure. Generally, this will be the in-progress or completed state. + + + + + Captures the reason for the current state of the procedure. + + + + + A code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure"). + + + + + The specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy"). + + + + + The person, animal or group on which the procedure was performed. + + + + + The Encounter during which this Procedure was created or performed or to which the creation of this record is tightly associated. + + + + + Estimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured. + + + + + + + + + + Individual who recorded the record and takes responsibility for its content. + + + + + Individual who is making the procedure statement. + + + + + Limited to "real" people rather than equipment. + + + + + The location where the procedure actually happened. E.g. a newborn at home, a tracheostomy at a restaurant. + + + + + The coded reason why the procedure was performed. This may be a coded entity of some type, or may simply be present as text. + + + + + The justification of why the procedure was performed. + + + + + Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion. + + + + + The outcome of the procedure - did it resolve the reasons for the procedure being performed? + + + + + This could be a histology result, pathology report, surgical report, etc. + + + + + Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the notes, which will typically describe the procedure itself rather than any 'post procedure' issues. + + + + + Any complications that occurred during the procedure, or in the immediate post-performance period. + + + + + If the procedure required specific follow up - e.g. removal of sutures. The follow up may be represented as a simple note or could potentially be more complex, in which case the CarePlan resource can be used. + + + + + Any other notes and comments about the procedure. + + + + + A device that is implanted, removed or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure. + + + + + Identifies medications, devices and any other substance used as part of the procedure. + + + + + Identifies coded items that were used as part of the procedure. + + + + + + + + + An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy. + + + + + + + Distinguishes the type of involvement of the performer in the procedure. For example, surgeon, anaesthetist, endoscopist. + + + + + The practitioner who was involved in the procedure. + + + + + The organization the device or practitioner was acting on behalf of. + + + + + + + + + An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy. + + + + + + + The kind of change that happened to the device during the procedure. + + + + + The device that was manipulated (changed) during the procedure. + + + + + + + + + Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource. Provenance provides a critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of contextual metadata and can themselves become important records with their own provenance. Provenance statement indicates clinical significance in terms of confidence in authenticity, reliability, and trustworthiness, integrity, and stage in lifecycle (e.g. Document Completion - has the artifact been legally authenticated), all of which may impact security, privacy, and trust policies. + + + + + Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource. Provenance provides a critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of contextual metadata and can themselves become important records with their own provenance. Provenance statement indicates clinical significance in terms of confidence in authenticity, reliability, and trustworthiness, integrity, and stage in lifecycle (e.g. Document Completion - has the artifact been legally authenticated), all of which may impact security, privacy, and trust policies. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + The Reference(s) that were generated or updated by the activity described in this resource. A provenance can point to more than one target if multiple resources were created/updated by the same activity. + + + + + The period during which the activity occurred. + + + + + + + The instant of time at which the activity was recorded. + + + + + Policy or plan the activity was defined by. Typically, a single activity may have multiple applicable policy documents, such as patient consent, guarantor funding, etc. + + + + + Where the activity occurred, if relevant. + + + + + The reason that the activity was taking place. + + + + + An activity is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities. + + + + + An actor taking a role in an activity for which it can be assigned some degree of responsibility for the activity taking place. + + + + + An entity used in this activity. + + + + + A digital signature on the target Reference(s). The signer should match a Provenance.agent. The purpose of the signature is indicated. + + + + + + + + + Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource. Provenance provides a critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of contextual metadata and can themselves become important records with their own provenance. Provenance statement indicates clinical significance in terms of confidence in authenticity, reliability, and trustworthiness, integrity, and stage in lifecycle (e.g. Document Completion - has the artifact been legally authenticated), all of which may impact security, privacy, and trust policies. + + + + + + + The participation the agent had with respect to the activity. + + + + + The function of the agent with respect to the activity. The security role enabling the agent with respect to the activity. + + + + + The individual, device or organization that participated in the event. + + + + + The individual, device, or organization for whom the change was made. + + + + + + + + + Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource. Provenance provides a critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of contextual metadata and can themselves become important records with their own provenance. Provenance statement indicates clinical significance in terms of confidence in authenticity, reliability, and trustworthiness, integrity, and stage in lifecycle (e.g. Document Completion - has the artifact been legally authenticated), all of which may impact security, privacy, and trust policies. + + + + + + + How the entity was used during the activity. + + + + + Identity of the Entity used. May be a logical or physical uri and maybe absolute or relative. + + + + + The entity is attributed to an agent to express the agent's responsibility for that entity, possibly along with other agents. This description can be understood as shorthand for saying that the agent was responsible for the activity which generated the entity. + + + + + + + + + + + Derivation + + + + + Revision + + + + + Quotation + + + + + Source + + + + + Removal + + + + + + + How an entity was used in an activity. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection. + + + + + A structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this questionnaire is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the questionnaire is stored on different servers. + + + + + 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. + + + + + 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. + + + + + 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. + + + + + A short, descriptive, user-friendly title for the questionnaire. + + + + + The URL of a Questionnaire that this Questionnaire is based on. + + + + + The status of this questionnaire. Enables tracking the life-cycle of the content. + + + + + 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. + + + + + The types of subjects that can be the subject of responses created for the questionnaire. + + + + + The date (and optionally time) when the questionnaire was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the questionnaire changes. + + + + + The name of the organization or individual that published the questionnaire. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the questionnaire from a consumer's perspective. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate questionnaire instances. + + + + + A legal or geographic region in which the questionnaire is intended to be used. + + + + + Explanation of why this questionnaire is needed and why it has been designed as it has. + + + + + 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. + + + + + The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. + + + + + The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. + + + + + The period during which the questionnaire content was or is planned to be in active use. + + + + + An identifier for this question or group of questions in a particular terminology such as LOINC. + + + + + A particular question, question grouping or display text that is part of the questionnaire. + + + + + + + + + A structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection. + + + + + + + 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 [[[ElementDefinition]]] that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. A detailed description of the construction of the URI is shown in Comments, below. If this element is present then the following element values MAY be derived from the Element Definition if the corresponding elements of this Questionnaire resource instance have no value: + +* code (ElementDefinition.code) +* type (ElementDefinition.type) +* required (ElementDefinition.min) +* repeats (ElementDefinition.max) +* maxLength (ElementDefinition.maxLength) +* answerValueSet (ElementDefinition.binding) +* options (ElementDefinition.binding). + + + + + A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). + + + + + 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 name of a section, the text of a question or text content for a display item. + + + + + 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.). + + + + + A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. + + + + + Controls how multiple enableWhen values are interpreted - whether all or any must be true. + + + + + 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 the item may occur multiple times in the response, collecting multiple answers for questions or multiple sets of answers for groups. + + + + + 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. + + + + + A reference to a value set containing a list of codes representing permitted answers for a "choice" or "open-choice" question. + + + + + One of the permitted answers for a "choice" or "open-choice" question. + + + + + One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. + + + + + Text, questions and other groups to be nested beneath a question or group. + + + + + + + + + A structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection. + + + + + + + The linkId for the question whose answer (or lack of answer) governs whether this item is enabled. + + + + + Specifies the criteria by which the question is enabled. + + + + + A value that the referenced question is tested using the specified operator in order for the item to be enabled. + + + + + + + + + + + + + + + + + + + A structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection. + + + + + + + A potential answer that's allowed as the answer to this question. + + + + + + + + + + + Indicates whether the answer value is selected when the list of possible answers is initially shown. + + + + + + + + + A structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection. + + + + + + + The actual value to for an initial answer. + + + + + + + + + + + + + + + + + + + + + + + Group + + + + + Display + + + + + Boolean + + + + + Decimal + + + + + Integer + + + + + Date + + + + + Date Time + + + + + Time + + + + + String + + + + + Text + + + + + Url + + + + + Choice + + + + + Open Choice + + + + + Attachment + + + + + Reference + + + + + Quantity + + + + + + + Distinguishes groups from questions and display text and indicates data type for questions. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + All + + + + + Any + + + + + + + Controls how multiple enableWhen values are interpreted - whether all or any must be true. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Exists + + + + + Equals + + + + + Not Equals + + + + + Greater Than + + + + + Less Than + + + + + Greater or Equals + + + + + Less or Equals + + + + + + + The criteria by which a question is enabled. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A structured set of questions and their answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the questionnaire being responded to. + + + + + A structured set of questions and their answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the questionnaire being responded to. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A business identifier assigned to a particular completed (or partially completed) questionnaire. + + + + + The order, proposal or plan that is fulfilled in whole or in part by this QuestionnaireResponse. For example, a ServiceRequest seeking an intake assessment or a decision support recommendation to assess for post-partum depression. + + + + + 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. + + + + + The Questionnaire that defines and organizes the questions for which answers are being provided. + + + + + The position of the questionnaire response within its overall lifecycle. + + + + + 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. + + + + + The Encounter during which this questionnaire response was created or to which the creation of this record is tightly associated. + + + + + The date and/or time that this set of answers were last changed. + + + + + Person who received the answers to the questions in the QuestionnaireResponse and recorded them in the system. + + + + + The person who answered the questions about the subject. + + + + + A group or question item from the original questionnaire for which answers are provided. + + + + + + + + + A structured set of questions and their answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the questionnaire being responded to. + + + + + + + The item from the Questionnaire that corresponds to this item in the QuestionnaireResponse resource. + + + + + A reference to an [[[ElementDefinition]]] that provides the details for the item. + + + + + Text that is displayed above the contents of the group or as the text of the question being answered. + + + + + The respondent's answer(s) to the question. + + + + + Questions or sub-groups nested beneath a question or group. + + + + + + + + + A structured set of questions and their answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the questionnaire being responded to. + + + + + + + The answer (or one of the answers) provided by the respondent to the question. + + + + + + + + + + + + + + + + + Nested groups and/or questions found within this particular answer. + + + + + + + + + + + In Progress + + + + + Completed + + + + + Amended + + + + + Entered in Error + + + + + Stopped + + + + + + + Lifecycle status of the questionnaire response. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + Information about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process. + + + + + Information about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifier for a person within a particular scope. + + + + + Whether this related person record is in active use. + + + + + The patient this person is related to. + + + + + The nature of the relationship between a patient and the related person. + + + + + A name associated with the person. + + + + + A contact detail for the person, e.g. a telephone number or an email address. + + + + + Administrative Gender - the gender that the person is considered to have for administration and record keeping purposes. + + + + + The date on which the related person was born. + + + + + Address where the related person can be contacted or visited. + + + + + Image of the person. + + + + + The period of time during which this relationship is or was active. If there are no dates defined, then the interval is unknown. + + + + + A language which may be used to communicate with about the patient's health. + + + + + + + + + Information about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process. + + + + + + + The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English. + + + + + Indicates whether or not the patient prefers this language (over other languages he masters up a certain level). + + + + + + + + + A group of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one". + + + + + A group of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one". + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Allows a service to provide a unique, business identifier for the request. + + + + + A canonical URL referencing a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this request. + + + + + A URL referencing an externally defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this request. + + + + + A plan, proposal or order that is fulfilled in whole or in part by this request. + + + + + Completed or terminated request(s) whose function is taken by this new request. + + + + + A shared identifier common to all requests that were authorized more or less simultaneously by a single author, representing the identifier of the requisition, prescription or similar form. + + + + + The current state of the request. For request groups, the status reflects the status of all the requests in the group. + + + + + Indicates the level of authority/intentionality associated with the request and where the request fits into the workflow chain. + + + + + Indicates how quickly the request should be addressed with respect to other requests. + + + + + A code that identifies what the overall request group is. + + + + + The subject for which the request group was created. + + + + + Describes the context of the request group, if any. + + + + + Indicates when the request group was created. + + + + + Provides a reference to the author of the request group. + + + + + Describes the reason for the request group in coded or textual form. + + + + + Indicates another resource whose existence justifies this request group. + + + + + Provides a mechanism to communicate additional information about the response. + + + + + The actions, if any, produced by the evaluation of the artifact. + + + + + + + + + A group of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one". + + + + + + + A user-visible prefix for the action. + + + + + The title of the action displayed to a user. + + + + + A short description of the action used to provide a summary to display to the user. + + + + + A text equivalent of the action to be performed. This provides a human-interpretable description of the action when the definition is consumed by a system that might not be capable of interpreting it dynamically. + + + + + Indicates how quickly the action should be addressed with respect to other actions. + + + + + A code that provides meaning for the action or action group. For example, a section may have a LOINC code for a section of a documentation template. + + + + + Didactic or other informational resources associated with the action that can be provided to the CDS recipient. Information resources can include inline text commentary and links to web resources. + + + + + An expression that describes applicability criteria, or start/stop conditions for the action. + + + + + A relationship to another action such as "before" or "30-60 minutes after start of". + + + + + An optional value describing when the action should be performed. + + + + + + + + + + + The participant that should perform or be responsible for this action. + + + + + The type of action to perform (create, update, remove). + + + + + Defines the grouping behavior for the action and its children. + + + + + Defines the selection behavior for the action and its children. + + + + + Defines expectations around whether an action is required. + + + + + Defines whether the action should usually be preselected. + + + + + Defines whether the action can be selected multiple times. + + + + + The resource that is the target of the action (e.g. CommunicationRequest). + + + + + Sub actions. + + + + + + + + + A group of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one". + + + + + + + The kind of condition. + + + + + An expression that returns true or false, indicating whether or not the condition is satisfied. + + + + + + + + + A group of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one". + + + + + + + The element id of the action this is related to. + + + + + The relationship of this action to the related action. + + + + + A duration or range of durations to apply to the relationship. For example, 30-60 minutes before. + + + + + + + + + + + The ResearchDefinition resource describes the conditional state (population and any exposures being compared within the population) and outcome (if specified) that the knowledge (evidence, assertion, recommendation) is about. + + + + + The ResearchDefinition resource describes the conditional state (population and any exposures being compared within the population) and outcome (if specified) that the knowledge (evidence, assertion, recommendation) is about. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this research definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this research definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the research definition is stored on different servers. + + + + + A formal identifier that is used to identify this research definition when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the research definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the research definition 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. To provide a version consistent with the Decision Support Service specification, use the format Major.Minor.Revision (e.g. 1.0.0). For more information on versioning knowledge assets, refer to the Decision Support Service specification. Note that a version is required for non-experimental active artifacts. + + + + + A natural language name identifying the research definition. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the research definition. + + + + + The short title provides an alternate title for use in informal descriptive contexts where the full, formal title is not necessary. + + + + + An explanatory or alternate title for the ResearchDefinition giving additional information about its content. + + + + + The status of this research definition. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this research definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The intended subjects for the ResearchDefinition. If this element is not provided, a Patient subject is assumed, but the subject of the ResearchDefinition can be anything. + + + + + + + The date (and optionally time) when the research definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the research definition changes. + + + + + The name of the organization or individual that published the research definition. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the research definition from a consumer's perspective. + + + + + A human-readable string to clarify or explain concepts about the resource. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate research definition instances. + + + + + A legal or geographic region in which the research definition is intended to be used. + + + + + Explanation of why this research definition is needed and why it has been designed as it has. + + + + + A detailed description, from a clinical perspective, of how the ResearchDefinition is used. + + + + + A copyright statement relating to the research definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the research definition. + + + + + The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. + + + + + The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. + + + + + The period during which the research definition content was or is planned to be in active use. + + + + + Descriptive topics related to the content of the ResearchDefinition. Topics provide a high-level categorization grouping types of ResearchDefinitions that can be useful for filtering and searching. + + + + + An individiual or organization primarily involved in the creation and maintenance of the content. + + + + + An individual or organization primarily responsible for internal coherence of the content. + + + + + An individual or organization primarily responsible for review of some aspect of the content. + + + + + An individual or organization responsible for officially endorsing the content for use in some setting. + + + + + Related artifacts such as additional documentation, justification, or bibliographic references. + + + + + A reference to a Library resource containing the formal logic used by the ResearchDefinition. + + + + + A reference to a ResearchElementDefinition resource that defines the population for the research. + + + + + A reference to a ResearchElementDefinition resource that defines the exposure for the research. + + + + + A reference to a ResearchElementDefinition resource that defines the exposureAlternative for the research. + + + + + A reference to a ResearchElementDefinition resomece that defines the outcome for the research. + + + + + + + + + The ResearchElementDefinition resource describes a "PICO" element that knowledge (evidence, assertion, recommendation) is about. + + + + + The ResearchElementDefinition resource describes a "PICO" element that knowledge (evidence, assertion, recommendation) is about. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this research element definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this research element definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the research element definition is stored on different servers. + + + + + A formal identifier that is used to identify this research element definition when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the research element definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the research element definition 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. To provide a version consistent with the Decision Support Service specification, use the format Major.Minor.Revision (e.g. 1.0.0). For more information on versioning knowledge assets, refer to the Decision Support Service specification. Note that a version is required for non-experimental active artifacts. + + + + + A natural language name identifying the research element definition. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the research element definition. + + + + + The short title provides an alternate title for use in informal descriptive contexts where the full, formal title is not necessary. + + + + + An explanatory or alternate title for the ResearchElementDefinition giving additional information about its content. + + + + + The status of this research element definition. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this research element definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The intended subjects for the ResearchElementDefinition. If this element is not provided, a Patient subject is assumed, but the subject of the ResearchElementDefinition can be anything. + + + + + + + The date (and optionally time) when the research element definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the research element definition changes. + + + + + The name of the organization or individual that published the research element definition. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the research element definition from a consumer's perspective. + + + + + A human-readable string to clarify or explain concepts about the resource. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate research element definition instances. + + + + + A legal or geographic region in which the research element definition is intended to be used. + + + + + Explanation of why this research element definition is needed and why it has been designed as it has. + + + + + A detailed description, from a clinical perspective, of how the ResearchElementDefinition is used. + + + + + A copyright statement relating to the research element definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the research element definition. + + + + + The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. + + + + + The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. + + + + + The period during which the research element definition content was or is planned to be in active use. + + + + + Descriptive topics related to the content of the ResearchElementDefinition. Topics provide a high-level categorization grouping types of ResearchElementDefinitions that can be useful for filtering and searching. + + + + + An individiual or organization primarily involved in the creation and maintenance of the content. + + + + + An individual or organization primarily responsible for internal coherence of the content. + + + + + An individual or organization primarily responsible for review of some aspect of the content. + + + + + An individual or organization responsible for officially endorsing the content for use in some setting. + + + + + Related artifacts such as additional documentation, justification, or bibliographic references. + + + + + A reference to a Library resource containing the formal logic used by the ResearchElementDefinition. + + + + + The type of research element, a population, an exposure, or an outcome. + + + + + The type of the outcome (e.g. Dichotomous, Continuous, or Descriptive). + + + + + A characteristic that defines the members of the research element. Multiple characteristics are applied with "and" semantics. + + + + + + + + + The ResearchElementDefinition resource describes a "PICO" element that knowledge (evidence, assertion, recommendation) is about. + + + + + + + Define members of the research element using Codes (such as condition, medication, or observation), Expressions ( using an expression language such as FHIRPath or CQL) or DataRequirements (such as Diabetes diagnosis onset in the last year). + + + + + + + + + Use UsageContext to define the members of the population, such as Age Ranges, Genders, Settings. + + + + + When true, members with this characteristic are excluded from the element. + + + + + Specifies the UCUM unit for the outcome. + + + + + A narrative description of the time period the study covers. + + + + + Indicates what effective period the study covers. + + + + + + + + + Indicates duration from the study initiation. + + + + + Indicates how elements are aggregated within the study effective period. + + + + + A narrative description of the time period the study covers. + + + + + Indicates what effective period the study covers. + + + + + + + + + Indicates duration from the participant's study entry. + + + + + Indicates how elements are aggregated within the study effective period. + + + + + + + + + + + Population + + + + + Exposure + + + + + Outcome + + + + + + + The possible types of research elements (E.g. Population, Exposure, Outcome). + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Dichotomous + + + + + Continuous + + + + + Descriptive + + + + + + + The possible types of variables for exposures or outcomes (E.g. Dichotomous, Continuous, Descriptive). + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A process where a researcher or organization plans and then executes a series of steps intended to increase the field of healthcare-related knowledge. This includes studies of safety, efficacy, comparative effectiveness and other information about medications, devices, therapies and other interventional and investigative techniques. A ResearchStudy involves the gathering of information about human or animal subjects. + + + + + A process where a researcher or organization plans and then executes a series of steps intended to increase the field of healthcare-related knowledge. This includes studies of safety, efficacy, comparative effectiveness and other information about medications, devices, therapies and other interventional and investigative techniques. A ResearchStudy involves the gathering of information about human or animal subjects. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifiers assigned to this research study by the sponsor or other systems. + + + + + A short, descriptive user-friendly label for the study. + + + + + The set of steps expected to be performed as part of the execution of the study. + + + + + A larger research study of which this particular study is a component or step. + + + + + The current state of the study. + + + + + The type of study based upon the intent of the study's activities. A classification of the intent of the study. + + + + + The stage in the progression of a therapy from initial experimental use in humans in clinical trials to post-market evaluation. + + + + + Codes categorizing the type of study such as investigational vs. observational, type of blinding, type of randomization, safety vs. efficacy, etc. + + + + + The medication(s), food(s), therapy(ies), device(s) or other concerns or interventions that the study is seeking to gain more information about. + + + + + The condition that is the focus of the study. For example, In a study to examine risk factors for Lupus, might have as an inclusion criterion "healthy volunteer", but the target condition code would be a Lupus SNOMED code. + + + + + Contact details to assist a user in learning more about or engaging with the study. + + + + + Citations, references and other related documents. + + + + + Key terms to aid in searching for or filtering the study. + + + + + Indicates a country, state or other region where the study is taking place. + + + + + A full description of how the study is being conducted. + + + + + Reference to a Group that defines the criteria for and quantity of subjects participating in the study. E.g. " 200 female Europeans between the ages of 20 and 45 with early onset diabetes". + + + + + Identifies the start date and the expected (or actual, depending on status) end date for the study. + + + + + An organization that initiates the investigation and is legally responsible for the study. + + + + + A researcher in a study who oversees multiple aspects of the study, such as concept development, protocol writing, protocol submission for IRB approval, participant recruitment, informed consent, data collection, analysis, interpretation and presentation. + + + + + A facility in which study activities are conducted. + + + + + A description and/or code explaining the premature termination of the study. + + + + + Comments made about the study by the performer, subject or other participants. + + + + + Describes an expected sequence of events for one of the participants of a study. E.g. Exposure to drug A, wash-out, exposure to drug B, wash-out, follow-up. + + + + + A goal that the study is aiming to achieve in terms of a scientific question to be answered by the analysis of data collected during the study. + + + + + + + + + A process where a researcher or organization plans and then executes a series of steps intended to increase the field of healthcare-related knowledge. This includes studies of safety, efficacy, comparative effectiveness and other information about medications, devices, therapies and other interventional and investigative techniques. A ResearchStudy involves the gathering of information about human or animal subjects. + + + + + + + Unique, human-readable label for this arm of the study. + + + + + Categorization of study arm, e.g. experimental, active comparator, placebo comparater. + + + + + A succinct description of the path through the study that would be followed by a subject adhering to this arm. + + + + + + + + + A process where a researcher or organization plans and then executes a series of steps intended to increase the field of healthcare-related knowledge. This includes studies of safety, efficacy, comparative effectiveness and other information about medications, devices, therapies and other interventional and investigative techniques. A ResearchStudy involves the gathering of information about human or animal subjects. + + + + + + + Unique, human-readable label for this objective of the study. + + + + + The kind of study objective. + + + + + + + + + + + Active + + + + + Administratively Completed + + + + + Approved + + + + + Closed to Accrual + + + + + Closed to Accrual and Intervention + + + + + Completed + + + + + Disapproved + + + + + In Review + + + + + Temporarily Closed to Accrual + + + + + Temporarily Closed to Accrual and Intervention + + + + + Withdrawn + + + + + + + Codes that convey the current status of the research study. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A physical entity which is the primary unit of operational and/or administrative interest in a study. + + + + + A physical entity which is the primary unit of operational and/or administrative interest in a study. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifiers assigned to this research subject for a study. + + + + + The current state of the subject. + + + + + The dates the subject began and ended their participation in the study. + + + + + Reference to the study the subject is participating in. + + + + + The record of the person or animal who is involved in the study. + + + + + The name of the arm in the study the subject is expected to follow as part of this study. + + + + + The name of the arm in the study the subject actually followed as part of this study. + + + + + A record of the patient's informed agreement to participate in the study. + + + + + + + + + + + Candidate + + + + + Eligible + + + + + Follow-up + + + + + Ineligible + + + + + Not Registered + + + + + Off-study + + + + + On-study + + + + + On-study-intervention + + + + + On-study-observation + + + + + Pending on-study + + + + + Potential Candidate + + + + + Screening + + + + + Withdrawn + + + + + + + Indicates the progression of a study subject through a study. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome. + + + + + An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifier assigned to the risk assessment. + + + + + A reference to the request that is fulfilled by this risk assessment. + + + + + A reference to a resource that this risk assessment is part of, such as a Procedure. + + + + + The status of the RiskAssessment, using the same statuses as an Observation. + + + + + The algorithm, process or mechanism used to evaluate the risk. + + + + + The type of the risk assessment performed. + + + + + The patient or group the risk assessment applies to. + + + + + The encounter where the assessment was performed. + + + + + The date (and possibly time) the risk assessment was performed. + + + + + + + For assessments or prognosis specific to a particular condition, indicates the condition being assessed. + + + + + The provider or software application that performed the assessment. + + + + + The reason the risk assessment was performed. + + + + + Resources supporting the reason the risk assessment was performed. + + + + + Indicates the source data considered as part of the assessment (for example, FamilyHistory, Observations, Procedures, Conditions, etc.). + + + + + Describes the expected outcome for the subject. + + + + + A description of the steps that might be taken to reduce the identified risk(s). + + + + + Additional comments about the risk assessment. + + + + + + + + + An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome. + + + + + + + One of the potential outcomes for the patient (e.g. remission, death, a particular condition). + + + + + Indicates how likely the outcome is (in the specified timeframe). + + + + + + + Indicates how likely the outcome is (in the specified timeframe), expressed as a qualitative value (e.g. low, medium, or high). + + + + + Indicates the risk for this particular subject (with their specific characteristics) divided by the risk of the population in general. (Numbers greater than 1 = higher risk than the population, numbers less than 1 = lower risk.). + + + + + Indicates the period of time or age range of the subject to which the specified probability applies. + + + + + + + Additional information explaining the basis for the prediction. + + + + + + + + + The RiskEvidenceSynthesis resource describes the likelihood of an outcome in a population plus exposure state where the risk estimate is derived from a combination of research studies. + + + + + The RiskEvidenceSynthesis resource describes the likelihood of an outcome in a population plus exposure state where the risk estimate is derived from a combination of research studies. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this risk evidence synthesis when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this risk evidence synthesis is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the risk evidence synthesis is stored on different servers. + + + + + A formal identifier that is used to identify this risk evidence synthesis when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the risk evidence synthesis when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the risk evidence synthesis 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. + + + + + A natural language name identifying the risk evidence synthesis. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the risk evidence synthesis. + + + + + The status of this risk evidence synthesis. Enables tracking the life-cycle of the content. + + + + + The date (and optionally time) when the risk evidence synthesis was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the risk evidence synthesis changes. + + + + + The name of the organization or individual that published the risk evidence synthesis. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the risk evidence synthesis from a consumer's perspective. + + + + + A human-readable string to clarify or explain concepts about the resource. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate risk evidence synthesis instances. + + + + + A legal or geographic region in which the risk evidence synthesis is intended to be used. + + + + + A copyright statement relating to the risk evidence synthesis and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the risk evidence synthesis. + + + + + The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. + + + + + The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. + + + + + The period during which the risk evidence synthesis content was or is planned to be in active use. + + + + + Descriptive topics related to the content of the RiskEvidenceSynthesis. Topics provide a high-level categorization grouping types of EffectEvidenceSynthesiss that can be useful for filtering and searching. + + + + + An individiual or organization primarily involved in the creation and maintenance of the content. + + + + + An individual or organization primarily responsible for internal coherence of the content. + + + + + An individual or organization primarily responsible for review of some aspect of the content. + + + + + An individual or organization responsible for officially endorsing the content for use in some setting. + + + + + Related artifacts such as additional documentation, justification, or bibliographic references. + + + + + Type of synthesis eg meta-analysis. + + + + + Type of study eg randomized trial. + + + + + A reference to a EvidenceVariable resource that defines the population for the research. + + + + + A reference to a EvidenceVariable resource that defines the exposure for the research. + + + + + A reference to a EvidenceVariable resomece that defines the outcome for the research. + + + + + A description of the size of the sample involved in the synthesis. + + + + + The estimated risk of the outcome. + + + + + A description of the certainty of the risk estimate. + + + + + + + + + The RiskEvidenceSynthesis resource describes the likelihood of an outcome in a population plus exposure state where the risk estimate is derived from a combination of research studies. + + + + + + + Human-readable summary of sample size. + + + + + Number of studies included in this evidence synthesis. + + + + + Number of participants included in this evidence synthesis. + + + + + + + + + The RiskEvidenceSynthesis resource describes the likelihood of an outcome in a population plus exposure state where the risk estimate is derived from a combination of research studies. + + + + + + + Human-readable summary of risk estimate. + + + + + Examples include proportion and mean. + + + + + The point estimate of the risk estimate. + + + + + Specifies the UCUM unit for the outcome. + + + + + The sample size for the group that was measured for this risk estimate. + + + + + The number of group members with the outcome of interest. + + + + + A description of the precision of the estimate for the effect. + + + + + + + + + The RiskEvidenceSynthesis resource describes the likelihood of an outcome in a population plus exposure state where the risk estimate is derived from a combination of research studies. + + + + + + + Examples include confidence interval and interquartile range. + + + + + Use 95 for a 95% confidence interval. + + + + + Lower bound of confidence interval. + + + + + Upper bound of confidence interval. + + + + + + + + + The RiskEvidenceSynthesis resource describes the likelihood of an outcome in a population plus exposure state where the risk estimate is derived from a combination of research studies. + + + + + + + A rating of the certainty of the effect estimate. + + + + + A human-readable string to clarify or explain concepts about the resource. + + + + + A description of a component of the overall certainty. + + + + + + + + + The RiskEvidenceSynthesis resource describes the likelihood of an outcome in a population plus exposure state where the risk estimate is derived from a combination of research studies. + + + + + + + Type of subcomponent of certainty rating. + + + + + A rating of a subcomponent of rating certainty. + + + + + A human-readable string to clarify or explain concepts about the resource. + + + + + + + + + A container for slots of time that may be available for booking appointments. + + + + + A container for slots of time that may be available for booking appointments. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + External Ids for this item. + + + + + Whether this schedule record is in active use or should not be used (such as was entered in error). + + + + + A broad categorization of the service that is to be performed during this appointment. + + + + + The specific service that is to be performed during this appointment. + + + + + The specialty of a practitioner that would be required to perform the service requested in this appointment. + + + + + Slots that reference this schedule resource provide the availability details to these referenced resource(s). + + + + + The period of time that the slots that reference this Schedule resource cover (even if none exist). These cover the amount of time that an organization's planning horizon; the interval for which they are currently accepting appointments. This does not define a "template" for planning outside these dates. + + + + + Comments on the availability to describe any extended information. Such as custom constraints on the slots that may be associated. + + + + + + + + + A search parameter that defines a named search item that can be used to search/filter on a resource. + + + + + A search parameter that defines a named search item that can be used to search/filter on a resource. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this search parameter when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this search parameter is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the search parameter is stored on different servers. + + + + + The identifier that is used to identify this version of the search parameter when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the search parameter 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. + + + + + A natural language name identifying the search parameter. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + Where this search parameter is originally defined. If a derivedFrom is provided, then the details in the search parameter must be consistent with the definition from which it is defined. i.e. the parameter should have the same meaning, and (usually) the functionality should be a proper subset of the underlying search parameter. + + + + + The status of this search parameter. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this search parameter is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The date (and optionally time) when the search parameter was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the search parameter changes. + + + + + The name of the organization or individual that published the search parameter. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + And how it used. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate search parameter instances. + + + + + A legal or geographic region in which the search parameter is intended to be used. + + + + + Explanation of why this search parameter is needed and why it has been designed as it has. + + + + + The code used in the URL or the parameter name in a parameters resource for this search parameter. + + + + + The base resource type(s) that this search parameter can be used against. + + + + + The type of value that a search parameter may contain, and how the content is interpreted. + + + + + A FHIRPath expression that returns a set of elements for the search parameter. + + + + + An XPath expression that returns a set of elements for the search parameter. + + + + + How the search parameter relates to the set of elements returned by evaluating the xpath query. + + + + + Types of resource (if a resource is referenced). + + + + + Whether multiple values are allowed for each time the parameter exists. Values are separated by commas, and the parameter matches if any of the values match. + + + + + Whether multiple parameters are allowed - e.g. more than one parameter with the same name. The search matches if all the parameters match. + + + + + Comparators supported for the search parameter. + + + + + A modifier supported for the search parameter. + + + + + Contains the names of any search parameters which may be chained to the containing search parameter. Chained parameters may be added to search parameters of type reference and specify that resources will only be returned if they contain a reference to a resource which matches the chained parameter value. Values for this field should be drawn from SearchParameter.code for a parameter on the target resource type. + + + + + Used to define the parts of a composite search parameter. + + + + + + + + + A search parameter that defines a named search item that can be used to search/filter on a resource. + + + + + + + The definition of the search parameter that describes this part. + + + + + A sub-expression that defines how to extract values for this component from the output of the main SearchParameter.expression. + + + + + + + + + + + Normal + + + + + Phonetic + + + + + Nearby + + + + + Distance + + + + + Other + + + + + + + How a search parameter relates to the set of elements returned by evaluating its xpath query. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Missing + + + + + Exact + + + + + Contains + + + + + Not + + + + + Text + + + + + In + + + + + Not In + + + + + Below + + + + + Above + + + + + Type + + + + + Identifier + + + + + Of Type + + + + + + + A supported modifier for a search parameter. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Equals + + + + + Not Equals + + + + + Greater Than + + + + + Less Than + + + + + Greater or Equals + + + + + Less of Equal + + + + + Starts After + + + + + Ends Before + + + + + Approximately + + + + + + + What Search Comparator Codes are supported in search. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A record of a request for service such as diagnostic investigations, treatments, or operations to be performed. + + + + + A record of a request for service such as diagnostic investigations, treatments, or operations to be performed. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifiers assigned to this order instance by the orderer and/or the receiver and/or order fulfiller. + + + + + The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this ServiceRequest. + + + + + The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this ServiceRequest. + + + + + Plan/proposal/order fulfilled by this request. + + + + + The request takes the place of the referenced completed or terminated request(s). + + + + + A shared identifier common to all service requests that were authorized more or less simultaneously by a single author, representing the composite or group identifier. + + + + + The status of the order. + + + + + Whether the request is a proposal, plan, an original order or a reflex order. + + + + + A code that classifies the service for searching, sorting and display purposes (e.g. "Surgical Procedure"). + + + + + Indicates how quickly the ServiceRequest should be addressed with respect to other requests. + + + + + Set this to true if the record is saying that the service/procedure should NOT be performed. + + + + + A code that identifies a particular service (i.e., procedure, diagnostic investigation, or panel of investigations) that have been requested. + + + + + Additional details and instructions about the how the services are to be delivered. For example, and order for a urinary catheter may have an order detail for an external or indwelling catheter, or an order for a bandage may require additional instructions specifying how the bandage should be applied. + + + + + An amount of service being requested which can be a quantity ( for example $1,500 home modification), a ratio ( for example, 20 half day visits per month), or a range (2.0 to 1.8 Gy per fraction). + + + + + + + + On whom or what the service is to be performed. This is usually a human patient, but can also be requested on animals, groups of humans or animals, devices such as dialysis machines, or even locations (typically for environmental scans). + + + + + An encounter that provides additional information about the healthcare context in which this request is made. + + + + + The date/time at which the requested service should occur. + + + + + + + + If a CodeableConcept is present, it indicates the pre-condition for performing the service. For example "pain", "on flare-up", etc. + + + + + + + When the request transitioned to being actionable. + + + + + The individual who initiated the request and has responsibility for its activation. + + + + + Desired type of performer for doing the requested service. + + + + + The desired performer for doing the requested service. For example, the surgeon, dermatopathologist, endoscopist, etc. + + + + + The preferred location(s) where the procedure should actually happen in coded or free text form. E.g. at home or nursing day care center. + + + + + A reference to the the preferred location(s) where the procedure should actually happen. E.g. at home or nursing day care center. + + + + + An explanation or justification for why this service is being requested in coded or textual form. This is often for billing purposes. May relate to the resources referred to in `supportingInfo`. + + + + + Indicates another resource that provides a justification for why this service is being requested. May relate to the resources referred to in `supportingInfo`. + + + + + Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be needed for delivering the requested service. + + + + + Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as "ask at order entry questions (AOEs)". This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements. + + + + + One or more specimens that the laboratory procedure will use. + + + + + Anatomic location where the procedure should be performed. This is the target site. + + + + + Any other notes and comments made about the service request. For example, internal billing notes. + + + + + Instructions in terms that are understood by the patient or consumer. + + + + + Key events in the history of the request. + + + + + + + + + A slot of time on a schedule that may be available for booking appointments. + + + + + A slot of time on a schedule that may be available for booking appointments. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + External Ids for this item. + + + + + A broad categorization of the service that is to be performed during this appointment. + + + + + The type of appointments that can be booked into this slot (ideally this would be an identifiable service - which is at a location, rather than the location itself). If provided then this overrides the value provided on the availability resource. + + + + + The specialty of a practitioner that would be required to perform the service requested in this appointment. + + + + + The style of appointment or patient that may be booked in the slot (not service type). + + + + + The schedule resource that this slot defines an interval of status information. + + + + + busy | free | busy-unavailable | busy-tentative | entered-in-error. + + + + + Date/Time that the slot is to begin. + + + + + Date/Time that the slot is to conclude. + + + + + This slot has already been overbooked, appointments are unlikely to be accepted for this time. + + + + + Comments on the slot to describe any extended information. Such as custom constraints on the slot. + + + + + + + + + + + Busy + + + + + Free + + + + + Busy (Unavailable) + + + + + Busy (Tentative) + + + + + Entered in error + + + + + + + The free/busy status of the slot. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A sample to be used for analysis. + + + + + A sample to be used for analysis. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Id for specimen. + + + + + The identifier assigned by the lab when accessioning specimen(s). This is not necessarily the same as the specimen identifier, depending on local lab procedures. + + + + + The availability of the specimen. + + + + + The kind of material that forms the specimen. + + + + + Where the specimen came from. This may be from patient(s), from a location (e.g., the source of an environmental sample), or a sampling of a substance or a device. + + + + + Time when specimen was received for processing or testing. + + + + + Reference to the parent (source) specimen which is used when the specimen was either derived from or a component of another specimen. + + + + + Details concerning a service request that required a specimen to be collected. + + + + + Details concerning the specimen collection. + + + + + Details concerning processing and processing steps for the specimen. + + + + + The container holding the specimen. The recursive nature of containers; i.e. blood in tube in tray in rack is not addressed here. + + + + + A mode or state of being that describes the nature of the specimen. + + + + + To communicate any details or issues about the specimen or during the specimen collection. (for example: broken vial, sent with patient, frozen). + + + + + + + + + A sample to be used for analysis. + + + + + + + Person who collected the specimen. + + + + + Time when specimen was collected from subject - the physiologically relevant time. + + + + + + + The span of time over which the collection of a specimen occurred. + + + + + The quantity of specimen collected; for instance the volume of a blood sample, or the physical measurement of an anatomic pathology sample. + + + + + A coded value specifying the technique that is used to perform the procedure. + + + + + Anatomical location from which the specimen was collected (if subject is a patient). This is the target site. This element is not used for environmental specimens. + + + + + Abstinence or reduction from some or all food, drink, or both, for a period of time prior to sample collection. + + + + + + + + + + + A sample to be used for analysis. + + + + + + + Textual description of procedure. + + + + + A coded value specifying the procedure used to process the specimen. + + + + + Material used in the processing step. + + + + + A record of the time or period when the specimen processing occurred. For example the time of sample fixation or the period of time the sample was in formalin. + + + + + + + + + + + A sample to be used for analysis. + + + + + + + Id for container. There may be multiple; a manufacturer's bar code, lab assigned identifier, etc. The container ID may differ from the specimen id in some circumstances. + + + + + Textual description of the container. + + + + + The type of container associated with the specimen (e.g. slide, aliquot, etc.). + + + + + The capacity (volume or other measure) the container may contain. + + + + + The quantity of specimen in the container; may be volume, dimensions, or other appropriate measurements, depending on the specimen type. + + + + + Introduced substance to preserve, maintain or enhance the specimen. Examples: Formalin, Citrate, EDTA. + + + + + + + + + + + + + Available + + + + + Unavailable + + + + + Unsatisfactory + + + + + Entered in Error + + + + + + + Codes providing the status/availability of a specimen. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A kind of specimen with associated set of requirements. + + + + + A kind of specimen with associated set of requirements. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A business identifier associated with the kind of specimen. + + + + + The kind of material to be collected. + + + + + Preparation of the patient for specimen collection. + + + + + Time aspect of specimen collection (duration or offset). + + + + + The action to be performed for collecting the specimen. + + + + + Specimen conditioned in a container as expected by the testing laboratory. + + + + + + + + + A kind of specimen with associated set of requirements. + + + + + + + Primary of secondary specimen. + + + + + The kind of specimen conditioned for testing expected by lab. + + + + + The preference for this type of conditioned specimen. + + + + + The specimen's container. + + + + + Requirements for delivery and special handling of this kind of conditioned specimen. + + + + + The usual time that a specimen of this kind is retained after the ordered tests are completed, for the purpose of additional testing. + + + + + Criterion for rejection of the specimen in its container by the laboratory. + + + + + Set of instructions for preservation/transport of the specimen at a defined temperature interval, prior the testing process. + + + + + + + + + A kind of specimen with associated set of requirements. + + + + + + + The type of material of the container. + + + + + The type of container used to contain this kind of specimen. + + + + + Color of container cap. + + + + + The textual description of the kind of container. + + + + + The capacity (volume or other measure) of this kind of container. + + + + + The minimum volume to be conditioned in the container. + + + + + + + Substance introduced in the kind of container to preserve, maintain or enhance the specimen. Examples: Formalin, Citrate, EDTA. + + + + + Special processing that should be applied to the container for this kind of specimen. + + + + + + + + + A kind of specimen with associated set of requirements. + + + + + + + Substance introduced in the kind of container to preserve, maintain or enhance the specimen. Examples: Formalin, Citrate, EDTA. + + + + + + + + + + + A kind of specimen with associated set of requirements. + + + + + + + It qualifies the interval of temperature, which characterizes an occurrence of handling. Conditions that are not related to temperature may be handled in the instruction element. + + + + + The temperature interval for this set of handling instructions. + + + + + The maximum time interval of preservation of the specimen with these conditions. + + + + + Additional textual instructions for the preservation or transport of the specimen. For instance, 'Protect from light exposure'. + + + + + + + + + + + Preferred + + + + + Alternate + + + + + + + Degree of preference of a type of conditioned specimen. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A definition of a FHIR structure. This resource is used to describe the underlying resources, data types defined in FHIR, and also for describing extensions and constraints on resources and data types. + + + + + A definition of a FHIR structure. This resource is used to describe the underlying resources, data types defined in FHIR, and also for describing extensions and constraints on resources and data types. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this structure definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this structure definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the structure definition is stored on different servers. + + + + + A formal identifier that is used to identify this structure definition when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the structure definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the structure definition 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. + + + + + A natural language name identifying the structure definition. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the structure definition. + + + + + The status of this structure definition. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this structure definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The date (and optionally time) when the structure definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the structure definition changes. + + + + + The name of the organization or individual that published the structure definition. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the structure definition from a consumer's perspective. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate structure definition instances. + + + + + A legal or geographic region in which the structure definition is intended to be used. + + + + + Explanation of why this structure definition is needed and why it has been designed as it has. + + + + + A copyright statement relating to the structure definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the structure definition. + + + + + A set of key words or terms from external terminologies that may be used to assist with indexing and searching of templates nby describing the use of this structure definition, or the content it describes. + + + + + The version of the FHIR specification on which this StructureDefinition is based - this is the formal version of the specification, without the revision number, e.g. [publication].[major].[minor], which is 4.0.0. for this version. + + + + + An external specification that the content is mapped to. + + + + + Defines the kind of structure that this definition is describing. + + + + + Whether structure this definition describes is abstract or not - that is, whether the structure is not intended to be instantiated. For Resources and Data types, abstract types will never be exchanged between systems. + + + + + Identifies the types of resource or data type elements to which the extension can be applied. + + + + + A set of rules as FHIRPath Invariants about when the extension can be used (e.g. co-occurrence variants for the extension). All the rules must be true. + + + + + The type this structure describes. If the derivation kind is 'specialization' then this is the master definition for a type, and there is always one of these (a data type, an extension, a resource, including abstract ones). Otherwise the structure definition is a constraint on the stated type (and in this case, the type cannot be an abstract type). References are URLs that are relative to http://hl7.org/fhir/StructureDefinition e.g. "string" is a reference to http://hl7.org/fhir/StructureDefinition/string. Absolute URLs are only allowed in logical models. + + + + + An absolute URI that is the base structure from which this type is derived, either by specialization or constraint. + + + + + How the type relates to the baseDefinition. + + + + + A snapshot view is expressed in a standalone form that can be used and interpreted without considering the base StructureDefinition. + + + + + A differential view is expressed relative to the base StructureDefinition - a statement of differences that it applies. + + + + + + + + + A definition of a FHIR structure. This resource is used to describe the underlying resources, data types defined in FHIR, and also for describing extensions and constraints on resources and data types. + + + + + + + An Internal id that is used to identify this mapping set when specific mappings are made. + + + + + An absolute URI that identifies the specification that this mapping is expressed to. + + + + + A name for the specification that is being mapped to. + + + + + Comments about this mapping, including version notes, issues, scope limitations, and other important notes for usage. + + + + + + + + + A definition of a FHIR structure. This resource is used to describe the underlying resources, data types defined in FHIR, and also for describing extensions and constraints on resources and data types. + + + + + + + Defines how to interpret the expression that defines what the context of the extension is. + + + + + An expression that defines where an extension can be used in resources. + + + + + + + + + A definition of a FHIR structure. This resource is used to describe the underlying resources, data types defined in FHIR, and also for describing extensions and constraints on resources and data types. + + + + + + + Captures constraints on each element within the resource. + + + + + + + + + A definition of a FHIR structure. This resource is used to describe the underlying resources, data types defined in FHIR, and also for describing extensions and constraints on resources and data types. + + + + + + + Captures constraints on each element within the resource. + + + + + + + + + + + Primitive Data Type + + + + + Complex Data Type + + + + + Resource + + + + + Logical + + + + + + + Defines the type of structure that a definition is describing. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Specialization + + + + + Constraint + + + + + + + How a type relates to its baseDefinition. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + FHIRPath + + + + + Element ID + + + + + Extension URL + + + + + + + How an extension context is interpreted. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A Map of relationships between 2 structures that can be used to transform data. + + + + + A Map of relationships between 2 structures that can be used to transform data. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this structure map when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this structure map is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the structure map is stored on different servers. + + + + + A formal identifier that is used to identify this structure map when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the structure map when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the structure map 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. + + + + + A natural language name identifying the structure map. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the structure map. + + + + + The status of this structure map. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this structure map is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The date (and optionally time) when the structure map was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the structure map changes. + + + + + The name of the organization or individual that published the structure map. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the structure map from a consumer's perspective. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate structure map instances. + + + + + A legal or geographic region in which the structure map is intended to be used. + + + + + Explanation of why this structure map is needed and why it has been designed as it has. + + + + + A copyright statement relating to the structure map and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the structure map. + + + + + A structure definition used by this map. The structure definition may describe instances that are converted, or the instances that are produced. + + + + + Other maps used by this map (canonical URLs). + + + + + Organizes the mapping into manageable chunks for human review/ease of maintenance. + + + + + + + + + A Map of relationships between 2 structures that can be used to transform data. + + + + + + + The canonical reference to the structure. + + + + + How the referenced structure is used in this mapping. + + + + + The name used for this type in the map. + + + + + Documentation that describes how the structure is used in the mapping. + + + + + + + + + A Map of relationships between 2 structures that can be used to transform data. + + + + + + + A unique name for the group for the convenience of human readers. + + + + + Another group that this group adds rules to. + + + + + If this is the default rule set to apply for the source type or this combination of types. + + + + + Additional supporting documentation that explains the purpose of the group and the types of mappings within it. + + + + + A name assigned to an instance of data. The instance must be provided when the mapping is invoked. + + + + + Transform Rule from source to target. + + + + + + + + + A Map of relationships between 2 structures that can be used to transform data. + + + + + + + Name for this instance of data. + + + + + Type for this instance of data. + + + + + Mode for this instance of data. + + + + + Documentation for this instance of data. + + + + + + + + + A Map of relationships between 2 structures that can be used to transform data. + + + + + + + Name of the rule for internal references. + + + + + Source inputs to the mapping. + + + + + Content to create because of this mapping rule. + + + + + Rules contained in this rule. + + + + + Which other rules to apply in the context of this rule. + + + + + Documentation for this instance of data. + + + + + + + + + A Map of relationships between 2 structures that can be used to transform data. + + + + + + + Type or variable this rule applies to. + + + + + Specified minimum cardinality for the element. This is optional; if present, it acts an implicit check on the input content. + + + + + Specified maximum cardinality for the element - a number or a "*". This is optional; if present, it acts an implicit check on the input content (* just serves as documentation; it's the default value). + + + + + Specified type for the element. This works as a condition on the mapping - use for polymorphic elements. + + + + + A value to use if there is no existing value in the source object. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Optional field for this source. + + + + + How to handle the list mode for this element. + + + + + Named context for field, if a field is specified. + + + + + FHIRPath expression - must be true or the rule does not apply. + + + + + FHIRPath expression - must be true or the mapping engine throws an error instead of completing. + + + + + A FHIRPath expression which specifies a message to put in the transform log when content matching the source rule is found. + + + + + + + + + A Map of relationships between 2 structures that can be used to transform data. + + + + + + + Type or variable this rule applies to. + + + + + How to interpret the context. + + + + + Field to create in the context. + + + + + Named context for field, if desired, and a field is specified. + + + + + If field is a list, how to manage the list. + + + + + Internal rule reference for shared list items. + + + + + How the data is copied / created. + + + + + Parameters to the transform. + + + + + + + + + A Map of relationships between 2 structures that can be used to transform data. + + + + + + + Parameter value - variable or literal. + + + + + + + + + + + + + + A Map of relationships between 2 structures that can be used to transform data. + + + + + + + Name of a rule or group to apply. + + + + + Variable to pass to the rule or group. + + + + + + + + + + + Source Instance + + + + + Target Instance + + + + + + + Mode for this instance of data. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Type + + + + + Variable + + + + + + + How to interpret the context. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + First + + + + + Share + + + + + Last + + + + + Collate + + + + + + + If field is a list, how to manage the production. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + create + + + + + copy + + + + + truncate + + + + + escape + + + + + cast + + + + + append + + + + + translate + + + + + reference + + + + + dateOp + + + + + uuid + + + + + pointer + + + + + evaluate + + + + + cc + + + + + c + + + + + qty + + + + + id + + + + + cp + + + + + + + How data is copied/created. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + First + + + + + All but the first + + + + + Last + + + + + All but the last + + + + + Enforce only one + + + + + + + If field is a list, how to manage the source. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Not a Default + + + + + Default for Type Combination + + + + + Default for type + combination + + + + + + + If this is the default rule set to apply for the source type, or this combination of types. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Source Structure Definition + + + + + Queried Structure Definition + + + + + Target Structure Definition + + + + + Produced Structure Definition + + + + + + + How the referenced structure is used in this mapping. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + The subscription resource is used to define a push-based subscription from a server to another system. Once a subscription is registered with the server, the server checks every resource that is created or updated, and if the resource matches the given criteria, it sends a message on the defined "channel" so that another system can take an appropriate action. + + + + + The subscription resource is used to define a push-based subscription from a server to another system. Once a subscription is registered with the server, the server checks every resource that is created or updated, and if the resource matches the given criteria, it sends a message on the defined "channel" so that another system can take an appropriate action. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + The status of the subscription, which marks the server state for managing the subscription. + + + + + Contact details for a human to contact about the subscription. The primary use of this for system administrator troubleshooting. + + + + + The time for the server to turn the subscription off. + + + + + A description of why this subscription is defined. + + + + + The rules that the server should use to determine when to generate notifications for this subscription. + + + + + A record of the last error that occurred when the server processed a notification. + + + + + Details where to send notifications when resources are received that meet the criteria. + + + + + + + + + The subscription resource is used to define a push-based subscription from a server to another system. Once a subscription is registered with the server, the server checks every resource that is created or updated, and if the resource matches the given criteria, it sends a message on the defined "channel" so that another system can take an appropriate action. + + + + + + + The type of channel to send notifications on. + + + + + The url that describes the actual end-point to send messages to. + + + + + The mime type to send the payload in - either application/fhir+xml, or application/fhir+json. If the payload is not present, then there is no payload in the notification, just a notification. The mime type "text/plain" may also be used for Email and SMS subscriptions. + + + + + Additional headers / information to send as part of the notification. + + + + + + + + + + + Requested + + + + + Active + + + + + Error + + + + + Off + + + + + + + The status of a subscription. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Rest Hook + + + + + Websocket + + + + + Email + + + + + SMS + + + + + Message + + + + + + + The type of method used to execute a subscription. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A homogeneous material with a definite composition. + + + + + A homogeneous material with a definite composition. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Unique identifier for the substance. + + + + + A code to indicate if the substance is actively used. + + + + + A code that classifies the general type of substance. This is used for searching, sorting and display purposes. + + + + + A code (or set of codes) that identify this substance. + + + + + A description of the substance - its appearance, handling requirements, and other usage notes. + + + + + Substance may be used to describe a kind of substance, or a specific package/container of the substance: an instance. + + + + + A substance can be composed of other substances. + + + + + + + + + A homogeneous material with a definite composition. + + + + + + + Identifier associated with the package/container (usually a label affixed directly). + + + + + When the substance is no longer valid to use. For some substances, a single arbitrary date is used for expiry. + + + + + The amount of the substance. + + + + + + + + + A homogeneous material with a definite composition. + + + + + + + The amount of the ingredient in the substance - a concentration ratio. + + + + + Another substance that is a component of this substance. + + + + + + + + + + + + + Active + + + + + Inactive + + + + + Entered in Error + + + + + + + A code to indicate if the substance is actively used. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + The detailed description of a substance, typically at a level beyond what is used for prescribing. + + + + + The detailed description of a substance, typically at a level beyond what is used for prescribing. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifier by which this substance is known. + + + + + High level categorization, e.g. polymer or nucleic acid. + + + + + Status of substance within the catalogue e.g. approved. + + + + + If the substance applies to only human or veterinary use. + + + + + Textual description of the substance. + + + + + Supporting literature. + + + + + Textual comment about this record of a substance. + + + + + Moiety, for structural modifications. + + + + + General specifications for this substance, including how it is related to other substances. + + + + + General information detailing this substance. + + + + + Structural information. + + + + + Codes associated with the substance. + + + + + Names applicable to this substance. + + + + + The molecular weight or weight range (for proteins, polymers or nucleic acids). + + + + + A link between this substance and another, with details of the relationship. + + + + + Data items specific to nucleic acids. + + + + + Data items specific to polymers. + + + + + Data items specific to proteins. + + + + + Material or taxonomic/anatomical source for the substance. + + + + + + + + + The detailed description of a substance, typically at a level beyond what is used for prescribing. + + + + + + + Role that the moiety is playing. + + + + + Identifier by which this moiety substance is known. + + + + + Textual name for this moiety substance. + + + + + Stereochemistry type. + + + + + Optical activity type. + + + + + Molecular formula. + + + + + Quantitative value for this moiety. + + + + + + + + + + + The detailed description of a substance, typically at a level beyond what is used for prescribing. + + + + + + + A category for this property, e.g. Physical, Chemical, Enzymatic. + + + + + Property type e.g. viscosity, pH, isoelectric point. + + + + + Parameters that were used in the measurement of a property (e.g. for viscosity: measured at 20C with a pH of 7.1). + + + + + A substance upon which a defining property depends (e.g. for solubility: in water, in alcohol). + + + + + + + Quantitative value for this property. + + + + + + + + + + + The detailed description of a substance, typically at a level beyond what is used for prescribing. + + + + + + + Stereochemistry type. + + + + + Optical activity type. + + + + + Molecular formula. + + + + + Specified per moiety according to the Hill system, i.e. first C, then H, then alphabetical, each moiety separated by a dot. + + + + + Applicable for single substances that contain a radionuclide or a non-natural isotopic ratio. + + + + + The molecular weight or weight range (for proteins, polymers or nucleic acids). + + + + + Supporting literature. + + + + + Molecular structural representation. + + + + + + + + + The detailed description of a substance, typically at a level beyond what is used for prescribing. + + + + + + + Substance identifier for each non-natural or radioisotope. + + + + + Substance name for each non-natural or radioisotope. + + + + + The type of isotopic substitution present in a single substance. + + + + + Half life - for a non-natural nuclide. + + + + + The molecular weight or weight range (for proteins, polymers or nucleic acids). + + + + + + + + + The detailed description of a substance, typically at a level beyond what is used for prescribing. + + + + + + + The method by which the molecular weight was determined. + + + + + Type of molecular weight such as exact, average (also known as. number average), weight average. + + + + + Used to capture quantitative values for a variety of elements. If only limits are given, the arithmetic mean would be the average. If only a single definite value for a given element is given, it would be captured in this field. + + + + + + + + + The detailed description of a substance, typically at a level beyond what is used for prescribing. + + + + + + + The type of structure (e.g. Full, Partial, Representative). + + + + + The structural representation as text string in a format e.g. InChI, SMILES, MOLFILE, CDX. + + + + + An attached file with the structural representation. + + + + + + + + + The detailed description of a substance, typically at a level beyond what is used for prescribing. + + + + + + + The specific code. + + + + + Status of the code assignment. + + + + + The date at which the code status is changed as part of the terminology maintenance. + + + + + Any comment can be provided in this field, if necessary. + + + + + Supporting literature. + + + + + + + + + The detailed description of a substance, typically at a level beyond what is used for prescribing. + + + + + + + The actual name. + + + + + Name type. + + + + + The status of the name. + + + + + If this is the preferred name for this substance. + + + + + Language of the name. + + + + + The use context of this name for example if there is a different name a drug active ingredient as opposed to a food colour additive. + + + + + The jurisdiction where this name applies. + + + + + A synonym of this name. + + + + + A translation for this name. + + + + + Details of the official nature of this name. + + + + + Supporting literature. + + + + + + + + + The detailed description of a substance, typically at a level beyond what is used for prescribing. + + + + + + + Which authority uses this official name. + + + + + The status of the official name. + + + + + Date of official name change. + + + + + + + + + The detailed description of a substance, typically at a level beyond what is used for prescribing. + + + + + + + A pointer to another substance, as a resource or just a representational code. + + + + + + + For example "salt to parent", "active moiety", "starting material". + + + + + For example where an enzyme strongly bonds with a particular substance, this is a defining relationship for that enzyme, out of several possible substance relationships. + + + + + A numeric factor for the relationship, for instance to express that the salt of a substance has some percentage of the active substance in relation to some other. + + + + + + + + + For use when the numeric. + + + + + An operator for the amount, for example "average", "approximately", "less than". + + + + + Supporting literature. + + + + + + + + + Nucleic acids are defined by three distinct elements: the base, sugar and linkage. Individual substance/moiety IDs will be created for each of these elements. The nucleotide sequence will be always entered in the 5’-3’ direction. + + + + + Nucleic acids are defined by three distinct elements: the base, sugar and linkage. Individual substance/moiety IDs will be created for each of these elements. The nucleotide sequence will be always entered in the 5’-3’ direction. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + The type of the sequence shall be specified based on a controlled vocabulary. + + + + + The number of linear sequences of nucleotides linked through phosphodiester bonds shall be described. Subunits would be strands of nucleic acids that are tightly associated typically through Watson-Crick base pairing. NOTE: If not specified in the reference source, the assumption is that there is 1 subunit. + + + + + The area of hybridisation shall be described if applicable for double stranded RNA or DNA. The number associated with the subunit followed by the number associated to the residue shall be specified in increasing order. The underscore “” shall be used as separator as follows: “Subunitnumber Residue”. + + + + + (TBC). + + + + + Subunits are listed in order of decreasing length; sequences of the same length will be ordered by molecular weight; subunits that have identical sequences will be repeated multiple times. + + + + + + + + + Nucleic acids are defined by three distinct elements: the base, sugar and linkage. Individual substance/moiety IDs will be created for each of these elements. The nucleotide sequence will be always entered in the 5’-3’ direction. + + + + + + + Index of linear sequences of nucleic acids in order of decreasing length. Sequences of the same length will be ordered by molecular weight. Subunits that have identical sequences will be repeated and have sequential subscripts. + + + + + Actual nucleotide sequence notation from 5' to 3' end using standard single letter codes. In addition to the base sequence, sugar and type of phosphate or non-phosphate linkage should also be captured. + + + + + The length of the sequence shall be captured. + + + + + (TBC). + + + + + The nucleotide present at the 5’ terminal shall be specified based on a controlled vocabulary. Since the sequence is represented from the 5' to the 3' end, the 5’ prime nucleotide is the letter at the first position in the sequence. A separate representation would be redundant. + + + + + The nucleotide present at the 3’ terminal shall be specified based on a controlled vocabulary. Since the sequence is represented from the 5' to the 3' end, the 5’ prime nucleotide is the letter at the last position in the sequence. A separate representation would be redundant. + + + + + The linkages between sugar residues will also be captured. + + + + + 5.3.6.8.1 Sugar ID (Mandatory). + + + + + + + + + Nucleic acids are defined by three distinct elements: the base, sugar and linkage. Individual substance/moiety IDs will be created for each of these elements. The nucleotide sequence will be always entered in the 5’-3’ direction. + + + + + + + The entity that links the sugar residues together should also be captured for nearly all naturally occurring nucleic acid the linkage is a phosphate group. For many synthetic oligonucleotides phosphorothioate linkages are often seen. Linkage connectivity is assumed to be 3’-5’. If the linkage is either 3’-3’ or 5’-5’ this should be specified. + + + + + Each linkage will be registered as a fragment and have an ID. + + + + + Each linkage will be registered as a fragment and have at least one name. A single name shall be assigned to each linkage. + + + + + Residues shall be captured as described in 5.3.6.8.3. + + + + + + + + + Nucleic acids are defined by three distinct elements: the base, sugar and linkage. Individual substance/moiety IDs will be created for each of these elements. The nucleotide sequence will be always entered in the 5’-3’ direction. + + + + + + + The Substance ID of the sugar or sugar-like component that make up the nucleotide. + + + + + The name of the sugar or sugar-like component that make up the nucleotide. + + + + + The residues that contain a given sugar will be captured. The order of given residues will be captured in the 5‘-3‘direction consistent with the base sequences listed above. + + + + + + + + + Todo. + + + + + Todo. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + + + + + Todo. + + + + + + + Todo. + + + + + Todo. + + + + + + + + + Todo. + + + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + + + + + Todo. + + + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + + + + + Todo. + + + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + + + + + Todo. + + + + + + + Todo. + + + + + Todo. + + + + + + + + + Todo. + + + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + + + + + A SubstanceProtein is defined as a single unit of a linear amino acid sequence, or a combination of subunits that are either covalently linked or have a defined invariant stoichiometric relationship. This includes all synthetic, recombinant and purified SubstanceProteins of defined sequence, whether the use is therapeutic or prophylactic. This set of elements will be used to describe albumins, coagulation factors, cytokines, growth factors, peptide/SubstanceProtein hormones, enzymes, toxins, toxoids, recombinant vaccines, and immunomodulators. + + + + + A SubstanceProtein is defined as a single unit of a linear amino acid sequence, or a combination of subunits that are either covalently linked or have a defined invariant stoichiometric relationship. This includes all synthetic, recombinant and purified SubstanceProteins of defined sequence, whether the use is therapeutic or prophylactic. This set of elements will be used to describe albumins, coagulation factors, cytokines, growth factors, peptide/SubstanceProtein hormones, enzymes, toxins, toxoids, recombinant vaccines, and immunomodulators. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + The SubstanceProtein descriptive elements will only be used when a complete or partial amino acid sequence is available or derivable from a nucleic acid sequence. + + + + + Number of linear sequences of amino acids linked through peptide bonds. The number of subunits constituting the SubstanceProtein shall be described. It is possible that the number of subunits can be variable. + + + + + The disulphide bond between two cysteine residues either on the same subunit or on two different subunits shall be described. The position of the disulfide bonds in the SubstanceProtein shall be listed in increasing order of subunit number and position within subunit followed by the abbreviation of the amino acids involved. The disulfide linkage positions shall actually contain the amino acid Cysteine at the respective positions. + + + + + This subclause refers to the description of each subunit constituting the SubstanceProtein. A subunit is a linear sequence of amino acids linked through peptide bonds. The Subunit information shall be provided when the finished SubstanceProtein is a complex of multiple sequences; subunits are not used to delineate domains within a single sequence. Subunits are listed in order of decreasing length; sequences of the same length will be ordered by decreasing molecular weight; subunits that have identical sequences will be repeated multiple times. + + + + + + + + + A SubstanceProtein is defined as a single unit of a linear amino acid sequence, or a combination of subunits that are either covalently linked or have a defined invariant stoichiometric relationship. This includes all synthetic, recombinant and purified SubstanceProteins of defined sequence, whether the use is therapeutic or prophylactic. This set of elements will be used to describe albumins, coagulation factors, cytokines, growth factors, peptide/SubstanceProtein hormones, enzymes, toxins, toxoids, recombinant vaccines, and immunomodulators. + + + + + + + Index of primary sequences of amino acids linked through peptide bonds in order of decreasing length. Sequences of the same length will be ordered by molecular weight. Subunits that have identical sequences will be repeated and have sequential subscripts. + + + + + The sequence information shall be provided enumerating the amino acids from N- to C-terminal end using standard single-letter amino acid codes. Uppercase shall be used for L-amino acids and lowercase for D-amino acids. Transcribed SubstanceProteins will always be described using the translated sequence; for synthetic peptide containing amino acids that are not represented with a single letter code an X should be used within the sequence. The modified amino acids will be distinguished by their position in the sequence. + + + + + Length of linear sequences of amino acids contained in the subunit. + + + + + The sequence information shall be provided enumerating the amino acids from N- to C-terminal end using standard single-letter amino acid codes. Uppercase shall be used for L-amino acids and lowercase for D-amino acids. Transcribed SubstanceProteins will always be described using the translated sequence; for synthetic peptide containing amino acids that are not represented with a single letter code an X should be used within the sequence. The modified amino acids will be distinguished by their position in the sequence. + + + + + Unique identifier for molecular fragment modification based on the ISO 11238 Substance ID. + + + + + The name of the fragment modified at the N-terminal of the SubstanceProtein shall be specified. + + + + + Unique identifier for molecular fragment modification based on the ISO 11238 Substance ID. + + + + + The modification at the C-terminal shall be specified. + + + + + + + + + Todo. + + + + + Todo. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + + + + + Todo. + + + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + + + + + Todo. + + + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + + + + + Todo. + + + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + + + + + Todo. + + + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + Todo. + + + + + + + + Todo. + + + + + Todo. + + + + + + + + + Source material shall capture information on the taxonomic and anatomical origins as well as the fraction of a material that can result in or can be modified to form a substance. This set of data elements shall be used to define polymer substances isolated from biological matrices. Taxonomic and anatomical origins shall be described using a controlled vocabulary as required. This information is captured for naturally derived polymers ( . starch) and structurally diverse substances. For Organisms belonging to the Kingdom Plantae the Substance level defines the fresh material of a single species or infraspecies, the Herbal Drug and the Herbal preparation. For Herbal preparations, the fraction information will be captured at the Substance information level and additional information for herbal extracts will be captured at the Specified Substance Group 1 information level. See for further explanation the Substance Class: Structurally Diverse and the herbal annex. + + + + + Source material shall capture information on the taxonomic and anatomical origins as well as the fraction of a material that can result in or can be modified to form a substance. This set of data elements shall be used to define polymer substances isolated from biological matrices. Taxonomic and anatomical origins shall be described using a controlled vocabulary as required. This information is captured for naturally derived polymers ( . starch) and structurally diverse substances. For Organisms belonging to the Kingdom Plantae the Substance level defines the fresh material of a single species or infraspecies, the Herbal Drug and the Herbal preparation. For Herbal preparations, the fraction information will be captured at the Substance information level and additional information for herbal extracts will be captured at the Specified Substance Group 1 information level. See for further explanation the Substance Class: Structurally Diverse and the herbal annex. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + General high level classification of the source material specific to the origin of the material. + + + + + The type of the source material shall be specified based on a controlled vocabulary. For vaccines, this subclause refers to the class of infectious agent. + + + + + The state of the source material when extracted. + + + + + The unique identifier associated with the source material parent organism shall be specified. + + + + + The organism accepted Scientific name shall be provided based on the organism taxonomy. + + + + + The parent of the herbal drug Ginkgo biloba, Leaf is the substance ID of the substance (fresh) of Ginkgo biloba L. or Ginkgo biloba L. (Whole plant). + + + + + The parent substance of the Herbal Drug, or Herbal preparation. + + + + + The country where the plant material is harvested or the countries where the plasma is sourced from as laid down in accordance with the Plasma Master File. For “Plasma-derived substances” the attribute country of origin provides information about the countries used for the manufacturing of the Cryopoor plama or Crioprecipitate. + + + + + The place/region where the plant is harvested or the places/regions where the animal source material has its habitat. + + + + + Stage of life for animals, plants, insects and microorganisms. This information shall be provided only when the substance is significantly different in these stages (e.g. foetal bovine serum). + + + + + Many complex materials are fractions of parts of plants, animals, or minerals. Fraction elements are often necessary to define both Substances and Specified Group 1 Substances. For substances derived from Plants, fraction information will be captured at the Substance information level ( . Oils, Juices and Exudates). Additional information for Extracts, such as extraction solvent composition, will be captured at the Specified Substance Group 1 information level. For plasma-derived products fraction information will be captured at the Substance and the Specified Substance Group 1 levels. + + + + + This subclause describes the organism which the substance is derived from. For vaccines, the parent organism shall be specified based on these subclause elements. As an example, full taxonomy will be described for the Substance Name: ., Leaf. + + + + + To do. + + + + + + + + + Source material shall capture information on the taxonomic and anatomical origins as well as the fraction of a material that can result in or can be modified to form a substance. This set of data elements shall be used to define polymer substances isolated from biological matrices. Taxonomic and anatomical origins shall be described using a controlled vocabulary as required. This information is captured for naturally derived polymers ( . starch) and structurally diverse substances. For Organisms belonging to the Kingdom Plantae the Substance level defines the fresh material of a single species or infraspecies, the Herbal Drug and the Herbal preparation. For Herbal preparations, the fraction information will be captured at the Substance information level and additional information for herbal extracts will be captured at the Specified Substance Group 1 information level. See for further explanation the Substance Class: Structurally Diverse and the herbal annex. + + + + + + + This element is capturing information about the fraction of a plant part, or human plasma for fractionation. + + + + + The specific type of the material constituting the component. For Herbal preparations the particulars of the extracts (liquid/dry) is described in Specified Substance Group 1. + + + + + + + + + Source material shall capture information on the taxonomic and anatomical origins as well as the fraction of a material that can result in or can be modified to form a substance. This set of data elements shall be used to define polymer substances isolated from biological matrices. Taxonomic and anatomical origins shall be described using a controlled vocabulary as required. This information is captured for naturally derived polymers ( . starch) and structurally diverse substances. For Organisms belonging to the Kingdom Plantae the Substance level defines the fresh material of a single species or infraspecies, the Herbal Drug and the Herbal preparation. For Herbal preparations, the fraction information will be captured at the Substance information level and additional information for herbal extracts will be captured at the Specified Substance Group 1 information level. See for further explanation the Substance Class: Structurally Diverse and the herbal annex. + + + + + + + The family of an organism shall be specified. + + + + + The genus of an organism shall be specified; refers to the Latin epithet of the genus element of the plant/animal scientific name; it is present in names for genera, species and infraspecies. + + + + + The species of an organism shall be specified; refers to the Latin epithet of the species of the plant/animal; it is present in names for species and infraspecies. + + + + + The Intraspecific type of an organism shall be specified. + + + + + The intraspecific description of an organism shall be specified based on a controlled vocabulary. For Influenza Vaccine, the intraspecific description shall contain the syntax of the antigen in line with the WHO convention. + + + + + 4.9.13.6.1 Author type (Conditional). + + + + + 4.9.13.8.1 Hybrid species maternal organism ID (Optional). + + + + + 4.9.13.7.1 Kingdom (Conditional). + + + + + + + + + Source material shall capture information on the taxonomic and anatomical origins as well as the fraction of a material that can result in or can be modified to form a substance. This set of data elements shall be used to define polymer substances isolated from biological matrices. Taxonomic and anatomical origins shall be described using a controlled vocabulary as required. This information is captured for naturally derived polymers ( . starch) and structurally diverse substances. For Organisms belonging to the Kingdom Plantae the Substance level defines the fresh material of a single species or infraspecies, the Herbal Drug and the Herbal preparation. For Herbal preparations, the fraction information will be captured at the Substance information level and additional information for herbal extracts will be captured at the Specified Substance Group 1 information level. See for further explanation the Substance Class: Structurally Diverse and the herbal annex. + + + + + + + The type of author of an organism species shall be specified. The parenthetical author of an organism species refers to the first author who published the plant/animal name (of any rank). The primary author of an organism species refers to the first author(s), who validly published the plant/animal name. + + + + + The author of an organism species shall be specified. The author year of an organism shall also be specified when applicable; refers to the year in which the first author(s) published the infraspecific plant/animal name (of any rank). + + + + + + + + + Source material shall capture information on the taxonomic and anatomical origins as well as the fraction of a material that can result in or can be modified to form a substance. This set of data elements shall be used to define polymer substances isolated from biological matrices. Taxonomic and anatomical origins shall be described using a controlled vocabulary as required. This information is captured for naturally derived polymers ( . starch) and structurally diverse substances. For Organisms belonging to the Kingdom Plantae the Substance level defines the fresh material of a single species or infraspecies, the Herbal Drug and the Herbal preparation. For Herbal preparations, the fraction information will be captured at the Substance information level and additional information for herbal extracts will be captured at the Specified Substance Group 1 information level. See for further explanation the Substance Class: Structurally Diverse and the herbal annex. + + + + + + + The identifier of the maternal species constituting the hybrid organism shall be specified based on a controlled vocabulary. For plants, the parents aren’t always known, and it is unlikely that it will be known which is maternal and which is paternal. + + + + + The name of the maternal species constituting the hybrid organism shall be specified. For plants, the parents aren’t always known, and it is unlikely that it will be known which is maternal and which is paternal. + + + + + The identifier of the paternal species constituting the hybrid organism shall be specified based on a controlled vocabulary. + + + + + The name of the paternal species constituting the hybrid organism shall be specified. + + + + + The hybrid type of an organism shall be specified. + + + + + + + + + Source material shall capture information on the taxonomic and anatomical origins as well as the fraction of a material that can result in or can be modified to form a substance. This set of data elements shall be used to define polymer substances isolated from biological matrices. Taxonomic and anatomical origins shall be described using a controlled vocabulary as required. This information is captured for naturally derived polymers ( . starch) and structurally diverse substances. For Organisms belonging to the Kingdom Plantae the Substance level defines the fresh material of a single species or infraspecies, the Herbal Drug and the Herbal preparation. For Herbal preparations, the fraction information will be captured at the Substance information level and additional information for herbal extracts will be captured at the Specified Substance Group 1 information level. See for further explanation the Substance Class: Structurally Diverse and the herbal annex. + + + + + + + The kingdom of an organism shall be specified. + + + + + The phylum of an organism shall be specified. + + + + + The class of an organism shall be specified. + + + + + The order of an organism shall be specified,. + + + + + + + + + Source material shall capture information on the taxonomic and anatomical origins as well as the fraction of a material that can result in or can be modified to form a substance. This set of data elements shall be used to define polymer substances isolated from biological matrices. Taxonomic and anatomical origins shall be described using a controlled vocabulary as required. This information is captured for naturally derived polymers ( . starch) and structurally diverse substances. For Organisms belonging to the Kingdom Plantae the Substance level defines the fresh material of a single species or infraspecies, the Herbal Drug and the Herbal preparation. For Herbal preparations, the fraction information will be captured at the Substance information level and additional information for herbal extracts will be captured at the Specified Substance Group 1 information level. See for further explanation the Substance Class: Structurally Diverse and the herbal annex. + + + + + + + Entity of anatomical origin of source material within an organism. + + + + + The detailed anatomic location when the part can be extracted from different anatomical locations of the organism. Multiple alternative locations may apply. + + + + + + + + + Record of delivery of what is supplied. + + + + + Record of delivery of what is supplied. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifier for the supply delivery event that is used to identify it across multiple disparate systems. + + + + + A plan, proposal or order that is fulfilled in whole or in part by this event. + + + + + A larger event of which this particular event is a component or step. + + + + + A code specifying the state of the dispense event. + + + + + A link to a resource representing the person whom the delivered item is for. + + + + + Indicates the type of dispensing event that is performed. Examples include: Trial Fill, Completion of Trial, Partial Fill, Emergency Fill, Samples, etc. + + + + + The item that is being delivered or has been supplied. + + + + + The date or time(s) the activity occurred. + + + + + + + + The individual responsible for dispensing the medication, supplier or device. + + + + + Identification of the facility/location where the Supply was shipped to, as part of the dispense event. + + + + + Identifies the person who picked up the Supply. + + + + + + + + + Record of delivery of what is supplied. + + + + + + + The amount of supply that has been dispensed. Includes unit of measure. + + + + + Identifies the medication, substance or device being dispensed. This is either a link to a resource representing the details of the item or a code that identifies the item from a known list. + + + + + + + + + + + + + In Progress + + + + + Delivered + + + + + Abandoned + + + + + Entered In Error + + + + + + + Status of the supply delivery. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A record of a request for a medication, substance or device used in the healthcare setting. + + + + + A record of a request for a medication, substance or device used in the healthcare setting. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Business identifiers assigned to this SupplyRequest by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server. + + + + + Status of the supply request. + + + + + Category of supply, e.g. central, non-stock, etc. This is used to support work flows associated with the supply process. + + + + + Indicates how quickly this SupplyRequest should be addressed with respect to other requests. + + + + + The item that is requested to be supplied. This is either a link to a resource representing the details of the item or a code that identifies the item from a known list. + + + + + + + The amount that is being ordered of the indicated item. + + + + + Specific parameters for the ordered item. For example, the size of the indicated item. + + + + + When the request should be fulfilled. + + + + + + + + When the request was made. + + + + + The device, practitioner, etc. who initiated the request. + + + + + Who is intended to fulfill the request. + + + + + The reason why the supply item was requested. + + + + + The reason why the supply item was requested. + + + + + Where the supply is expected to come from. + + + + + Where the supply is destined to go. + + + + + + + + + A record of a request for a medication, substance or device used in the healthcare setting. + + + + + + + A code or string that identifies the device detail being asserted. + + + + + The value of the device detail. + + + + + + + + + + + + + + + Draft + + + + + Active + + + + + Suspended + + + + + Cancelled + + + + + Completed + + + + + Entered in Error + + + + + Unknown + + + + + + + Status of the supply request. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A task to be performed. + + + + + A task to be performed. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + The business identifier for this task. + + + + + The URL pointing to a *FHIR*-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Task. + + + + + The URL pointing to an *externally* maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Task. + + + + + BasedOn refers to a higher-level authorization that triggered the creation of the task. It references a "request" resource such as a ServiceRequest, MedicationRequest, ServiceRequest, CarePlan, etc. which is distinct from the "request" resource the task is seeking to fulfill. This latter resource is referenced by FocusOn. For example, based on a ServiceRequest (= BasedOn), a task is created to fulfill a procedureRequest ( = FocusOn ) to collect a specimen from a patient. + + + + + An identifier that links together multiple tasks and other requests that were created in the same context. + + + + + Task that this particular task is part of. + + + + + The current status of the task. + + + + + An explanation as to why this task is held, failed, was refused, etc. + + + + + Contains business-specific nuances of the business state. + + + + + Indicates the "level" of actionability associated with the Task, i.e. i+R[9]Cs this a proposed task, a planned task, an actionable task, etc. + + + + + Indicates how quickly the Task should be addressed with respect to other requests. + + + + + A name or code (or both) briefly describing what the task involves. + + + + + A free-text description of what is to be performed. + + + + + The request being actioned or the resource being manipulated by this task. + + + + + The entity who benefits from the performance of the service specified in the task (e.g., the patient). + + + + + The healthcare event (e.g. a patient and healthcare provider interaction) during which this task was created. + + + + + Identifies the time action was first taken against the task (start) and/or the time final action was taken against the task prior to marking it as completed (end). + + + + + The date and time this task was created. + + + + + The date and time of last modification to this task. + + + + + The creator of the task. + + + + + The kind of participant that should perform the task. + + + + + Individual organization or Device currently responsible for task execution. + + + + + Principal physical location where the this task is performed. + + + + + A description or code indicating why this task needs to be performed. + + + + + A resource reference indicating why this task needs to be performed. + + + + + Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be relevant to the Task. + + + + + Free-text information captured about the task as it progresses. + + + + + Links to Provenance records for past versions of this Task that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the task. + + + + + 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. + + + + + Additional information that may be needed in the execution of the task. + + + + + Outputs produced by the Task. + + + + + + + + + A task to be performed. + + + + + + + Indicates the number of times the requested action should occur. + + + + + Over what time-period is fulfillment sought. + + + + + For requests that are targeted to more than on potential recipient/target, for whom is fulfillment sought? + + + + + + + + + A task to be performed. + + + + + + + A code or description indicating how the input is intended to be used as part of the task execution. + + + + + The value of the input parameter as a basic type. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + A task to be performed. + + + + + + + The name of the Output parameter. + + + + + The value of the Output parameter as a basic type. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Draft + + + + + Requested + + + + + Received + + + + + Accepted + + + + + Rejected + + + + + Ready + + + + + Cancelled + + + + + In Progress + + + + + On Hold + + + + + Failed + + + + + Completed + + + + + Entered in Error + + + + + + + The current status of the task. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Unknown + + + + + Proposal + + + + + Plan + + + + + Order + + + + + Original Order + + + + + Reflex Order + + + + + Filler Order + + + + + Instance Order + + + + + Option + + + + + + + Distinguishes whether the task is a proposal, plan or full order. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this terminology capabilities when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this terminology capabilities is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the terminology capabilities is stored on different servers. + + + + + The identifier that is used to identify this version of the terminology capabilities when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the terminology capabilities 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. + + + + + A natural language name identifying the terminology capabilities. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the terminology capabilities. + + + + + The status of this terminology capabilities. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this terminology capabilities is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The date (and optionally time) when the terminology capabilities was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the terminology capabilities changes. + + + + + The name of the organization or individual that published the terminology capabilities. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the terminology capabilities from a consumer's perspective. Typically, this is used when the capability statement describes a desired rather than an actual solution, for example as a formal expression of requirements as part of an RFP. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate terminology capabilities instances. + + + + + A legal or geographic region in which the terminology capabilities is intended to be used. + + + + + Explanation of why this terminology capabilities is needed and why it has been designed as it has. + + + + + A copyright statement relating to the terminology capabilities and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the terminology capabilities. + + + + + The way that this statement is intended to be used, to describe an actual running instance of software, a particular product (kind, not instance of software) or a class of implementation (e.g. a desired purchase). + + + + + Software that is covered by this terminology capability statement. It is used when the statement describes the capabilities of a particular software version, independent of an installation. + + + + + Identifies a specific implementation instance that is described by the terminology capability statement - i.e. a particular installation, rather than the capabilities of a software program. + + + + + Whether the server supports lockedDate. + + + + + Identifies a code system that is supported by the server. If there is a no code system URL, then this declares the general assumptions a client can make about support for any CodeSystem resource. + + + + + Information about the [ValueSet/$expand](valueset-operation-expand.html) operation. + + + + + The degree to which the server supports the code search parameter on ValueSet, if it is supported. + + + + + Information about the [ValueSet/$validate-code](valueset-operation-validate-code.html) operation. + + + + + Information about the [ConceptMap/$translate](conceptmap-operation-translate.html) operation. + + + + + Whether the $closure operation is supported. + + + + + + + + + A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + Name the software is known by. + + + + + The version identifier for the software covered by this statement. + + + + + + + + + A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + Information about the specific installation that this terminology capability statement relates to. + + + + + An absolute base URL for the implementation. + + + + + + + + + A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + URI for the Code System. + + + + + For the code system, a list of versions that are supported by the server. + + + + + True if subsumption is supported for this version of the code system. + + + + + + + + + A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + For version-less code systems, there should be a single version with no identifier. + + + + + If this is the default version for this code system. + + + + + If the compositional grammar defined by the code system is supported. + + + + + Language Displays supported. + + + + + Filter Properties supported. + + + + + Properties supported for $lookup. + + + + + + + + + A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + Code of the property supported. + + + + + Operations supported for the property. + + + + + + + + + A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + Whether the server can return nested value sets. + + + + + Whether the server supports paging on expansion. + + + + + Allow request for incomplete expansions? + + + + + Supported expansion parameter. + + + + + Documentation about text searching works. + + + + + + + + + A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + Expansion Parameter name. + + + + + Description of support for parameter. + + + + + + + + + A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + Whether translations are validated. + + + + + + + + + A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + Whether the client must identify the map. + + + + + + + + + A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. + + + + + + + If cross-system closure is supported. + + + + + + + + + + + Explicit Codes + + + + + Implicit Codes + + + + + + + The degree to which the server supports the code search parameter on ValueSet, if it is supported. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A summary of information based on the results of executing a TestScript. + + + + + A summary of information based on the results of executing a TestScript. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + Identifier for the TestScript assigned for external purposes outside the context of FHIR. + + + + + A free text natural language name identifying the executed TestScript. + + + + + The current state of this test report. + + + + + Ideally this is an absolute URL that is used to identify the version-specific TestScript that was executed, matching the `TestScript.url`. + + + + + The overall result from the execution of the TestScript. + + + + + The final score (percentage of tests passed) resulting from the execution of the TestScript. + + + + + Name of the tester producing this report (Organization or individual). + + + + + When the TestScript was executed and this TestReport was generated. + + + + + A participant in the test execution, either the execution engine, a client, or a server. + + + + + The results of the series of required setup operations before the tests were executed. + + + + + A test executed from the test script. + + + + + The results of the series of operations required to clean up after all the tests were executed (successfully or otherwise). + + + + + + + + + A summary of information based on the results of executing a TestScript. + + + + + + + The type of participant. + + + + + The uri of the participant. An absolute URL is preferred. + + + + + The display name of the participant. + + + + + + + + + A summary of information based on the results of executing a TestScript. + + + + + + + Action would contain either an operation or an assertion. + + + + + + + + + A summary of information based on the results of executing a TestScript. + + + + + + + The operation performed. + + + + + The results of the assertion performed on the previous operations. + + + + + + + + + A summary of information based on the results of executing a TestScript. + + + + + + + The result of this operation. + + + + + An explanatory message associated with the result. + + + + + A link to further details on the result. + + + + + + + + + A summary of information based on the results of executing a TestScript. + + + + + + + The result of this assertion. + + + + + An explanatory message associated with the result. + + + + + A link to further details on the result. + + + + + + + + + A summary of information based on the results of executing a TestScript. + + + + + + + The name of this test used for tracking/logging purposes by test engines. + + + + + A short description of the test used by test engines for tracking and reporting purposes. + + + + + Action would contain either an operation or an assertion. + + + + + + + + + A summary of information based on the results of executing a TestScript. + + + + + + + An operation would involve a REST request to a server. + + + + + The results of the assertion performed on the previous operations. + + + + + + + + + A summary of information based on the results of executing a TestScript. + + + + + + + The teardown action will only contain an operation. + + + + + + + + + A summary of information based on the results of executing a TestScript. + + + + + + + An operation would involve a REST request to a server. + + + + + + + + + + + Completed + + + + + In Progress + + + + + Waiting + + + + + Stopped + + + + + Entered In Error + + + + + + + The current status of the test report. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Pass + + + + + Skip + + + + + Fail + + + + + Warning + + + + + Error + + + + + + + The results of executing an action. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Test Engine + + + + + Client + + + + + Server + + + + + + + The type of participant. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Pass + + + + + Fail + + + + + Pending + + + + + + + The reported execution result. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this test script when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this test script is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the test script is stored on different servers. + + + + + A formal identifier that is used to identify this test script when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the test script when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the test script 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. + + + + + A natural language name identifying the test script. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the test script. + + + + + The status of this test script. Enables tracking the life-cycle of the content. + + + + + A Boolean value to indicate that this test script is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The date (and optionally time) when the test script was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the test script changes. + + + + + The name of the organization or individual that published the test script. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the test script from a consumer's perspective. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate test script instances. + + + + + A legal or geographic region in which the test script is intended to be used. + + + + + Explanation of why this test script is needed and why it has been designed as it has. + + + + + A copyright statement relating to the test script and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the test script. + + + + + An abstract server used in operations within this test script in the origin element. + + + + + An abstract server used in operations within this test script in the destination element. + + + + + The required capability must exist and are assumed to function correctly on the FHIR server being tested. + + + + + Fixture in the test script - by reference (uri). All fixtures are required for the test script to execute. + + + + + Reference to the profile to be used for validation. + + + + + Variable is set based either on element value in response body or on header field value in the response headers. + + + + + A series of required setup operations before tests are executed. + + + + + A test in this script. + + + + + A series of operations required to clean up after all the tests are executed (successfully or otherwise). + + + + + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + + + + + + + Abstract name given to an origin server in this test script. The name is provided as a number starting at 1. + + + + + The type of origin profile the test system supports. + + + + + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + + + + + + + Abstract name given to a destination server in this test script. The name is provided as a number starting at 1. + + + + + The type of destination profile the test system supports. + + + + + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + + + + + + + A link to the FHIR specification that this test is covering. + + + + + Capabilities that must exist and are assumed to function correctly on the FHIR server being tested. + + + + + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + + + + + + + URL to a particular requirement or feature within the FHIR specification. + + + + + Short description of the link. + + + + + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + + + + + + + Whether or not the test execution will require the given capabilities of the server in order for this test script to execute. + + + + + Whether or not the test execution will validate the given capabilities of the server in order for this test script to execute. + + + + + Description of the capabilities that this test script is requiring the server to support. + + + + + Which origin server these requirements apply to. + + + + + Which server these requirements apply to. + + + + + Links to the FHIR specification that describes this interaction and the resources involved in more detail. + + + + + Minimum capabilities required of server for test script to execute successfully. If server does not meet at a minimum the referenced capability statement, then all tests in this script are skipped. + + + + + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + + + + + + + Whether or not to implicitly create the fixture during setup. If true, the fixture is automatically created on each server being tested during setup, therefore no create operation is required for this fixture in the TestScript.setup section. + + + + + Whether or not to implicitly delete the fixture during teardown. If true, the fixture is automatically deleted on each server being tested during teardown, therefore no delete operation is required for this fixture in the TestScript.teardown section. + + + + + Reference to the resource (containing the contents of the resource needed for operations). + + + + + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + + + + + + + Descriptive name for this variable. + + + + + A default, hard-coded, or user-defined value for this variable. + + + + + A free text natural language description of the variable and its purpose. + + + + + The FHIRPath expression to evaluate against the fixture body. When variables are defined, only one of either expression, headerField or path must be specified. + + + + + Will be used to grab the HTTP header field value from the headers that sourceId is pointing to. + + + + + Displayable text string with hint help information to the user when entering a default value. + + + + + XPath or JSONPath to evaluate against the fixture body. When variables are defined, only one of either expression, headerField or path must be specified. + + + + + Fixture to evaluate the XPath/JSONPath expression or the headerField against within this variable. + + + + + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + + + + + + + Action would contain either an operation or an assertion. + + + + + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + + + + + + + The operation to perform. + + + + + Evaluates the results of previous operations to determine if the server under test behaves appropriately. + + + + + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + + + + + + + Server interaction or operation type. + + + + + The type of the resource. See http://build.fhir.org/resourcelist.html. + + + + + The label would be used for tracking/logging purposes by test engines. + + + + + The description would be used by test engines for tracking and reporting purposes. + + + + + The mime-type to use for RESTful operation in the 'Accept' header. + + + + + The mime-type to use for RESTful operation in the 'Content-Type' header. + + + + + The server where the request message is destined for. Must be one of the server numbers listed in TestScript.destination section. + + + + + Whether or not to implicitly send the request url in encoded format. The default is true to match the standard RESTful client behavior. Set to false when communicating with a server that does not support encoded url paths. + + + + + The HTTP method the test engine MUST use for this operation regardless of any other operation details. + + + + + The server where the request message originates from. Must be one of the server numbers listed in TestScript.origin section. + + + + + Path plus parameters after [type]. Used to set parts of the request URL explicitly. + + + + + Header elements would be used to set HTTP headers. + + + + + The fixture id (maybe new) to map to the request. + + + + + The fixture id (maybe new) to map to the response. + + + + + The id of the fixture used as the body of a PUT or POST request. + + + + + Id of fixture used for extracting the [id], [type], and [vid] for GET requests. + + + + + Complete request URL. + + + + + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + + + + + + + The HTTP header field e.g. "Accept". + + + + + The value of the header e.g. "application/fhir+xml". + + + + + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + + + + + + + The label would be used for tracking/logging purposes by test engines. + + + + + The description would be used by test engines for tracking and reporting purposes. + + + + + The direction to use for the assertion. + + + + + Id of the source fixture used as the contents to be evaluated by either the "source/expression" or "sourceId/path" definition. + + + + + The FHIRPath expression to evaluate against the source fixture. When compareToSourceId is defined, either compareToSourceExpression or compareToSourcePath must be defined, but not both. + + + + + XPath or JSONPath expression to evaluate against the source fixture. When compareToSourceId is defined, either compareToSourceExpression or compareToSourcePath must be defined, but not both. + + + + + The mime-type contents to compare against the request or response message 'Content-Type' header. + + + + + The FHIRPath expression to be evaluated against the request or response message contents - HTTP headers and payload. + + + + + The HTTP header field name e.g. 'Location'. + + + + + The ID of a fixture. Asserts that the response contains at a minimum the fixture specified by minimumId. + + + + + Whether or not the test execution performs validation on the bundle navigation links. + + + + + The operator type defines the conditional behavior of the assert. If not defined, the default is equals. + + + + + The XPath or JSONPath expression to be evaluated against the fixture representing the response received from server. + + + + + The request method or HTTP operation code to compare against that used by the client system under test. + + + + + The value to use in a comparison against the request URL path string. + + + + + The type of the resource. See http://build.fhir.org/resourcelist.html. + + + + + okay | created | noContent | notModified | bad | forbidden | notFound | methodNotAllowed | conflict | gone | preconditionFailed | unprocessable. + + + + + The value of the HTTP response code to be tested. + + + + + Fixture to evaluate the XPath/JSONPath expression or the headerField against. + + + + + The ID of the Profile to validate against. + + + + + The value to compare to. + + + + + Whether or not the test execution will produce a warning only on error for this assert. + + + + + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + + + + + + + The name of this test used for tracking/logging purposes by test engines. + + + + + A short description of the test used by test engines for tracking and reporting purposes. + + + + + Action would contain either an operation or an assertion. + + + + + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + + + + + + + An operation would involve a REST request to a server. + + + + + Evaluates the results of previous operations to determine if the server under test behaves appropriately. + + + + + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + + + + + + + The teardown action will only contain an operation. + + + + + + + + + A structured set of tests against a FHIR server or client implementation to determine compliance against the FHIR specification. + + + + + + + An operation would involve a REST request to a server. + + + + + + + + + + + response + + + + + request + + + + + + + The type of direction to use for assertion. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + equals + + + + + notEquals + + + + + in + + + + + notIn + + + + + greaterThan + + + + + lessThan + + + + + empty + + + + + notEmpty + + + + + contains + + + + + notContains + + + + + evaluate + + + + + + + The type of operator to use for assertion. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + okay + + + + + created + + + + + noContent + + + + + notModified + + + + + bad + + + + + forbidden + + + + + notFound + + + + + methodNotAllowed + + + + + conflict + + + + + gone + + + + + preconditionFailed + + + + + unprocessable + + + + + + + The type of response code to use for assertion. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + DELETE + + + + + GET + + + + + OPTIONS + + + + + PATCH + + + + + POST + + + + + PUT + + + + + HEAD + + + + + + + The allowable request method or HTTP operation codes. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between [[[CodeSystem]]] definitions and their use in [coded elements](terminologies.html). + + + + + A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between [[[CodeSystem]]] definitions and their use in [coded elements](terminologies.html). + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + An absolute URI that is used to identify this value set when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this value set is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the value set is stored on different servers. + + + + + A formal identifier that is used to identify this value set when it is represented in other formats, or referenced in a specification, model, design or an instance. + + + + + The identifier that is used to identify this version of the value set when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the value set 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. + + + + + A natural language name identifying the value set. This name should be usable as an identifier for the module by machine processing applications such as code generation. + + + + + A short, descriptive, user-friendly title for the value set. + + + + + The status of this value set. Enables tracking the life-cycle of the content. The status of the value set applies to the value set definition (ValueSet.compose) and the associated ValueSet metadata. Expansions do not have a state. + + + + + A Boolean value to indicate that this value set is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. + + + + + The date (and optionally time) when the value set was created or revised (e.g. the 'content logical definition'). + + + + + The name of the organization or individual that published the value set. + + + + + Contact details to assist a user in finding and communicating with the publisher. + + + + + A free text natural language description of the value set from a consumer's perspective. The textual description specifies the span of meanings for concepts to be included within the Value Set Expansion, and also may specify the intended use and limitations of the Value Set. + + + + + The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate value set instances. + + + + + A legal or geographic region in which the value set is intended to be used. + + + + + If this is set to 'true', then no new versions of the content logical definition can be created. Note: Other metadata might still change. + + + + + Explanation of why this value set is needed and why it has been designed as it has. + + + + + A copyright statement relating to the value set and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the value set. + + + + + A set of criteria that define the contents of the value set by including or excluding codes selected from the specified code system(s) that the value set draws from. This is also known as the Content Logical Definition (CLD). + + + + + A value set can also be "expanded", where the value set is turned into a simple collection of enumerated codes. This element holds the expansion, if it has been performed. + + + + + + + + + A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between [[[CodeSystem]]] definitions and their use in [coded elements](terminologies.html). + + + + + + + The Locked Date is the effective date that is used to determine the version of all referenced Code Systems and Value Set Definitions included in the compose that are not already tied to a specific version. + + + + + Whether inactive codes - codes that are not approved for current use - are in the value set. If inactive = true, inactive codes are to be included in the expansion, if inactive = false, the inactive codes will not be included in the expansion. If absent, the behavior is determined by the implementation, or by the applicable $expand parameters (but generally, inactive codes would be expected to be included). + + + + + Include one or more codes from a code system or other value set(s). + + + + + Exclude one or more codes from the value set based on code system filters and/or other value sets. + + + + + + + + + A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between [[[CodeSystem]]] definitions and their use in [coded elements](terminologies.html). + + + + + + + An absolute URI which is the code system from which the selected codes come from. + + + + + The version of the code system that the codes are selected from, or the special version '*' for all versions. + + + + + Specifies a concept to be included or excluded. + + + + + Select concepts by specify a matching criterion based on the properties (including relationships) defined by the system, or on filters defined by the system. If multiple filters are specified, they SHALL all be true. + + + + + Selects the concepts found in this value set (based on its value set definition). This is an absolute URI that is a reference to ValueSet.url. If multiple value sets are specified this includes the union of the contents of all of the referenced value sets. + + + + + + + + + A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between [[[CodeSystem]]] definitions and their use in [coded elements](terminologies.html). + + + + + + + Specifies a code for the concept to be included or excluded. + + + + + The text to display to the user for this concept in the context of this valueset. If no display is provided, then applications using the value set use the display specified for the code by the system. + + + + + Additional representations for this concept when used in this value set - other languages, aliases, specialized purposes, used for particular purposes, etc. + + + + + + + + + A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between [[[CodeSystem]]] definitions and their use in [coded elements](terminologies.html). + + + + + + + The language this designation is defined for. + + + + + A code that represents types of uses of designations. + + + + + The text value for this designation. + + + + + + + + + A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between [[[CodeSystem]]] definitions and their use in [coded elements](terminologies.html). + + + + + + + A code that identifies a property or a filter defined in the code system. + + + + + The kind of operation to perform as a part of the filter criteria. + + + + + The match value may be either a code defined by the system, or a string value, which is a regex match on the literal string of the property value (if the filter represents a property defined in CodeSystem) or of the system filter value (if the filter represents a filter defined in CodeSystem) when the operation is 'regex', or one of the values (true and false), when the operation is 'exists'. + + + + + + + + + A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between [[[CodeSystem]]] definitions and their use in [coded elements](terminologies.html). + + + + + + + An identifier that uniquely identifies this expansion of the valueset, based on a unique combination of the provided parameters, the system default parameters, and the underlying system code system versions etc. Systems may re-use the same identifier as long as those factors remain the same, and the expansion is the same, but are not required to do so. This is a business identifier. + + + + + The time at which the expansion was produced by the expanding system. + + + + + The total number of concepts in the expansion. If the number of concept nodes in this resource is less than the stated number, then the server can return more using the offset parameter. + + + + + If paging is being used, the offset at which this resource starts. I.e. this resource is a partial view into the expansion. If paging is not being used, this element SHALL NOT be present. + + + + + A parameter that controlled the expansion process. These parameters may be used by users of expanded value sets to check whether the expansion is suitable for a particular purpose, or to pick the correct expansion. + + + + + The codes that are contained in the value set expansion. + + + + + + + + + A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between [[[CodeSystem]]] definitions and their use in [coded elements](terminologies.html). + + + + + + + Name of the input parameter to the $expand operation; may be a server-assigned name for additional default or other server-supplied parameters used to control the expansion process. + + + + + The value of the parameter. + + + + + + + + + + + + + + + + A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between [[[CodeSystem]]] definitions and their use in [coded elements](terminologies.html). + + + + + + + An absolute URI which is the code system in which the code for this item in the expansion is defined. + + + + + If true, this entry is included in the expansion for navigational purposes, and the user cannot select the code directly as a proper value. + + + + + If the concept is inactive in the code system that defines it. Inactive codes are those that are no longer to be used, but are maintained by the code system for understanding legacy data. It might not be known or specified whether an concept is inactive (and it may depend on the context of use). + + + + + The version of the code system from this code was taken. 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. + + + + + The code for this item in the expansion hierarchy. If this code is missing the entry in the hierarchy is a place holder (abstract) and does not represent a valid code in the value set. + + + + + The recommended display for this item in the expansion. + + + + + Additional representations for this item - other languages, aliases, specialized purposes, used for particular purposes, etc. These are relevant when the conditions of the expansion do not fix to a single correct representation. + + + + + Other codes and entries contained under this entry in the hierarchy. + + + + + + + + + Describes validation requirements, source(s), status and dates for one or more elements. + + + + + Describes validation requirements, source(s), status and dates for one or more elements. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A resource that was validated. + + + + + The fhirpath location(s) within the resource that was validated. + + + + + The frequency with which the target must be validated (none; initial; periodic). + + + + + The validation status of the target (attested; validated; in process; requires revalidation; validation failed; revalidation failed). + + + + + When the validation status was updated. + + + + + What the target is validated against (nothing; primary source; multiple sources). + + + + + The primary process by which the target is validated (edit check; value set; primary source; multiple sources; standalone; in context). + + + + + Frequency of revalidation. + + + + + The date/time validation was last completed (including failed validations). + + + + + The date when target is next validated, if appropriate. + + + + + The result if validation fails (fatal; warning; record only; none). + + + + + Information about the primary source(s) involved in validation. + + + + + Information about the entity attesting to information. + + + + + Information about the entity validating information. + + + + + + + + + Describes validation requirements, source(s), status and dates for one or more elements. + + + + + + + Reference to the primary source. + + + + + Type of primary source (License Board; Primary Education; Continuing Education; Postal Service; Relationship owner; Registration Authority; legal source; issuing source; authoritative source). + + + + + Method for communicating with the primary source (manual; API; Push). + + + + + Status of the validation of the target against the primary source (successful; failed; unknown). + + + + + When the target was validated against the primary source. + + + + + Ability of the primary source to push updates/alerts (yes; no; undetermined). + + + + + Type of alerts/updates the primary source can send (specific requested changes; any changes; as defined by source). + + + + + + + + + Describes validation requirements, source(s), status and dates for one or more elements. + + + + + + + The individual or organization attesting to information. + + + + + When the who is asserting on behalf of another (organization or individual). + + + + + The method by which attested information was submitted/retrieved (manual; API; Push). + + + + + The date the information was attested to. + + + + + A digital identity certificate associated with the attestation source. + + + + + A digital identity certificate associated with the proxy entity submitting attested information on behalf of the attestation source. + + + + + Signed assertion by the proxy entity indicating that they have the right to submit attested information on behalf of the attestation source. + + + + + Signed assertion by the attestation source that they have attested to the information. + + + + + + + + + Describes validation requirements, source(s), status and dates for one or more elements. + + + + + + + Reference to the organization validating information. + + + + + A digital identity certificate associated with the validator. + + + + + Signed assertion by the validator that they have validated the information. + + + + + + + + + + + Attested + + + + + Validated + + + + + In process + + + + + Requires revalidation + + + + + Validation failed + + + + + Re-Validation failed + + + + + + + The validation status of the target. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + An authorization for the provision of glasses and/or contact lenses to a patient. + + + + + An authorization for the provision of glasses and/or contact lenses to a patient. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + A unique identifier assigned to this vision prescription. + + + + + The status of the resource instance. + + + + + The date this resource was created. + + + + + A resource reference to the person to whom the vision prescription applies. + + + + + A reference to a resource that identifies the particular occurrence of contact between patient and health care provider during which the prescription was issued. + + + + + The date (and perhaps time) when the prescription was written. + + + + + The healthcare professional responsible for authorizing the prescription. + + + + + Contain the details of the individual lens specifications and serves as the authorization for the fullfillment by certified professionals. + + + + + + + + + An authorization for the provision of glasses and/or contact lenses to a patient. + + + + + + + Identifies the type of vision correction product which is required for the patient. + + + + + The eye for which the lens specification applies. + + + + + Lens power measured in dioptres (0.25 units). + + + + + Power adjustment for astigmatism measured in dioptres (0.25 units). + + + + + Adjustment for astigmatism measured in integer degrees. + + + + + Allows for adjustment on two axis. + + + + + Power adjustment for multifocal lenses measured in dioptres (0.25 units). + + + + + Contact lens power measured in dioptres (0.25 units). + + + + + Back curvature measured in millimetres. + + + + + Contact lens diameter measured in millimetres. + + + + + The recommended maximum wear period for the lens. + + + + + Special color or pattern. + + + + + Brand recommendations or restrictions. + + + + + Notes for special requirements such as coatings and lens materials. + + + + + + + + + An authorization for the provision of glasses and/or contact lenses to a patient. + + + + + + + Amount of prism to compensate for eye alignment in fractional units. + + + + + The relative base, or reference lens edge, for the prism. + + + + + + + + + + + Up + + + + + Down + + + + + In + + + + + Out + + + + + + + A coded concept listing the base codes. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + + + + + Right Eye + + + + + Left Eye + + + + + + + A coded concept listing the eye codes. + If the element is present, it must have either a @value, an @id, or extensions + + + + + + + + diff --git a/org.hl7.fhir.r4/src/main/resources/schemas/fhir-xhtml.xsd b/org.hl7.fhir.r4/src/main/resources/schemas/fhir-xhtml.xsd new file mode 100644 index 000000000..1e442e4ef --- /dev/null +++ b/org.hl7.fhir.r4/src/main/resources/schemas/fhir-xhtml.xsd @@ -0,0 +1,2101 @@ + + + + + + + XHTML 1.0 (Second Edition) Strict in XML Schema + + This is the same as HTML 4 Strict except for + changes due to the differences between XML and SGML. + + Namespace = http://www.w3.org/1999/xhtml + + For further information, see: http://www.w3.org/TR/xhtml1 + + Copyright (c) 1998-2002 W3C (MIT, INRIA, Keio), + All Rights Reserved. + + The DTD version is identified by the PUBLIC and SYSTEM identifiers: + + PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" + SYSTEM "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd" + + _id: xhtml1-strict.xsd,v 1.2 2002/08/28 08:05:44 mimasa Exp $ + + + + + + ================ Character mnemonic entities ========================= + + XHTML entity sets are identified by the PUBLIC and SYSTEM identifiers: + + PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" + SYSTEM "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent" + + PUBLIC "-//W3C//ENTITIES Special for XHTML//EN" + SYSTEM "http://www.w3.org/TR/xhtml1/DTD/xhtml-special.ent" + + PUBLIC "-//W3C//ENTITIES Symbols for XHTML//EN" + SYSTEM "http://www.w3.org/TR/xhtml1/DTD/xhtml-symbol.ent" + + + + + ================== Imported Names ==================================== + + + + + + media type, as per [RFC2045] + + + + + + + + comma-separated list of media types, as per [RFC2045] + + + + + + + + a character encoding, as per [RFC2045] + + + + + + + + a space separated list of character encodings, as per [RFC2045] + + + + + + + + a language code, as per [RFC3066] + + + + + + + + a single character, as per section 2.2 of [XML] + + + + + + + + + + one or more digits + + + + + + + + + + tabindex attribute specifies the position of the current element + in the tabbing order for the current document. This value must be + a number between 0 and 32767. User agents should ignore leading zeros. + + + + + + + + + + + space-separated list of link types + + + + + + + + single or comma-separated list of media descriptors + + + + + + + + + + a Uniform Resource Identifier, see [RFC2396] + + + + + + + + a space separated list of Uniform Resource Identifiers + + + + + + + + date and time information. ISO date format + + + + + + + + script expression + + + + + + + + style sheet data + + + + + + + + used for titles etc. + + + + + + + + nn for pixels or nn% for percentage length + + + + + + + + + + pixel, percentage, or relative + + + + + + + + + + integer representing length in pixels + + + + + + + these are used for image maps + + + + + + + + + + + + + + comma separated list of lengths + + + + + + + + + =================== Generic Attributes =============================== + + + + + + core attributes common to most elements + id document-wide unique id + class space separated list of classes + style associated style info + title advisory title/amplification + + + + + + + + + + + internationalization attributes + lang language code (backwards compatible) + xml:lang language code (as per XML 1.0 spec) + dir direction for weak/neutral text + + + + + + + + + + + + + + + + + attributes for common UI events + onclick a pointer button was clicked + ondblclick a pointer button was double clicked + onmousedown a pointer button was pressed down + onmouseup a pointer button was released + onmousemove a pointer was moved onto the element + onmouseout a pointer was moved away from the element + onkeypress a key was pressed and released + onkeydown a key was pressed down + onkeyup a key was released + + + + + + + + attributes for elements that can get the focus + accesskey accessibility key character + tabindex position in tabbing order + onfocus the element got the focus + onblur the element lost the focus + + + + + + + + + + + + + + =================== Text Elements ==================================== + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + "Inline" covers inline or "text-level" elements + + + + + + + + + + ================== Block level elements ============================== + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + "Flow" mixes block and inline and is used for list items etc. + + + + + + + + + + + ================== Content models for exclusions ===================== + + + + + + a elements use "Inline" excluding a + + + + + + + + + + + + + pre uses "Inline" excluding big, small, sup or sup + + + + + + + + + + + + + + ================ Document Structure ================================== + + + + + + + generic language/style container + + + + + + + + + + + + + =================== Paragraphs ======================================= + + + + + + + + + + + + + + =================== Headings ========================================= + + There are six levels of headings from h1 (the most important) + to h6 (the least important). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + =================== Lists ============================================ + + + + + + Unordered list + + + + + + + + + + + + + Ordered (numbered) list + + + + + + + + + + + + + list item + + + + + + + + + + + + + definition lists - dt for term, dd for its definition + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + =================== Address ========================================== + + + + + + information on author + + + + + + + + + + + + + =================== Horizontal Rule ================================== + + + + + + + + + + =================== Preformatted Text ================================ + + + + + + content is "Inline" excluding "img|object|big|small|sub|sup" + + + + + + + + + + + + + + =================== Block-like Quotes ================================ + + + + + + + + + + + + + + + + ================== The Anchor Element ================================ + + + + + + content is "Inline" except that anchors shouldn't be nested + + + + + + + + + + + + + + + + + + + + + + + ===================== Inline Elements ================================ + + + + + + generic language/style container + + + + + + + + + + + + + + I18N BiDi over-ride + + + + + + + + + + + + + + + + + + + + + + + + + forced line break + + + + + + + + + + emphasis + + + + + + + + + + + + + + strong emphasis + + + + + + + + + + + + + + definitional + + + + + + + + + + + + + + program code + + + + + + + + + + + + + + sample + + + + + + + + + + + + + + something user would type + + + + + + + + + + + + + + variable + + + + + + + + + + + + + + citation + + + + + + + + + + + + + + abbreviation + + + + + + + + + + + + + + acronym + + + + + + + + + + + + + + inlined quote + + + + + + + + + + + + + + + subscript + + + + + + + + + + + + + + superscript + + + + + + + + + + + + + + fixed pitch font + + + + + + + + + + + + + + italic font + + + + + + + + + + + + + + bold font + + + + + + + + + + + + + + bigger font + + + + + + + + + + + + + + smaller font + + + + + + + + + + + + + + =================== Images =========================================== + + To avoid accessibility problems for people who aren't + able to see the image, you should provide a text + description using the alt and longdesc attributes. + In addition, avoid the use of server-side image maps. + Note that in this DTD there is no name attribute. That + is only available in the transitional and frameset DTD. + + + + + + + + + + + + + + usemap points to a map element which may be in this document + or an external document, although the latter is not widely supported + + + + + + + + + + + + + + + ================== Client-side image maps ============================ + + These can be placed in the same document or grouped in a + separate document although this isn't yet widely supported + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + ======================= Tables ======================================= + + Derived from IETF HTML table standard, see [RFC1942] + + + + + + The border attribute sets the thickness of the frame around the + table. The default units are screen pixels. + + The frame attribute specifies which parts of the frame around + the table should be rendered. The values are not the same as + CALS to avoid a name clash with the valign attribute. + + + + + + + + + + + + + + + + + + The rules attribute defines which rules to draw between cells: + + If rules is absent then assume: + "none" if border is absent or border="0" otherwise "all" + + + + + + + + + + + + + + horizontal alignment attributes for cell contents + + char alignment char, e.g. char=':' + charoff offset for alignment char + + + + + + + + + + + + + + + + + + + + vertical alignment attributes for cell contents + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Use thead to duplicate headers when breaking table + across page boundaries, or for static headers when + tbody sections are rendered in scrolling panel. + + Use tfoot to duplicate footers when breaking table + across page boundaries, or for static footers when + tbody sections are rendered in scrolling panel. + + Use multiple tbody sections when rules are needed + between groups of table rows. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + colgroup groups a set of col elements. It allows you to group + several semantically related columns together. + + + + + + + + + + + + + + + + + col elements define the alignment properties for cells in + one or more columns. + + The width attribute specifies the width of the columns, e.g. + + width=64 width in screen pixels + width=0.5* relative width of 0.5 + + The span attribute causes the attributes of one + col element to apply to more than one column. + + + + + + + + + + + + + + + + + + + + + + + + + Scope is simpler than headers attribute for common tables + + + + + + + + + + + + th is for headers, td for data and for cells acting as both + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/org.hl7.fhir.r4/src/main/resources/schemas/xml.xsd b/org.hl7.fhir.r4/src/main/resources/schemas/xml.xsd new file mode 100644 index 000000000..efe005d46 --- /dev/null +++ b/org.hl7.fhir.r4/src/main/resources/schemas/xml.xsd @@ -0,0 +1,272 @@ + + + + + + +
+

About the XML namespace

+
+

+ This schema document describes the XML namespace, in a form + suitable for import by other schema documents. +

+

+ See + http://www.w3.org/XML/1998/namespace.html and + + http://www.w3.org/TR/REC-xml for information + about this namespace. +

+

+ Note that local names in this namespace are intended to be + defined only by the World Wide Web Consortium or its subgroups. + The names currently defined in this namespace are listed below. + They should not be used with conflicting semantics by any Working + Group, specification, or document instance. +

+

+ See further below in this document for more information about how to refer to this schema document from your own + XSD schema documents and about the + namespace-versioning policy governing this schema document. +

+
+
+ + + + + +
+

lang (as an attribute name)

+

+ denotes an attribute whose value + is a language code for the natural language of the content of + any element; its value is inherited. This name is reserved + by virtue of its definition in the XML specification.

+
+
+

Notes

+

+ Attempting to install the relevant ISO 2- and 3-letter + codes as the enumerated possible values is probably never + going to be a realistic possibility. +

+

+ See BCP 47 at + http://www.rfc-editor.org/rfc/bcp/bcp47.txt + and the IANA language subtag registry at + + http://www.iana.org/assignments/language-subtag-registry + for further information. +

+

+ The union allows for the 'un-declaration' of xml:lang with + the empty string. +

+
+ + + + + + + + + + + + + + + +
+

space (as an attribute name)

+

+ denotes an attribute whose + value is a keyword indicating what whitespace processing + discipline is intended for the content of the element; its + value is inherited. This name is reserved by virtue of its + definition in the XML specification.

+
+ + + + + + + + + + + + +
+

base (as an attribute name)

+

+ denotes an attribute whose value + provides a URI to be used as the base for interpreting any + relative URIs in the scope of the element on which it + appears; its value is inherited. This name is reserved + by virtue of its definition in the XML Base specification.

+

+ See http://www.w3.org/TR/xmlbase/ + for information about this attribute. +

+
+ + + + + + +
+

id (as an attribute name)

+

+ denotes an attribute whose value + should be interpreted as if declared to be of type ID. + This name is reserved by virtue of its definition in the + xml:id specification.

+

+ See http://www.w3.org/TR/xml-id/ + for information about this attribute. +

+
+ + + + + + + + + + + +
+

Father (in any context at all)

+
+

+ denotes Jon Bosak, the chair of + the original XML Working Group. This name is reserved by + the following decision of the W3C XML Plenary and + XML Coordination groups: +

+
+

+ In appreciation for his vision, leadership and + dedication the W3C XML Plenary on this 10th day of + February, 2000, reserves for Jon Bosak in perpetuity + the XML name "xml:Father". +

+
+
+
+ + + + +
+

+ About this schema document +

+
+

+ This schema defines attributes and an attribute group suitable + for use by schemas wishing to allow xml:base, + xml:lang, xml:space or + xml:id attributes on elements they define. +

+

+ To enable this, such a schema must import this schema for + the XML namespace, e.g. as follows: +

+ 
+          <schema . . .>
+           . . .
+           <import namespace="http://www.w3.org/XML/1998/namespace"
+                      schemaLocation="http://www.w3.org/2001/xml.xsd"/>
+
+

+ or +

+ 
+           <import namespace="http://www.w3.org/XML/1998/namespace"
+                      schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
+
+

+ Subsequently, qualified reference to any of the attributes or the + group defined below will have the desired effect, e.g. +

+ 
+          <type . . .>
+           . . .
+           <attributeGroup ref="xml:specialAttrs"/>
+
+

+ will define a type which will schema-validate an instance element + with any of those attributes. +

+
+
+ + + + +
+

+ Versioning policy for this schema document +

+
+

+ In keeping with the XML Schema WG's standard versioning + policy, this schema document will persist at + + http://www.w3.org/2009/01/xml.xsd. +

+

+ At the date of issue it can also be found at + + http://www.w3.org/2001/xml.xsd. +

+

+ The schema document at that URI may however change in the future, + in order to remain compatible with the latest version of XML + Schema itself, or with the XML namespace itself. In other words, + if the XML Schema or XML namespaces change, the version of this + document at + http://www.w3.org/2001/xml.xsd + + will change accordingly; the version at + + http://www.w3.org/2009/01/xml.xsd + + will not change. +

+

+ Previous dated (and unchanging) versions of this schema + document are at: +

+ +
+
+ + + diff --git a/org.hl7.fhir.r4/src/main/resources/schemas/xmldsig-core-schema.xsd b/org.hl7.fhir.r4/src/main/resources/schemas/xmldsig-core-schema.xsd new file mode 100644 index 000000000..555a88bdb --- /dev/null +++ b/org.hl7.fhir.r4/src/main/resources/schemas/xmldsig-core-schema.xsd @@ -0,0 +1,254 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/org.hl7.fhir.r4/src/main/resources/snapshot-generation-tests.xml b/org.hl7.fhir.r4/src/main/resources/snapshot-generation-tests.xml index d2cf74d76..ba13ea65e 100644 --- a/org.hl7.fhir.r4/src/main/resources/snapshot-generation-tests.xml +++ b/org.hl7.fhir.r4/src/main/resources/snapshot-generation-tests.xml @@ -1,4 +1,4 @@ - + @@ -1733,7 +1735,7 @@ - + @@ -1827,6 +1829,54 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1898,7 +1948,7 @@ - + @@ -3586,7 +3636,7 @@ <warningOnly value="false"/> </assert> </action> - </test> + </test> <test> <name value="Test36"/> <description value="Test deep nesting"/> @@ -3613,7 +3663,33 @@ </assert> </action> </test> - <test> + <test> + <name value="Test37"/> + <description value="Test deep nesting"/> + <action> + <operation> + <type> + <system value="http://hl7.org/fhir/testscript-operation-codes"/> + <code value="snapshot"/> + </type> + <resource value="StructureDefinition"/> + <encodeRequestUrl value="false"/> + <params value="sort=true"/> + <responseId value="t37o"/> + <sourceId value="t37"/> + </operation> + </action> + <action> + <assert> + <label value="test37"/> + <description value="Snapshot includes polymorphic constrained element"/> + <direction value="response"/> + <expression value="fixture('t37o').snapshot.element.where(path = 'MedicationDispense.dosageInstruction.doseQuantity').count() = 1"/> + <warningOnly value="false"/> + </assert> + </action> + </test> + <test> <name value="Test38"/> <description value="Test deep nesting"/> <action>