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 may 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 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 An instant in time - known at least to the second Note: This is intended for precisely observed times, typically system logs etc., and not human-reported times - for them, see date and dateTime 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 markdown syntax for optional processing by a mark down presentation engine Systems are not required to have markdown support, and there is considerable variation in markdown syntax, so the text should be readable without markdown processing. The preferred markdown syntax is described here: http://daringfireball.net/projects/markdown/syntax (and tests here: http://daringfireball.net/projects/downloads/MarkdownTest_1.0.zip) 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 a 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 - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for 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 that contains it. Usually modifier elements provide negation or qualification. In order 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. A human-readable formatted text, including images. 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. In order 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. 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. An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity 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 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 that the period is ongoing. 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. 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. In XML, represented using base64. An alternative 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 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 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 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. 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. 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 A technical identifier - identifies some entity uniquely and unambiguously. 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 Identifies the purpose for this identifier, if known . If the element is present, it must have either a @value, an @id, or extensions 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 - i.e. off a pick list of available items (codes or displays). A digital signature along with supporting context. The signature may be electronic/cryptographic in nature, or a graphical image representing a hand-written signature, or a signature process. 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 signature. Important mime types are application/signature+xml for X ML DigSig, application/jwt for JWT, 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. 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 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 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 metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content may 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 values changes when the resource is created, updated, or deleted. When the resource last changed - e.g. when the version changed. 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. A full text representation of the address. 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, 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 (i.e. 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 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 description of a triggering event. 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. The name of the event (if this is a named-event trigger). The timing of the event (if this is a period trigger). The triggering data of the event (if this is a data trigger). Named Event Periodic Data Added Data Modified 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 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 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. 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. Note that the value for this element can be a path to allow references to nested elements. In that case, all the elements along the path must be supported. Code filters specify additional constraints on the data, specifying the value set of interest for a particular element of the data. Date filters specify additional constraints on the data in terms of the applicable date range for specific elements. 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 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 path must resolve to an element of type code, Coding, or CodeableConcept. The valueset for the code filter. The valueSet and value elements are exclusive. 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. Only one of valueSet, valueCode, valueCoding, or valueCodeableConcept may be specified. 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. The Codings for the code filter. Only one of valueSet, valueCode, valueConding, or valueCodeableConcept may be specified. 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 Codings. The CodeableConcepts for the code filter. Only one of valueSet, valueCode, valueConding, or valueCodeableConcept may be specified. 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 CodeableConcepts. 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 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 path must resolve to an element of type 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 from now. 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 instruction - e.g. "with meals". 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. Amount of medication per dose. Upper limit on medication per unit of time. Upper limit on medication per administration. Upper limit on medication per lifetime of the patient. Amount of medication per unit of time. 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 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 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. 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. A full text representation of the name. 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. Contacts are ranked with lower values coming before higher 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 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. 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. 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. A maximum value for the count of the desired repetitions (e.g. do something 6-8 times). How long this thing happens for when it happens. The upper limit of how long this thing happens for when it happens. The units of time for the duration, in UCUM units. The number of times to repeat the action within the specified period / period range (i.e. both period and periodMax provided). 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 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. Real world events that the occurrence of the event should be tied to. 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 Afternoon 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 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. 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. Explanatory notes and implementation guidance about the data element, including notes about how to use the data properly, exceptions to proper use, etc. 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. This information is provided 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. Identifies the identity of an element defined elsewhere in the profile whose content rules should be applied to the current element. 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. The values of elements present in the pattern must match exactly (case-sensitive, accent-sensitive, etc.). 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 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. 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](http://hl7.org/fluentpath) 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 SHALL hold for the datatype this element refers to. 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 resource SHALL conform to at least one profile defined in the implementation guide. Identifies a profile structure or implementation Guide that SHALL hold for the target of the reference this element refers to. 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 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. Points to the value set or external definition (e.g. implicit value set) that identifies the set of codes to be used. If the binding refers to an explicit value set - the normal case - then use a Reference(ValueSet) preferably containing the canonical URL for the value set. If the reference is to an implicit value set - usually, an IETF RFC that defines a grammar, such as mime types - then use a uri. 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 a restricted subset of FHIRPath, 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 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. A resource that includes narrative, extensions, and contained resources. A human-readable narrative that contains a summary of the resource, and may 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. In order 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. 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. Usually modifier elements provide negation or qualification. In order 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. 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 may 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. 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 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 Processing Complete Error Partial Processing 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 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. May or may 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 patient, device, practitioner, location or other object the account is associated with. Identifies the period of time the account applies to; e.g. accounts created per fiscal year, quarter, etc. Indicates the period of time over which the account is allowed to have transactions posted to it. This period may be different to the coveragePeriod which is the duration of time that services may occur. Represents the sum of all credits less all debits associated with the account. Might be positive, zero or negative. 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 organization, department, etc. with responsibility for the account. Provides additional information about what the account tracks and how it is used. Parties financially responsible for the 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 are responsible for payment (or part of) of charges applied to this account (including self-pay). A coverage may only be resposible 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 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. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this activity definition is (or will be) published. The URL SHOULD include the major version of the activity definition. For more information see [Technical and Business Versions](resource.html#versions). 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. 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. The date (and optionally time) when the activity definition was published. The date must change if and 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 individual or organization that published the activity definition. A free text natural language description of the activity definition from a consumer's perspective. Explaination of why this activity definition is needed and why it has been designed as it has. A detailed description of how the asset is used from a clinical perspective. 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 doesn't change the original approval date. The period during which the activity definition content was or is planned to be in active use. The content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching for appropriate activity definition instances. A legal or geographic region in which the activity definition is intended to be used. 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. A contributor to the content of the asset, including authors, editors, reviewers, and endorsers. Contact details to assist a user in finding and communicating with the publisher. 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. Related artifacts such as additional documentation, justification, or bibliographic references. A reference to a Library resource containing any formal logic used by the asset. A description of the kind of resource the activity definition is representing. For example, a MedicationRequest, a ProcedureRequest, or a CommunicationRequest. Typically, but not always, this is a Request resource. Detailed description of the type of activity; e.g. What lab test, what procedure, what kind of encounter. 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). 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 intent 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. A brief, natural language description of the intended semantics of the dynamic value. 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 media type of the language for the expression. An expression specifying the value of the customized element. Patient Practitioner Related Person The type of participant in the activity If the element is present, it must have either a @value, an @id, or extensions Account ActivityDefinition AdverseEvent AllergyIntolerance Appointment AppointmentResponse AuditEvent Basic Binary BodySite Bundle CapabilityStatement CarePlan CareTeam ChargeItem Claim ClaimResponse ClinicalImpression CodeSystem Communication CommunicationRequest CompartmentDefinition Composition ConceptMap Condition Consent Contract Coverage DataElement DetectedIssue Device DeviceComponent DeviceMetric DeviceRequest DeviceUseStatement DiagnosticReport DocumentManifest DocumentReference DomainResource EligibilityRequest EligibilityResponse Encounter Endpoint EnrollmentRequest EnrollmentResponse EpisodeOfCare ExpansionProfile ExplanationOfBenefit FamilyMemberHistory Flag Goal GraphDefinition Group GuidanceResponse HealthcareService ImagingManifest ImagingStudy Immunization ImmunizationRecommendation ImplementationGuide Library Linkage List Location Measure MeasureReport Media Medication MedicationAdministration MedicationDispense MedicationRequest MedicationStatement MessageDefinition MessageHeader NamingSystem NutritionOrder Observation OperationDefinition OperationOutcome Organization Parameters Patient PaymentNotice PaymentReconciliation Person PlanDefinition Practitioner PractitionerRole Procedure ProcedureRequest ProcessRequest ProcessResponse Provenance Questionnaire QuestionnaireResponse ReferralRequest RelatedPerson RequestGroup ResearchStudy ResearchSubject Resource RiskAssessment Schedule SearchParameter Sequence ServiceDefinition Slot Specimen StructureDefinition StructureMap Subscription Substance SupplyDelivery SupplyRequest Task TestReport TestScript ValueSet VisionPrescription The kind of activity the definition is describing 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 The identifier(s) of this adverse event that are assigned by business processes and/or used to refer to it when a direct URL reference to the resource itsefl is not appropriate. The type of event which is important to characterize what occurred and caused harm to the subject, or had the potential to cause harm to the subject. This element defines the specific type of event that occurred or that was prevented from occurring. This subject or group impacted by the event. With a prospective adverse event, there will be no subject as the adverse event was prevented. The date (and perhaps time) when the adverse event occurred. 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. Describes the seriousness or severity of the adverse event. 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 Act. Such information includes information leading to the decision to perform the Act and how to perform the Act (e.g. consultant), information that the Act itself seeks to reveal (e.g. informant of clinical history), or information about what Act was performed (e.g. informant witness). Describes the adverse event in text. 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. causality1 | causality2. assess1 | assess2. AdverseEvent.suspectEntity.causalityProductRelatedness. method1 | method2. AdverseEvent.suspectEntity.causalityAuthor. result1 | result2. causality1 placeholder causality2 placeholder TODO If the element is present, it must have either a @value, an @id, or extensions Adverse Event Potential Adverse Event Overall categorization of the 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 This records identifiers associated with this allergy/intolerance 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 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"). The patient who has the allergy or intolerance. Estimated or actual date, date-time, or age when allergy or intolerance was identified. The date on which the existance of the AllergyIntolerance was first asserted or acknowledged. 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'. 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. If the element is present, it must have either a @value, an @id, or extensions Unconfirmed Confirmed Refuted Entered In Error Assertion about certainty associated with a propensity, or potential risk, of a reaction to the identified substance. 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 Active Inactive Resolved The clinical status of the allergy or intolerance. 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. A broad categorisation 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 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 (where actual time of appointment is only an estimate or is a planned appointment request). 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. The referral request this appointment is allocated to assess (incoming referral). List of participants involved in the appointment. A set of date ranges (potentially including times) that the appointment is preferred to be scheduled within. When using these values, the minutes duration should be provided to indicate the length of the appointment to fill and populate the start/end times for the actual allocated time. 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. Is this participant required to be present at the meeting. This covers a use-case where 2 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. 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 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 time when the event occurred on the source. 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. 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. Direct reference to a resource that identifies the agent. Unique identifier for the user actively participating 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 always be version specific. 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 details, base64 encoded. Used to carry bulk information. 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 binary resource can contain any content, whether text, image, pdf, zip archive, etc. 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). Treat this binary as if it was this other resource for access control purposes. The actual content, base64 encoded. Record details about the anatomical location of a specimen or body part. This resource may be used when a coded concept does not provide the necessary detail needed for the use case. Record details about the anatomical location of a specimen or body part. 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 location. Whether this body site is in active use. Named anatomical location - ideally coded where possible. Qualifier to refine the anatomical location. These include qualifiers for laterality, relative location, directionality, number, and plane. A summary, charactarization or explanation of the anatomic location. 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 batch that won't change as a batch is copied from server to server. Indicates the purpose of this bundle - how it was intended to be used. If a set of search matches, this is the total number of matches for the search (as opposed to the number of results in this 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. 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 Resources for the entry. 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. Additional information about how this entry should be processed as part of a transaction. 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. When searching, the server's search ranking score for the entry. A container for a collection of resources. The HTTP verb for this entry in either a change history, or a transaction/ transaction response. 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. The etag for the resource, it 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 POST PUT DELETE HTTP verbs (in the HTTP command line). 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 was 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. 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 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 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. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this capability statement is (or will be) published. The URL SHOULD include the major version of the capability statement. For more information see [Technical and Business Versions](resource.html#versions). 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 if and 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 individual or organization 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 terms 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. Explaination 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 or uses. This capability statement is a published API description that corresponds to a business service. The rest of the capability statement does not need to repeat the details of the referenced resource, but can do so. 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 on which this capability statement is based. A code that indicates whether the application accepts unknown elements or extensions when reading resources. 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 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). 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 that may be used as a statement of actual server functionality or a statement of required or desired server implementation. Name 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 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. A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server 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 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. Certificates associated with security profiles. A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation. Mime type for a certificate. Actual certificate. A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server 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). 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 (e.g. 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. A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server 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 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]]]). 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 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 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. A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server 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 description of the solution's support for an event at this end-point. A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server 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 end-point. 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 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 that may be used as a statement of actual server functionality or a statement of required or desired server implementation. A coded identifier of a supported messaging event. The impact of the content of the message. The mode of this event declaration - whether an application is a sender or receiver. A resource associated with the event. This is the resource that defines the event. Information about the request for this event. Information about the response for this event. Guidance on how this event is handled, such as internal system trigger points, business rules, etc. A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server 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 constraint on a resource used in the document. 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 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 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 Neither Elements or Extensions Unknown Extensions Unknown Elements Unknown Elements and Extensions A code that indicates whether an application accepts unknown elements or extensions when reading resources. 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 This records identifiers associated with this care plan 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). Identifies the protocol, questionnaire, guideline or other specification the care plan should be conducted in accordance with. 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 CarePlan. A description of the scope and nature of the plan. Identifies the patient or group whose intended care is described by the plan. Identifies the original context in which this particular CarePlan was created. Indicates when the plan did (or is intended to) come into effect and end. Identifies the individual(s) or ogranization who is responsible for the content 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 co-morbidities, 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. High-level categorization of the type of activity in a care plan. Identifies the protocol, questionnaire, guideline or other specification the planned activity should be conducted in accordance with. 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. Provides the health condition(s) that 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, 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. Pending Active Suspended Completed Entered In Error Cancelled 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 Not Started Scheduled In Progress On Hold Completed Cancelled Unknown Indicates where the activity is at in 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 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 This records identifiers associated with this care team 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. 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 or episode of care that establishes the context for this care team. 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. 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 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 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. 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. Account into which this ChargeItems belongs. Comments made about the event by the performer, subject or other participants. Further information supporting the 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, anaesthesiologiest, 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 stage lifecycle stage of a ChargeItem If the element is present, it must have either a @value, an @id, or extensions A provider issued list of services and products provided, or to be provided, to a patient which is provided to an insurer for payment recovery. A provider issued list of services and products provided, or to be provided, to a patient which is provided to an insurer for payment recovery. If the element is present, it must have either a @value, an @id, or extensions The business identifier for the instance: claim number, pre-determination or pre-authorization number. The status of the resource instance. The category of claim, eg, oral, pharmacy, vision, insitutional, professional. A finer grained suite of claim subtype codes which may convey Inpatient vs Outpatient and/or a specialty service. In the US the BillType. Complete (Bill or Claim), Proposed (Pre-Authorization), Exploratory (Pre-determination). Patient Resource. The billable period for which charges are being submitted. The date when the enclosed suite of services were performed or completed. Person who created the invoice/claim/pre-determination or pre-authorization. The Insurer who is target of the request. The provider which is responsible for the bill, claim pre-determination, pre-authorization. The organization which is responsible for the bill, claim pre-determination, pre-authorization. Immediate (STAT), best effort (NORMAL), deferred (DEFER). In the case of a Pre-Determination/Pre-Authorization the provider may request that funds in the amount of the expected Benefit be reserved ('Patient' or 'Provider') to pay for the Benefits determined on the subsequent claim(s). 'None' explicitly indicates no funds reserving is requested. Other claims which are related to this claim such as prior claim versions or for related services. Prescription to support the dispensing of Pharmacy or Vision products. Original prescription which has been superceded by this prescription to support the dispensing of pharmacy services, medications or products. For example, a physician may prescribe a medication which the pharmacy determines is contraindicated, or for which the patient has an intolerance, and therefor issues a new precription for an alternate medication which has the same theraputic intent. The prescription from the pharmacy becomes the 'prescription' and that from the physician becomes the 'original prescription'. The party to be reimbursed for the services. The referral resource which lists the date, practitioner, reason and other supporting information. Facility where the services were provided. The members of the team who provided the overall service as well as their role and whether responsible and qualifications. Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. Often there are mutiple jurisdiction specific valuesets which are required. List of patient diagnosis for which care is sought. Ordered list of patient procedures performed to support the adjudication. Financial instrument by which payment information for health care. An accident which resulted in the need for healthcare services. The start and optional end dates of when the patient was precluded from working due to the treatable condition(s). The start and optional end dates of when the patient was confined to a treatment center. First tier of goods and services. The total value of the claim. A provider issued list of services and products provided, or to be provided, to a patient which is provided to an insurer for payment recovery. Other claims which are related to this claim such as prior claim versions or for related services. For example prior or umbrella. An alternate organizational reference to the case or file to which this particular claim pertains - eg Property/Casualy insurer claim # or Workers Compensation case # . A provider issued list of services and products provided, or to be provided, to a patient which is provided to an insurer for payment recovery. Type of Party to be reimbursed: Subscriber, provider, other. organization | patient | practitioner | relatedperson. Party to be reimbursed: Subscriber, provider, other. A provider issued list of services and products provided, or to be provided, to a patient which is provided to an insurer for payment recovery. Sequence of the careTeam which serves to order and provide a link. Member of the team who provided the overall service. The party who is billing and responsible for the claimed good or service rendered to the patient. The lead, assisting or supervising practitioner and their discipline if a multidisiplinary team. The qualification which is applicable for this service. A provider issued list of services and products provided, or to be provided, to a patient which is provided to an insurer for payment recovery. Sequence of the information element which serves to provide a link. 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 which may influence the adjudication. 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. For example, provides the reason for: the additional stay, or missing tooth or any other situation where a reason code is required in addition to the content. A provider issued list of services and products provided, or to be provided, to a patient which is provided to an insurer for payment recovery. Sequence of diagnosis which serves to provide a link. The diagnosis. The type of the Diagnosis, for example: admitting, primary, secondary, discharge. The package billing code, for example DRG, based on the assigned grouping code system. A provider issued list of services and products provided, or to be provided, to a patient which is provided to an insurer for payment recovery. Sequence of procedures which serves to order and provide a link. Date and optionally time the procedure was performed . The procedure code. A provider issued list of services and products provided, or to be provided, to a patient which is provided to an insurer for payment recovery. Sequence of coverage which serves to provide a link and convey coordination of benefit order. A flag to indicate that this Coverage is the focus for adjudication. The Coverage against which the claim is to be adjudicated. Reference to the program or plan identification, underwriter or payor. The contract number of a business agreement which describes the terms and conditions. A list of references from the Insurer to which these services pertain. The Coverages adjudication details. A provider issued list of services and products provided, or to be provided, to a patient which is provided to an insurer for payment recovery. Date of an accident which these services are addressing. Type of accident: work, auto, etc. Accident Place. A provider issued list of services and products provided, or to be provided, to a patient which is provided to an insurer for payment recovery. A service line number. CareTeam applicable for this service or product line. Diagnosis applicable for this service or product line. Procedures applicable for this service or product line. Exceptions, special conditions and supporting information pplicable for this service or product line. The type of reveneu or cost center providing the product and/or service. Health Care Service Type Codes to identify the classification of service or benefits. If this is an actual service or product line, ie. not a Group, then use code to indicate the Professional Service or Product supplied (eg. CTP, HCPCS,USCLS,ICD10, NCPDP,DIN,RXNorm,ACHI,CCI). If a grouping item then use a group code to indicate the type of thing being grouped eg. 'glasses' or 'compound'. Item typification or modifiers codes, eg for Oral whether the treatment is cosmetic or associated with TMJ, or for medical whether the treatment was outside the clinic or out of office hours. For programs which require reason codes for the inclusion or covering of this billed item under the program or sub-program. The date or dates when the enclosed suite of services were performed or completed. Where the service was provided. The number of repetitions of a service or product. If the item is a node then this is the fee for the product or service, otherwise this is the total of the fees for the children 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 addittional service or product or charge. 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. List of Unique Device Identifiers associated with this line item. Physical service site on the patient (limb, tooth, etc). A region or surface of the site, eg. limb region or tooth surface(s). A billed item may include goods or services provided in multiple encounters. Second tier of goods and services. A provider issued list of services and products provided, or to be provided, to a patient which is provided to an insurer for payment recovery. A service line number. The type of reveneu or cost center providing the product and/or service. Health Care Service Type Codes to identify the classification of service or benefits. If this is an actual service or product line, ie. not a Group, then use code to indicate the Professional Service or Product supplied (eg. CTP, HCPCS,USCLS,ICD10, NCPDP,DIN,ACHI,CCI). If a grouping item then use a group code to indicate the type of thing being grouped eg. 'glasses' or 'compound'. Item typification or modifiers codes, eg for Oral whether the treatment is cosmetic or associated with TMJ, or for medical whether the treatment was outside the clinic or out of office hours. For programs which require reson codes for the inclusion, covering, of this billed item under the program or sub-program. The number of repetitions of a service or product. If the item is a node then this is the fee for the product or service, otherwise this is the total of the fees for the children 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 addittional service or product or charge. 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. List of Unique Device Identifiers associated with this line item. Third tier of goods and services. A provider issued list of services and products provided, or to be provided, to a patient which is provided to an insurer for payment recovery. A service line number. The type of reveneu or cost center providing the product and/or service. Health Care Service Type Codes to identify the classification of service or benefits. A code to indicate the Professional Service or Product supplied (eg. CTP, HCPCS,USCLS,ICD10, NCPDP,DIN,ACHI,CCI). Item typification or modifiers codes, eg for Oral whether the treatment is cosmetic or associated with TMJ, or for medical whether the treatment was outside the clinic or out of office hours. For programs which require reson codes for the inclusion, covering, of this billed item under the program or sub-program. The number of repetitions of a service or product. The fee for an addittional service or product or charge. 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 addittional service or product or charge. 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. List of Unique Device Identifiers associated with this line item. Complete Proposed Exploratory Other Complete, proposed, exploratory, other 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 The Response business identifier. The status of the resource instance. Patient Resource. 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. The organization which is responsible for the services rendered to the patient. Original request resource referrence. Processing outcome errror, partial or complete processing. A description of the status of the adjudication. Party to be reimbursed: Subscriber, provider, other. The first tier service adjudications for submitted services. The first tier service adjudications for payor added services. Mutually exclusive with Services Provided (Item). The total cost of the services reported. The amount of deductible applied which was not allocated to any particular service line. Total amount of benefit payable (Equal to sum of the Benefit amounts from all detail lines and additions less the Unallocated Deductible). Payment details for the claim if the claim has been paid. Status of funds reservation (For provider, for Patient, None). The form to be used for printing the content. Note text. Request for additional supporting or authorizing information, such as: documents, images or resources. Financial instrument by which payment information for health care. This resource provides the adjudication details from the processing of a Claim resource. A service line number. A list of note references to the notes provided below. The adjudication results. The second tier service adjudications for submitted services. This resource provides the adjudication details from the processing of a Claim resource. Code indicating: Co-Pay, deductible, eligible, benefit, tax, etc. Adjudication reason such as limit reached. Monetary amount associated with the code. A non-monetary value for example a percentage. Mutually exclusive to the amount element above. This resource provides the adjudication details from the processing of a Claim resource. A service line number. A list of note references to the notes provided below. The adjudications results. The third tier service adjudications for submitted services. This resource provides the adjudication details from the processing of a Claim resource. A service line number. A list of note references to the notes provided below. The adjudications results. This resource provides the adjudication details from the processing of a Claim resource. List of input service items which this service line is intended to replace. The type of reveneu or cost center providing the product and/or service. Health Care Service Type Codes to identify the classification of service or benefits. A code to indicate the Professional Service or Product supplied. Item typification or modifiers codes, eg for Oral whether the treatment is cosmetic or associated with TMJ, or for medical whether the treatment was outside the clinic or out of office hours. The fee charged for the professional service or product.. A list of note references to the notes provided below. The adjudications results. The second tier service adjudications for payor added services. This resource provides the adjudication details from the processing of a Claim resource. The type of reveneu or cost center providing the product and/or service. Health Care Service Type Codes to identify the classification of service or benefits. A code to indicate the Professional Service or Product supplied. Item typification or modifiers codes, eg for Oral whether the treatment is cosmetic or associated with TMJ, or for medical whether the treatment was outside the clinic or out of office hours. The fee charged for the professional service or product.. A list of note references to the notes provided below. The adjudications results. 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 is elsewhere. The sequence number of the addition within the line item submitted which contains the error. This value is omitted when the error is not related to an Addition. The sequence number of the addition within the line item submitted which contains the error. This value is omitted when the error is not related to an Addition. An error code,from a specified code system, which details why the claim could not be adjudicated. This resource provides the adjudication details from the processing of a Claim resource. Whether this represents partial or complete payment of the claim. Adjustment to the payment of this transaction which is not related to adjudication of this transaction. Reason for the payment adjustment. Estimated payment data. Payable less any payment adjustment. Payment identifier. This resource provides the adjudication details from the processing of a Claim resource. An integer associated with each note which may be referred to from each service line item. The note purpose: Print/Display. The note text. 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. This resource provides the adjudication details from the processing of a Claim resource. A service line item. The instance number of the Coverage which is the focus for adjudication. The Coverage against which the claim is to be adjudicated. Reference to the program or plan identification, underwriter or payor. The contract number of a business agreement which describes the terms and conditions. A list of references from the Insurer to which these services pertain. The Coverages adjudication details. 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 A unique identifier assigned to the clinical impression that remains consistent regardless of what server the impression is stored on. Identifies the workflow status of the assessment. Categorizes the type of clinical assessment performed. A summary of the context and/or cause of the assessment - why / where was it performed, and what patient events/status prompted it. The patient or group of individuals assessed as part of this record. The encounter or episode of care this impression was created as part of. 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 assesment that was conducted bon 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. This a list of the relevant problems/conditions for a patient. One or more sets of investigations (signs, symptions, etc.). The actual grouping of investigations vary 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 was considered likely or relevant to ongoing treatment. Estimate of likely outcome. RiskAssessment expressing likely outcome. Action taken as part of assessment procedure. 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|nutitirional) 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, code or 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 A code system resource specifies a set of codes drawn from one or more code systems. A code system resource specifies a set of codes drawn from one or more code systems. 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. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this code system is (or will be) published. The URL SHOULD include the major version of the code system. For more information see [Technical and Business Versions](resource.html#versions). 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 status of this code system. Enables tracking the life-cycle of the content. 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 if and 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 individual or organization 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 terms 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. Explaination 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 URL of value set that contains the entire code system. The meaning of the hierarchy of concepts. True If code system defines a post-composition grammar. This flag is used to signify that the code system has not (or does not) maintain the definitions, and a version must be specified when referencing this code system. How much of the content of the code system - the concepts and codes it defines - are represented in this resource. The total number of concepts defined by the code system. Where the code system has a compositional grammar, the count refers to the number of base (primitive) concepts. 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 meaning of the hierarchical relationships are. A code system resource specifies a set of codes drawn from one or more code systems. The code that identifies this filter when it is used in the instance. 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. A code system resource specifies a set of codes drawn from one or more code systems. 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 anotherr defined concept). A code system resource specifies a set of codes drawn from one or more code systems. 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. A code system resource specifies a set of codes drawn from one or more code systems. The language this designation is defined for. A code that details how this designation would be used. The text value for this designation. A code system resource specifies a set of codes drawn from one or more code systems. 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 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 How much 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 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 was notified about a reportable condition. If the element is present, it must have either a @value, an @id, or extensions Identifiers associated with this Communication 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). A protocol, guideline, or other definition that was adhered to in whole or in part by this communication event. An order, proposal or plan fulfilled in whole or in part by this Communication. Part of this action. The status of the transmission. If true, indicates that the described communication event did not actually occur. Describes why the communication event did not occur in coded and/or textual form. The type of message conveyed such as alert, notification, reminder, instruction, etc. A channel that was used for this communication (e.g. email, fax). The patient or group that was the focus of this communication. The entity (e.g. person, organization, clinical information system, or device) which was the target of the communication. If receipts need to be tracked by individual, a separate resource instance will need to be created for each recipient.  Multiple recipient communications are intended where either a receipt(s) is not tracked (e.g. a mass mail-out) or is captured in aggregate (all emails confirmed received by a particular time). The resources which were responsible for or related to producing this communication. The encounter within which the communication was sent. 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, 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 was notified about a reportable condition. A communicated content (or for multi-part communications, one portion of the communication). Preparation In Progress Suspended Aborted 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 A unique ID of this request for reference purposes. It must be provided if user wants it returned as part of any output, otherwise it will be autogenerated, if needed, by CDS system. Does not need to be the actual ID of the source system. 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. 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. A channel that was used for this communication (e.g. email, fax). The patient or group that is the focus of this communication request. The entity (e.g. person, organization, clinical information system, device, group, or care team) which is the intended target of the communication. The resources which were related to producing this communication request. The encounter or episode of care within which the communication request was created. 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 entity (e.g. person, organization, clinical information system, or device) which is to be the source of the communication. The individual who initiated the request and has responsibility for its activation. 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 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 device, practitioner, etc. who initiated the request. The organization the device or practitioner was acting on behalf of. Draft Active Suspended Cancelled Completed Entered in Error Unknown The status of the communication request. If the element is present, it must have either a @value, an @id, or extensions Routine Urgent ASAP STAT Codes indicating the relative importance of a communication request. If the element is present, it must have either a @value, an @id, or extensions 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. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this compartment definition is (or will be) published. The URL SHOULD include the major version of the compartment definition. For more information see [Technical and Business Versions](resource.html#versions). 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. A short, descriptive, user-friendly title for the compartment definition. 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 if and 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 individual or organization 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. Explaination of why this compartment definition is needed and why it has been designed as it has. The content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching for appropriate compartment definition instances. A legal or geographic region in which the compartment definition is intended to be used. 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 compartment 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 document 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. While a Composition defines the structure, it does not actually contain the content: rather the full content of a document is contained in a Bundle, of which the Composition is the first resource contained. A set of healthcare-related information that is assembled together into a single logical document 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. While a Composition defines the structure, it does not actually contain the content: rather the full content of a document is contained in a Bundle, of which the Composition is the first resource contained. If the element is present, it must have either a @value, an @id, or extensions Logical identifier for the composition, assigned when created. 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 document 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. While a Composition defines the structure, it does not actually contain the content: rather the full content of a document is contained in a Bundle, of which the Composition is the first resource contained. 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 document 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. While a Composition defines the structure, it does not actually contain the content: rather the full content of a document is contained in a Bundle, of which the Composition is the first resource contained. 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 document 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. While a Composition defines the structure, it does not actually contain the content: rather the full content of a document is contained in a Bundle, of which the Composition is the first resource contained. 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 document 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. While a Composition defines the structure, it does not actually contain the content: rather the full content of a document is contained in a Bundle, of which the Composition is the first resource contained. 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. 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. 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 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 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 code systems or data elements, or classes in class models. A statement of relationships from one set of concepts to one or more other concepts - either code systems or data elements, 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. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this concept map is (or will be) published. The URL SHOULD include the major version of the concept map. For more information see [Technical and Business Versions](resource.html#versions). 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 if and 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 individual or organization 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 terms 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. Explaination 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. The source value set that specifies the concepts that are being mapped. The target value set provides context to 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 code systems or data elements, or classes in class models. An absolute URI that identifies the Code System (if the source is a value set that crosses more than one code system). The specific version of the code system, as determined by the code system authority. An absolute URI that identifies the code system of the target code (if the target is a value set that cross code systems). 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 match in the mappings in the group. A statement of relationships from one set of concepts to one or more other concepts - either code systems or data elements, 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 code systems or data elements, 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 code systems or data elements, 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 somwhere 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 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 code systems or data elements, or classes in class models. Defines which action to take if there is no match in the group. One of 3 actions is 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 URL of the map to use if this map contains no mapping. 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 This records identifiers associated with this condition 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 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. Encounter during which the condition was first asserted. 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 date on which the existance of the Condition was first asserted or acknowledged. 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 on which this condition is suspected or confirmed. 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. 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. Provisional Differential Confirmed Refuted Entered In Error Unknown The verification status to support or decline the clinical status of the condition or diagnosis. If the element is present, it must have either a @value, an @id, or extensions Active Recurrence Inactive Remission Resolved The clinical status of the condition or diagnosis. If the element is present, it must have either a @value, an @id, or extensions A record of a healthcare consumer’s policy 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 policy 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 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. Relevant time or time-period when this Consent is applicable. 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. Who or what is controlled by this consent. Use group to identify a set of actors by some property they share (e.g. 'admitting officers'). Actions controlled by this consent. 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 referece to the specific computable policy. A set of security labels that define which resources are controlled by this consent. If more than one label is specified, all resources must have all the specified labels. The context of the activities a user is taking - why the user is accessing the data - that are controlled by this consent. Clinical or Operational Relevant period of time that bounds the data controlled by this consent. The resources controlled by this consent, if specific resources are referenced. 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 policy 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 consent. The resource that identifies the actor. To identify a 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 policy 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 policy 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. A record of a healthcare consumer’s policy 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 exception conditions are met. The timeframe in this exception is valid. Who or what is controlled by this Exception. Use group to identify a set of actors by some property they share (e.g. 'admitting officers'). Actions controlled by this Exception. A set of security labels that define which resources are controlled by this exception. If more than one label is specified, all resources must have all the specified labels. The context of the activities a user is taking - why the user is accessing the data - that are controlled by this exception. The class of information covered by this exception. 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 exception applies. Clinical or Operational Relevant period of time that bounds the data controlled by this exception. The resources controlled by this exception, if specific resources are referenced. A record of a healthcare consumer’s policy 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 a 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 policy 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. 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 Opt Out Opt In How an exception 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 A formal agreement between parties regarding the conduct of business, exchange of information or other matters. A formal agreement between parties regarding the conduct of business, exchange of information or other matters. If the element is present, it must have either a @value, an @id, or extensions Unique identifier for this Contract. The status of the resource instance. When this Contract was issued. Relevant time or time-period when this Contract is applicable. The target entity impacted by or of interest to parties to the agreement. The matter of concern in the context of this 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. Type of Contract such as an insurance policy, real estate contract, a will, power of attorny, Privacy or Security policy , trust framework agreement, etc. More specific type or specialization of an overarching or more general contract such as auto insurance, home owner insurance, prenupial agreement, Advanced-Directive, or privacy consent. Action stipulated by this Contract. Reason for action stipulated by this Contract. The type of decision made by a grantor with respect to an offer made by a grantee. The minimal content derived from the basal information source at a specific stage in its lifecycle. A set of security labels that define which resources are controlled by this consent. If more than one label is specified, all resources must have all the specified labels. An actor taking a role in an activity for which it can be assigned some degree of responsibility for the activity taking place. 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. Contract Valued Item List. One or more Contract Provisions, which may be related and conveyed as a group, and may contain nested groups. 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. 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. A formal agreement between parties regarding the conduct of business, exchange of information or other matters. Who or what parties are assigned roles in this Contract. Role type of agent assigned roles in this Contract. A formal agreement between parties regarding the conduct of business, exchange of information or other matters. 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. A formal agreement between parties regarding the conduct of business, exchange of information or other matters. 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. A formal agreement between parties regarding the conduct of business, exchange of information or other matters. Unique identifier for this particular Contract Provision. When this Contract Provision was issued. Relevant time or time-period when this Contract Provision is applicable. Type of Contract Provision such as specific requirements, purposes for actions, obligations, prohibitions, e.g. life time maximum benefit. Subtype of this Contract Provision, e.g. life time maximum payment for a contract term for specific valued item, e.g. disability payment. The matter of concern in the context of this provision of the agrement. Action stipulated by this Contract Provision. Reason or purpose for the action stipulated by this Contract Provision. A set of security labels that define which terms are controlled by this condition. An actor taking a role in an activity for which it can be assigned some degree of responsibility for the activity taking place. Human readable form of this Contract Provision. Contract Provision Valued Item List. Nested group of Contract Provisions. A formal agreement between parties regarding the conduct of business, exchange of information or other matters. The agent assigned a role in this Contract Provision. Role played by the agent assigned this role in the execution of this Contract Provision. A formal agreement between parties regarding the conduct of business, exchange of information or other matters. Specific type of Contract Provision Valued Item that may be priced. Identifies a Contract Provision Valued Item instance. Indicates the time during which this Contract Term ValuedItem information is effective. Specifies the units by which the Contract Provision Valued Item is measured or counted, and quantifies the countable or measurable Contract Term Valued Item instances. A Contract Provision Valued Item unit valuation measure. A real number that represents a multiplier used in determining the overall value of the Contract Provision 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 Provision Valued Item delivered. The concept of Points allows for assignment of point values for a Contract ProvisionValued Item, such that a monetary amount can be assigned to each point. Expresses the product of the Contract Provision 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. A formal agreement between parties regarding the conduct of business, exchange of information or other matters. Human readable rendering of this Contract in a format and representation intended to enhance comprehension and ensure understandability. A formal agreement between parties regarding the conduct of business, exchange of information or other matters. Contract legal text in human renderable form. A formal agreement between parties regarding the conduct of business, exchange of information or other matters. 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 Financial instrument which may be used to reimburse or pay for health care products and services. Financial instrument which may be used to reimburse or pay for health care products and services. If the element is present, it must have either a @value, an @id, or extensions The main (and possibly only) identifier for the coverage - often referred to as a Member Id, Certificate number, Personal Health Number or Case ID. May be constructed as the concatination of the Coverage.SubscriberID and the Coverage.dependant. 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, may be an individual, corporation or the subscriber's employer. 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 services are provided. 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. May provide multiple identifiers such as insurance company identifier or business identifier (BIN number). A suite of underwrite specific classifiers, for example may be used to identify a class of coverage or employer group, Policy, Plan. A unique identifier for a dependent under the coverage. An optional counter for a particular instance of the identified coverage which increments upon each renewal. The order of applicability of this coverage relative to other coverages which are currently inforce. Note, there may be gaps in the numbering and this does not imply primary, secondard 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. The policy(s) which constitute this insurance coverage. Financial instrument which may be used to reimburse or pay for health care products and services. Identifies a style or collective of coverage issued by the underwriter, for example may be used to identify an employer group. May also be referred to as a Policy or Group ID. A short description for the group. Identifies a style or collective of coverage issued by the underwriter, for example may be used to identify a subset of an employer group. A short description for the subgroup. Identifies a style or collective of coverage issued by the underwriter, for example may be used to identify a collection of benefits provided to employees. May be referred to as a Section or Division ID. A short description for the plan. Identifies a sub-style or sub-collective of coverage issued by the underwriter, for example may be used to identify a subset of a collection of benefits provided to employees. A short description for the subplan. Identifies a style or collective of coverage issues by the underwriter, for example may be used to identify a class of coverage such as a level of deductables or co-payment. A short description for the class. Identifies a sub-style or sub-collective of coverage issues by the underwriter, for example may be used to identify a subclass of coverage such as a sub-level of deductables or co-payment. A short description for the subclass. The formal description of a single piece of information that can be gathered and reported. The formal description of a single piece of information that can be gathered and reported. If the element is present, it must have either a @value, an @id, or extensions An absolute URI that is used to identify this data element when it is referenced in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this data element is (or will be) published. The URL SHOULD include the major version of the data element. For more information see [Technical and Business Versions](resource.html#versions). A formal identifier that is used to identify this data element 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 data element when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the data element 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. The status of this data element. Enables tracking the life-cycle of the content. A boolean value to indicate that this data element 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 data element was published. The date must change if and 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 data element changes. The name of the individual or organization that published the data element. A natural language name identifying the data element. 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 data element. 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 terms may be used to assist with indexing and searching for appropriate data element instances. A legal or geographic region in which the data element is intended to be used. A copyright statement relating to the data element and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the data element. Identifies how precise the data element is in its definition. Identifies a specification (other than a terminology) that the elements which make up the DataElement have some correspondence with. Defines the structure, type, allowed values and other constraining characteristics of the data element. The formal description of a single piece of information that can be gathered and reported. An internal id that is used to identify this mapping set when specific mappings are made on a per-element basis. 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. Comparable Fully Specified Equivalent Convertable Scaleable Flexible Indicates the degree of precision of the data element definition. 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 date-time 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. 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 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. 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 This resource identifies an instance or 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. Medical devices include durable (reusable) medical equipment, implantable devices, as well as disposable equipment used for diagnostic, treatment, and research for healthcare and public health. Non-medical devices may include items such as a machine, cellphone, computer, application, etc. This resource identifies an instance or 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. Medical devices include durable (reusable) medical equipment, implantable devices, as well as disposable equipment used for diagnostic, treatment, and research for healthcare and public health. Non-medical devices may include items such as a machine, cellphone, computer, application, etc. 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. [Unique device identifier (UDI)](device.html#5.11.3.2.2) assigned to device label or package. Status of the Device availability. Code or identifier to identify a kind of device. Lot number assigned by the manufacturer. 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). The "model" is an identifier assigned by the manufacturer to identify the product by its type. This number is shared by the all devices sold as the same type. The version of the device, if the device has multiple releases under the same model, or if the device is software or carries firmware. 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. This resource identifies an instance or 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. Medical devices include durable (reusable) medical equipment, implantable devices, as well as disposable equipment used for diagnostic, treatment, and research for healthcare and public health. Non-medical devices may include items such as a machine, cellphone, computer, application, etc. 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. Name of device as used in labeling or catalog. 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 as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device. 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. 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. A coded entry to indicate how the data was entered. 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 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 The locally assigned unique identification by the software. For example: handle ID. The component type as defined in the object-oriented or metric nomenclature partition. The timestamp for the most recent system change which includes device configuration or setting change. The link to the source Device that contains administrative device information such as manufacture, serial number, etc. The link to the parent resource. For example: Channel is linked to its VMD parent. The current operational status of the device. For example: On, Off, Standby, etc. The parameter group supported by the current device component that is based on some nomenclature, e.g. cardiovascular. The physical principle of the measurement. For example: thermal, chemical, acoustical, etc. The production specification such as component revision, serial number, etc. The language code for the human-readable text string produced by the device. This language code will follow the IETF language tag. Example: en-US. The characteristics, operational status and capabilities of a medical-related component of a medical device. The specification type, such as, serial number, part number, hardware revision, software revision, etc. The internal component unique identification. This is a provision for manufacture specific standard components using a private OID. 11073-10101 has a partition for private OID semantic that the manufacturer can make use of. The printable string defining the component. MSP Other MSP Chemical MSP Electrical MSP Impedance MSP Nuclear MSP Optical MSP Thermal MSP Biological MSP Mechanical MSP Acoustical MSP Manual Different measurement principle supported by the device. If the element is present, it must have either a @value, an @id, or extensions 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 Describes the unique identification of this metric that has been assigned by the device or gateway software. For example: handle ID. It should be noted that in order to make the identifier unique, the system element of the identifier should be set to the unique identifier of the device. 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 DeviceComponent 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 DeviceComponent 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. Protocol or definition followed by this request. For example: The proposed act must be performed if the indicated conditions occur, e.g.., shortness of breath, SpO2 less than x%. 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. 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 perfomer for doing the diagnostic testing. Reason or justification for the use of this device. Reason or justification for the use of this device. Additional clinical information about the patient that may influence the request fulfilment. For example, this may includes body where on the subject's 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. The device, practitioner, etc. who initiated the request. The organization the device or practitioner was acting on behalf of. 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 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. The time period over which the device was used. 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 the site on the subject's body where the device was used ( i.e. the target site). 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 a 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 test or procedure requested. The status of the diagnostic report as a whole. 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 per 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 released from the source diagnostic service. Indicates who or what participated in producing the report. Details about the specimens on which this diagnostic report is based. Observations that are part of this diagnostic report. Observations can be simple name/value pairs (e.g. "atomic" results), or they can be grouping observations that include references to other members of the group (e.g. "panels"). 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 impression / summary of the diagnostic report. Codes for the conclusion. 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. Describes the type of participation (e.g. a responsible party, author, or verifier). The reference to the practitioner or organization involved in producing the report. For example, the diagnostic service that is responsible for issuing the report. 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 as a whole. 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. Specifies the kind of this set of documents (e.g. Patient Summary, Discharge Summary, Prescription, etc.). The type of a set of documents may be the same as one of the documents in it - especially if there is only one - but it may be wider. 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 responsible for creating the manifest, and adding documents to it. 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 Documents included in the 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. The list of references to document content, or Attachment that consist of the parts of this document manifest. Usually, these would be document references, but direct references to Media or Attachments are also allowed. 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, ProcedureRequest, Procedure, EligibilityRequest, etc. A reference to a document. A reference to a document. 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 was created. 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. This is sometimes known as the "title". 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. The type of relationship that this document has with anther document. The target document of this relationship. A reference to a document. 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. 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 typeCode, 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. A reference to a document. Related identifier to this DocumentReference. If both id and ref are present they shall refer to the same thing. Related Resource to this DocumentReference. If both id and ref are present they shall refer to the same thing. The EligibilityRequest provides patient and insurance coverage information to an insurer for them to respond, in the form of an EligibilityResponse, with information regarding whether the stated coverage is valid and in-force and optionally to provide the insurance details of the policy. The EligibilityRequest provides patient and insurance coverage information to an insurer for them to respond, in the form of an EligibilityResponse, 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 The Response business identifier. The status of the resource instance. Immediate (STAT), best effort (NORMAL), deferred (DEFER). Patient Resource. 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 invoice/claim/pre-determination or pre-authorization. The practitioner who is responsible for the services rendered to the patient. The organization which is responsible for the services rendered to the patient. The Insurer who is target of the request. Facility where the services were provided. Financial instrument by which payment information for health care. The contract number of a business agreement which describes the terms and conditions. Dental, Vision, Medical, Pharmacy, Rehab etc. Dental: basic, major, ortho; Vision exam, glasses, contacts; etc. This resource provides eligibility and plan details from the processing of an Eligibility resource. This resource provides eligibility and plan details from the processing of an Eligibility 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. The date when the enclosed suite of services were performed or completed. The practitioner who is responsible for the services rendered to the patient. The organization which is responsible for the services rendered to the patient. Original request resource reference. Transaction status: error, complete. A description of the status of the adjudication. The Insurer who produced this adjudicated response. 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 insurer may provide both the details for the requested coverage as well as details for additional coverages known to the insurer. The form to be used for printing the content. Mutually exclusive with Services Provided (Item). This resource provides eligibility and plan details from the processing of an Eligibility resource. A suite of updated or additional Coverages from the Insurer. The contract resource which may provide more detailed information. Benefits and optionally current balances by Category. This resource provides eligibility and plan details from the processing of an Eligibility resource. Dental, Vision, Medical, Pharmacy, Rehab etc. Dental: basic, major, ortho; Vision exam, glasses, contacts; etc. True if the indicated class of service is excluded from the plan, missing or False indicated the service is included in the coverage. A short name or tag for the benefit, for example MED01, or DENT2. A richer description of the benefit, for example 'DENT2 covers 100% of basic, 50% of major but exclused Ortho, Implants and Costmetic services'. Network designation. Unit designation: individual or family. The term or period of the values such as 'maximum lifetime benefit' or 'maximum annual vistis'. Benefits Used to date. This resource provides eligibility and plan details from the processing of an Eligibility resource. Deductable, visits, benefit amount. Benefits allowed. Benefits used. This resource provides eligibility and plan details from the processing of an Eligibility resource. An error code,from a specified code system, which details why the eligibility check could not be performed. 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. inpatient | outpatient | ambulatory | emergency +. 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 transisions 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 kindof discharge from emergency to inpatient. Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation). Indicates the urgency of the encounter. The patient ro 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 referral request this encounter satisfies (incoming referral). 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. 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. An organization that is in charge of maintaining the information of this Encounter (e.g. who maintains the report or the master service catalog item, etc.). This MAY be the same as the organization on the Patient record, however it could be different. This MAY not be not the Service Delivery Location's Organization. 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 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 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 is no longer at the location, then the period will have an end date/time. 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 organisation is hosting this in the cloud, it is the organisation 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. The organization which 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 Enrollment resource. This resource provides enrollment and plan details from the processing of an Enrollment 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. The organization which 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 co-ordinator 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 Resource to define constraints on the Expansion of a FHIR ValueSet. Resource to define constraints on the Expansion of a FHIR ValueSet. If the element is present, it must have either a @value, an @id, or extensions An absolute URI that is used to identify this expansion profile when it is referenced in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this expansion profile is (or will be) published. The URL SHOULD include the major version of the expansion profile. For more information see [Technical and Business Versions](resource.html#versions). A formal identifier that is used to identify this expansion profile 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 expansion profile when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the expansion profile 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 expansion profile. This name should be usable as an identifier for the module by machine processing applications such as code generation. The status of this expansion profile. Enables tracking the life-cycle of the content. A boolean value to indicate that this expansion profile 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 expansion profile was published. The date must change if and 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 expansion profile changes. The name of the individual or organization that published the expansion profile. Contact details to assist a user in finding and communicating with the publisher. A free text natural language description of the expansion profile from a consumer's perspective. The content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching for appropriate expansion profile instances. A legal or geographic region in which the expansion profile is intended to be used. Fix use of a particular code system to a particular version. Code system, or a particular version of a code system to be excluded from value set expansions. Controls whether concept designations are to be included or excluded in value set expansions. A set of criteria that provide the constraints imposed on the value set expansion by including or excluding designations. Controls whether the value set definition is included or excluded in value set expansions. Controls whether inactive concepts are included or excluded in value set expansions. Controls whether or not the value set expansion nests codes or not (i.e. ValueSet.expansion.contains.contains). Controls whether or not the value set expansion includes codes which cannot be displayed in user interfaces. Controls whether or not the value set expansion includes post coordinated codes. Specifies the language to be used for description in the expansions i.e. the language to be used for ValueSet.expansion.contains.display. If the value set being expanded is incomplete (because it is too big to expand), return a limited expansion (a subset) with an indicator that expansion is incomplete, using the extension [http://hl7.org/fhir/StructureDefinition/valueset-toocostly](extension-valueset-toocostly.html). Resource to define constraints on the Expansion of a FHIR ValueSet. The specific system for which to fix the version. The version of the code system from which codes in the expansion should be included. How to manage the intersection between a fixed version in a value set, and this fixed version of the system in the expansion profile. Resource to define constraints on the Expansion of a FHIR ValueSet. An absolute URI which is the code system to be excluded. The version of the code system from which codes in the expansion should be excluded. Resource to define constraints on the Expansion of a FHIR ValueSet. Designations to be included. Designations to be excluded. Resource to define constraints on the Expansion of a FHIR ValueSet. A data group for each designation to be included. Resource to define constraints on the Expansion of a FHIR ValueSet. The language this designation is defined for. Which kinds of designation to include in the expansion. Resource to define constraints on the Expansion of a FHIR ValueSet. A data group for each designation to be excluded. Resource to define constraints on the Expansion of a FHIR ValueSet. The language this designation is defined for. Which kinds of designation to exclude from the expansion. Default Version Check ValueSet Version Override ValueSet Version How to manage the intersection between a fixed version in a value set, and a fixed version of the system in the expansion profile 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 The EOB Business Identifier. The status of the resource instance. The category of claim, eg, oral, pharmacy, vision, insitutional, professional. A finer grained suite of claim subtype codes which may convey Inpatient vs Outpatient and/or a specialty service. In the US the BillType. Patient Resource. The billable period for which charges are being submitted. The date when the EOB was created. The person who created the explanation of benefit. The insurer which is responsible for the explanation of benefit. The provider which is responsible for the claim. The provider which is responsible for the claim. The referral resource which lists the date, practitioner, reason and other supporting information. Facility where the services were provided. The business identifier for the instance: invoice number, claim number, pre-determination or pre-authorization number. The business identifier for the instance: invoice number, claim number, pre-determination or pre-authorization number. Processing outcome errror, partial or complete processing. A description of the status of the adjudication. Other claims which are related to this claim such as prior claim versions or for related services. Prescription to support the dispensing of Pharmacy or Vision products. Original prescription which has been superceded by this prescription to support the dispensing of pharmacy services, medications or products. For example, a physician may prescribe a medication which the pharmacy determines is contraindicated, or for which the patient has an intolerance, and therefor issues a new precription for an alternate medication which has the same theraputic intent. The prescription from the pharmacy becomes the 'prescription' and that from the physician becomes the 'original prescription'. The party to be reimbursed for the services. Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. Often there are mutiple jurisdiction specific valuesets which are required. The members of the team who provided the overall service as well as their role and whether responsible and qualifications. Ordered list of patient diagnosis for which care is sought. Ordered list of patient procedures performed to support the adjudication. Precedence (primary, secondary, etc.). Financial instrument by which payment information for health care. An accident which resulted in the need for healthcare services. The start and optional end dates of when the patient was precluded from working due to the treatable condition(s). The start and optional end dates of when the patient was confined to a treatment center. First tier of goods and services. The first tier service adjudications for payor added services. The total cost of the services reported. The amount of deductable applied which was not allocated to any particular service line. Total amount of benefit payable (Equal to sum of the Benefit amounts from all detail lines and additions less the Unallocated Deductable). Payment details for the claim if the claim has been paid. The form to be used for printing the content. Note text. 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. Other claims which are related to this claim such as prior claim versions or for related services. For example prior or umbrella. An alternate organizational reference to the case or file to which this particular claim pertains - eg Property/Casualy insurer claim # or Workers Compensation case # . 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. organization | patient | practitioner | relatedperson. Party to be reimbursed: Subscriber, provider, other. 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. Sequence of the information element which serves to provide a link. 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 which may influence the adjudication. 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. For example, provides the reason for: the additional stay, or missing tooth or any other 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. Sequence of careteam which serves to order and provide a link. The members of the team who provided the overall service. The practitioner who is billing and responsible for the claimed services rendered to the patient. The lead, assisting or supervising practitioner and their discipline if a multidisiplinary team. The qualification 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. Sequence of diagnosis which serves to provide a link. The diagnosis. The type of the Diagnosis, for example: admitting, primary, secondary, discharge. The package billing code, for example DRG, based on the assigned 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. Sequence of procedures which serves to order and provide a link. Date and optionally time the procedure was performed . The procedure code. 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 the program or plan identification, underwriter or payor. A list of references from the Insurer to which these services pertain. 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 which these services are addressing. Type of accident: work, auto, etc. Where the accident occurred. 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 service line number. Careteam applicable for this service or product line. Diagnosis applicable for this service or product line. Procedures applicable for this service or product line. Exceptions, special conditions and supporting information pplicable for this service or product line. The type of reveneu or cost center providing the product and/or service. Health Care Service Type Codes to identify the classification of service or benefits. If this is an actual service or product line, ie. not a Group, then use code to indicate the Professional Service or Product supplied (eg. CTP, HCPCS,USCLS,ICD10, NCPDP,DIN,ACHI,CCI). If a grouping item then use a group code to indicate the type of thing being grouped eg. 'glasses' or 'compound'. Item typification or modifiers codes, eg for Oral whether the treatment is cosmetic or associated with TMJ, or for medical whether the treatment was outside the clinic or out of office hours. For programs which require reson codes for the inclusion, covering, of this billed item under the program or sub-program. The date or dates when the enclosed suite of services were performed or completed. Where the service was provided. The number of repetitions of a service or product. If the item is a node then this is the fee for the product or service, otherwise this is the total of the fees for the children 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 addittional service or product or charge. 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. List of Unique Device Identifiers associated with this line item. Physical service site on the patient (limb, tooth, etc). A region or surface of the site, eg. limb region or tooth surface(s). A billed item may include goods or services provided in multiple encounters. A list of note references to the notes provided below. The adjudications results. 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. Code indicating: Co-Pay, deductable, elegible, benefit, tax, etc. Adjudication reason such as limit reached. Monitory amount associated with the code. A non-monetary value for example a percentage. 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 service line number. The type of product or service. The type of reveneu or cost center providing the product and/or service. Health Care Service Type Codes to identify the classification of service or benefits. If this is an actual service or product line, ie. not a Group, then use code to indicate the Professional Service or Product supplied (eg. CTP, HCPCS,USCLS,ICD10, NCPDP,DIN,ACHI,CCI). If a grouping item then use a group code to indicate the type of thing being grouped eg. 'glasses' or 'compound'. Item typification or modifiers codes, eg for Oral whether the treatment is cosmetic or associated with TMJ, or for medical whether the treatment was outside the clinic or out of office hours. For programs which require reson codes for the inclusion, covering, of this billed item under the program or sub-program. The number of repetitions of a service or product. If the item is a node then this is the fee for the product or service, otherwise this is the total of the fees for the children 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 addittional service or product or charge. 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. List of Unique Device Identifiers associated with this line item. A list of note references to the notes provided below. The adjudications 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 service line number. The type of product or service. The type of reveneu or cost center providing the product and/or service. Health Care Service Type Codes to identify the classification of service or benefits. A code to indicate the Professional Service or Product supplied (eg. CTP, HCPCS,USCLS,ICD10, NCPDP,DIN,ACHI,CCI). Item typification or modifiers codes, eg for Oral whether the treatment is cosmetic or associated with TMJ, or for medical whether the treatment was outside the clinic or out of office hours. For programs which require reson codes for the inclusion, covering, of this billed item under the program or sub-program. The number of repetitions of a service or product. The fee for an addittional service or product or charge. 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 addittional service or product or charge. 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. List of Unique Device Identifiers associated with this line item. A list of note references to the notes provided below. The adjudications 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. List of input service items which this service line is intended to replace. The type of reveneu or cost center providing the product and/or service. Health Care Service Type Codes to identify the classification of service or benefits. If this is an actual service or product line, ie. not a Group, then use code to indicate the Professional Service or Product supplied (eg. CTP, HCPCS,USCLS,ICD10, NCPDP,DIN,ACHI,CCI). If a grouping item then use a group code to indicate the type of thing being grouped eg. 'glasses' or 'compound'. Item typification or modifiers codes, eg for Oral whether the treatment is cosmetic or associated with TMJ, or for medical whether the treatment was outside the clinic or out of office hours. The fee charged for the professional service or product. A list of note references to the notes provided below. The adjudications 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. The type of reveneu or cost center providing the product and/or service. Health Care Service Type Codes to identify the classification of service or benefits. A code to indicate the Professional Service or Product supplied (eg. CTP, HCPCS,USCLS,ICD10, NCPDP,DIN,ACHI,CCI). Item typification or modifiers codes, eg for Oral whether the treatment is cosmetic or associated with TMJ, or for medical whether the treatment was outside the clinic or out of office hours. The fee charged for the professional service or product. A list of note references to the notes provided below. The adjudications 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. Whether this represents partial or complete payment of the claim. Adjustment to the payment of this transaction which is not related to adjudication of this transaction. Reason for the payment adjustment. Estimated payment date. Payable less any payment adjustment. Payment identifer. 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. An integer associated with each note which may be referred to from each service line item. The note purpose: Print/Display. The note text. 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. 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. Dental, Vision, Medical, Pharmacy, Rehab etc. Dental: basic, major, ortho; Vision exam, glasses, contacts; etc. True if the indicated class of service is excluded from the plan, missing or False indicated the service is included in the coverage. A short name or tag for the benefit, for example MED01, or DENT2. A richer description of the benefit, for example 'DENT2 covers 100% of basic, 50% of major but exclused Ortho, Implants and Costmetic services'. Network designation. Unit designation: individual or family. The term or period of the values such as 'maximum lifetime benefit' or 'maximum annual vistis'. 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. Deductable, visits, benefit amount. Benefits allowed. Benefits used. 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 events and conditions for a person related to the patient relevant in the context of care for the patient. Significant health events and 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 This records identifiers associated with this family member history record 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). A protocol or questionnaire that was adhered to in whole or in part by this event. A code specifying the status of the record of the family history of a specific family member. If true, indicates the taking of an individual family member's history did not occur. The notDone element should not be used to document negated conditions, such as a family member that did not have a condition. Describes why the family member's history is absent. The person who this history concerns. The date (and possibly time) when the family member history was taken. 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.). Administrative Gender - the gender that the relative is considered to have for administration and record keeping purposes. 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 events and 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 as a result of this condition. If the condition resulted in death, deceased date is captured on the relation. 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 Identifier assigned to the flag for external use (outside the FHIR environment). Supports basic workflow. Allows an 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 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 This records identifiers associated with this care plan 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). Indicates whether the goal has been reached and is still considered relevant. 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 Accepted Planned In Progress On Target Ahead of Target Behind Target Sustaining Achieved On Hold Cancelled Entered In Error Rejected Indicates whether the goal has been met and 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. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this graph definition is (or will be) published. The URL SHOULD include the major version of the graph definition. For more information see [Technical and Business Versions](resource.html#versions). 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 if and 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 individual or organization 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 terms 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. Explaination 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. Path in the resource that contains the link. 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. 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. Identifies the compartment. identical | matching | different | no-rule | custom. Custom rule, as a FHIRPath expression. Documentation for FHIRPath expression. 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. Identifies the traits 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. 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 id of the request associated with this response. If an id 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 a unique, business identifier for the response. A reference to the knowledge module that was invoked. 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. Allows the context of the guidance response to be provided if available. In a service context, this would likely be unavailable. Indicates when the guidance response was processed. Provides a reference to the device that performed the guidance. 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. Whether this healthcareservice record is in active use. 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? Describes the eligibility conditions for the service. Program Names that can be used to categorize the service. Collection of characteristics (attributes). 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. 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 A text description of the DICOM SOP instances selected in the ImagingManifest; or the reason for, or significance of, the selection. A text description of the DICOM SOP instances selected in the ImagingManifest; or the reason for, or significance of, the selection. If the element is present, it must have either a @value, an @id, or extensions Unique identifier of the DICOM Key Object Selection (KOS) that this resource represents. A patient resource reference which is the patient subject of all DICOM SOP Instances in this ImagingManifest. Date and time when the selection of the referenced instances were made. It is (typically) different from the creation date of the selection resource, and from dates associated with the referenced instances (e.g. capture time of the referenced image). Author of ImagingManifest. It can be a human author or a device which made the decision of the SOP instances selected. For example, a radiologist selected a set of imaging SOP instances to attach in a diagnostic report, and a CAD application may author a selection to describe SOP instances it used to generate a detection conclusion. Free text narrative description of the ImagingManifest. The value may be derived from the DICOM Standard Part 16, CID-7010 descriptions (e.g. Best in Set, Complete Study Content). Note that those values cover the wide range of uses of the DICOM Key Object Selection object, several of which are not supported by ImagingManifest. Specifically, there is no expected behavior associated with descriptions that suggest referenced images be removed or not used. Study identity and locating information of the DICOM SOP instances in the selection. A text description of the DICOM SOP instances selected in the ImagingManifest; or the reason for, or significance of, the selection. Study instance UID of the SOP instances in the selection. Reference to the Imaging Study in FHIR form. 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.type. Series identity and locating information of the DICOM SOP instances in the selection. A text description of the DICOM SOP instances selected in the ImagingManifest; or the reason for, or significance of, the selection. Series instance UID of the SOP instances in the selection. 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.type. Identity and locating information of the selected DICOM SOP instances. A text description of the DICOM SOP instances selected in the ImagingManifest; or the reason for, or significance of, the selection. SOP class UID of the selected instance. SOP Instance UID of the selected instance. 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 Formal identifier for the study. Accession Number is an identifier related to some aspect of imaging workflow and data management. Usage may vary across different institutions. See for instance [IHE Radiology Technical Framework Volume 1 Appendix A](http://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_TF_Rev13.0_Vol1_FT_2014-07-30.pdf). Other identifiers for the study. Availability of study (online, offline, or nearline). A list of all the Series.ImageModality 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 patient imaged in the study. The encounter or episode at which the request is initiated. 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.type. 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. A reference to the performed Procedure. The code for the performed procedure type. Description of clinical condition indicating why the ImagingStudy was requested. Institution-generated description or classification of the Study 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. Formal identifier for this 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. Availability of series (online, offline or nearline). 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.type. 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 date and time the series was started. The physician or operator (often the radiology technician) who performed the series. The performer is recorded at the series level, since each series in a study may be performed by a different practitioner, at different times, and using different devices. A series may be performed by multiple practitioners. 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. Formal identifier for this image or other content. The number of instance in the series. DICOM instance type. The description of the instance. Online Offline Nearline Unavailable Availability of the resource If the element is present, it must have either a @value, an @id, or extensions Describes the event of a patient being administered a vaccination or a record of a vaccination as reported by a patient, a clinician or another party and may include vaccine reaction information and what vaccination protocol was followed. Describes the event of a patient being administered a vaccination or a record of a vaccination as reported by a patient, a clinician or another party and may include vaccine reaction information and what vaccination protocol was followed. 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 vaccination event. Indicates if the vaccination was or was not given. 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. 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 or what performed the event. Extra information about the immunization that is not conveyed by the other attributes. Reasons why a vaccine was or was not administered. Categorical data indicating that an adverse event is associated in time to an immunization. Contains information about the protocol(s) under which the vaccine was administered. Describes the event of a patient being administered a vaccination or a record of a vaccination as reported by a patient, a clinician or another party and may include vaccine reaction information and what vaccination protocol was followed. Describes the type of performance (e.g. ordering provider, administering provider, etc.). The device, practitioner, etc. who performed the action. Describes the event of a patient being administered a vaccination or a record of a vaccination as reported by a patient, a clinician or another party and may include vaccine reaction information and what vaccination protocol was followed. Reasons why a vaccine was administered. Reason why a vaccine was not administered. Describes the event of a patient being administered a vaccination or a record of a vaccination as reported by a patient, a clinician or another party and may include vaccine reaction information and what vaccination protocol was followed. Date of reaction to the immunization. Details of the reaction. Self-reported indicator. Describes the event of a patient being administered a vaccination or a record of a vaccination as reported by a patient, a clinician or another party and may include vaccine reaction information and what vaccination protocol was followed. Nominal position in a series. Contains the description about the protocol under which the vaccine was administered. Indicates the authority who published the protocol. E.g. ACIP. One possible path to achieve presumed immunity against a disease - within the context of an authority. The recommended number of doses to achieve immunity. The targeted disease. Indicates if the immunization event should "count" against the protocol. Provides an explanation as to why an immunization event should or should not count against the protocol. Completed Entered in Error 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 A patient's point-in-time immunization and recommendation (i.e. forecasting a patient's immunization eligibility according to a published schedule) with optional supporting justification. A patient's point-in-time immunization and recommendation (i.e. forecasting a patient's immunization eligibility 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 recommendations are for. Vaccine administration recommendations. A patient's point-in-time immunization and recommendation (i.e. forecasting a patient's immunization eligibility according to a published schedule) with optional supporting justification. The date the immunization recommendation was created. Vaccine that pertains to the recommendation. The targeted disease for the recommendation. The next recommended dose number (e.g. dose 2 is the next recommended dose). Vaccine administration status. Vaccine date recommendations. For example, earliest date to administer, latest date to administer, etc. Contains information about the protocol under which the vaccine was administered. Immunization event history 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 immunization and recommendation (i.e. forecasting a patient's immunization eligibility 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 patient's point-in-time immunization and recommendation (i.e. forecasting a patient's immunization eligibility according to a published schedule) with optional supporting justification. Indicates the nominal position in a series of the next dose. This is the recommended dose number as per a specified protocol. Contains the description about the protocol under which the vaccine was administered. Indicates the authority who published the protocol. For example, ACIP. One possible path to achieve presumed immunity against a disease - within the context of an authority. A set of rules of how FHIR is used to solve a particular problem. 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 FHIR is used to solve a particular problem. 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. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this implementation guide is (or will be) published. The URL SHOULD include the major version of the implementation guide. For more information see [Technical and Business Versions](resource.html#versions). 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. 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 if and 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 individual or organization 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 terms 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 version of the FHIR specification on which this ImplementationGuide is based - this is the formal version of the specification, without the revision number, e.g. [publication].[major].[minor], which is 3.0.1 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 logical group of resources. Logical groups can be used when building pages. A set of profiles that all resources covered by this implementation guide must conform to. A binary file that is included in the implementation guide when it is published. A page / section in the implementation guide. The root page is the implementation guide home page. A set of rules of how FHIR is used to solve a particular problem. 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. How the dependency is represented when the guide is published. Where the dependency is located. A set of rules of how FHIR is used to solve a particular problem. 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 name for the group, as used in page.package. Human readable text describing the package. 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 set of rules of how FHIR is used to solve a particular problem. 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. Whether a resource is included in the guide as part of the rules defined by the guide, or just as an example of a resource that conforms to the rules and/or help implementers understand the intent of the guide. 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. A short code that may be used to identify the resource throughout the implementation guide. Where this resource is found. Another resource that this resource is an example for. This is mostly used for resources that are included as examples of StructureDefinitions. A set of rules of how FHIR is used to solve a particular problem. 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 FHIR is used to solve a particular problem. 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. The kind of page that this is. Some pages are autogenerated (list, example), and other kinds are of interest so that tools can navigate the user to the page of interest. For constructed pages, what kind of resources to include in the list. For constructed pages, a list of packages to include in the page (or else empty for everything). The format of the page. Nested Pages/Sections under this page. Reference Inclusion How a dependency is represented when the guide is published. If the element is present, it must have either a @value, an @id, or extensions Page Example List Include Directory Dictionary Table Of Contents Resource The kind of an included page. 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. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this library is (or will be) published. The URL SHOULD include the major version of the library. For more information see [Technical and Business Versions](resource.html#versions). 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. 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. The date (and optionally time) when the library was published. The date must change if and 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 individual or organization that published the library. A free text natural language description of the library from a consumer's perspective. Explaination 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. 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 doesn't change the original approval date. The period during which the library content was or is planned to be in active use. The content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching for appropriate library instances. A legal or geographic region in which the library is intended to be used. 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. A contributor to the content of the library, including authors, editors, reviewers, and endorsers. Contact details to assist a user in finding and communicating with the publisher. 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. 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 are referring to the same real-world "occurrence". Identifies two or more records (resource instances) that are referring 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 and who establishes the context for evaluating the nature of each linkage. Identifies one of the records that is considered to refer to the same real-world occurrence as well as how the items hould be evaluated within the collection of linked items. Identifies two or more records (resource instances) that are referring 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 set of information summarized from a list of other resources. A set of information summarized from a list of other 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 set of information summarized from a list of other 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/chair/etc such as an isolation unit/dialisys 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 which this Location is physically part of. 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). 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. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this measure is (or will be) published. The URL SHOULD include the major version of the measure. For more information see [Technical and Business Versions](resource.html#versions). 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. 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 date (and optionally time) when the measure was published. The date must change if and 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 individual or organization that published the measure. A free text natural language description of the measure from a consumer's perspective. Explaination of why this measure is needed and why it has been designed as it has. A detailed description of how the measure is used from a clinical perspective. 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 doesn't change the original approval date. The period during which the measure content was or is planned to be in active use. The content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching for appropriate measure instances. A legal or geographic region in which the measure is intended to be used. Descriptive topics related to the content of the measure. Topics provide a high-level categorization of the type of the measure that can be useful for filtering and searching. A contributor to the content of the measure, including authors, editors, reviewers, and endorsers. Contact details to assist a user in finding and communicating with the publisher. 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. 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 succint 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 whthin 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. The measure set, e.g. Preventive Care and Screening. 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. A unique identifier for the group. This identifier will used to report data for the group in the measure report. Optional name or short description of this group. 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. A unique identifier for the population criteria. This identifier is used to report data against this criteria within the measure report. The type of population criteria. Optional name or short description of this population. The human readable description of this population criteria. The name of a valid referenced CQL expression (may be namespaced) that defines this population criteria. The Measure resource provides the definition of a quality measure. The identifier for the stratifier used to coordinate the reported data back to this stratifier. The criteria for the stratifier. This must be the name of an expression defined within a referenced library. The path to an element that defines the stratifier, specified as a valid FHIR resource path. The Measure resource provides the definition of a quality measure. An identifier for the supplemental data. 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 criteria for the supplemental data. This must be the name of a valid expression defined within a referenced library, and defines the data to be returned for this element. The supplemental data to be supplied as part of the measure response, specified as a valid FHIR Resource Path. The MeasureReport resource contains the results of evaluating a measure. The MeasureReport resource contains the results of evaluating a measure. If the element is present, it must have either a @value, an @id, or extensions A formal identifier that is used to identify this report when it is represented in other formats, or referenced in a specification, model, design or an instance. The report status. No data will be available until the report status is complete. The type of measure report. This may be an individual report, which provides a single patient's score for the measure; a patient listing, which returns the list of patients that meet the various criteria in the measure; or a summary report, which returns a population count for each of the criteria in the measure. A reference to the Measure that was evaluated to produce this report. Optional Patient if the report was requested for a single patient. The date this measure report was generated. Reporting Organization. The reporting period for which the report was calculated. 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 evaluation of this report. The MeasureReport resource contains the results of evaluating a measure. The identifier 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 evaluating a measure. The identifier of the population being reported, as defined by the population element of the measure. The type of the population. The number of members of the population. This element refers to a List of patient level MeasureReport resources, one for each patient in this population. The MeasureReport resource contains the results of evaluating a measure. The identifier 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 evaluating a measure. The value for this stratum, expressed as a string. When defining stratifiers on complex values, the value must be rendered such that the value for each stratum within the stratifier is unique. 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 evaluating a measure. The identifier of the population being reported, as defined by the population element of the measure. The type of the population. The number of members of the population in this stratum. This element refers to a List of patient level MeasureReport resources, one for each patient 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 Patient List Summary 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. Whether the media is a photo (still image), an audio recording, or a video recording. 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 or episode of care that establishes the context for this media. The date and time(s) at which the media was collected. 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 media was collected (i.e. the target site). 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. Photo Video Audio Whether the media is a photo, video, or audio If the element is present, it must have either a @value, an @id, or extensions This resource is primarily used for the identification and definition of a medication. It covers the ingredients and the packaging for a medication. This resource is primarily used for the identification and definition of a medication. It covers the ingredients and the packaging for a medication. If the element is present, it must have either a @value, an @id, or extensions 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. Set to true if the item is attributable to a specific manufacturer. Set to true if the medication can be obtained without an order from a prescriber. 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. Identifies a particular constituent of interest in the product. Information that only applies to packages (not products). Photo(s) or graphic representation(s) of the medication. This resource is primarily used for the identification and definition of a medication. It covers the ingredients and the packaging for a medication. 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. This resource is primarily used for the identification and definition of a medication. It covers the ingredients and the packaging for a medication. The kind of container that this package comes as. A set of components that go to make up the described item. Information about a group of medication produced or packaged from one production run. This resource is primarily used for the identification and definition of a medication. It covers the ingredients and the packaging for a medication. Identifies one of the items in the package. The amount of the product that is in the package. This resource is primarily used for the identification and definition of a medication. It covers the ingredients and the packaging for a medication. 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 External identifier - FHIR will generate its own internal identifiers (probably URLs) which do not need to be explicitly managed by the resource. The identifier here is one that would be used by another non-FHIR system - for example an automated medication pump would provide a record each time it operated; an administration while the patient was off the ward might be made with a different system and entered after the event. Particularly important if these records have to be updated. 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. Indicates the type of medication administration and 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 the medication administration was performed as part of. 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. The individual who was responsible for giving the medication to the patient. Set this to true if the record is saying that the medication was NOT administered. A code indicating why the administration was not performed. 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. The device, practitioner, etc. who performed the action. The organization the device or practitioner was acting on behalf of. 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. In Progress On Hold Completed Entered in Error Stopped Unknown A set of codes indicating the current status of a MedicationAdministration. If the element is present, it must have either a @value, an @id, or extensions 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 Identifier assigned by the dispensing facility - this is an identifier assigned outside FHIR. The procedure that the dispense is done because of. A code specifying the state of the set of dispense events. Indicates type of medication dispense and 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. 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. It should be assumed that the performer is the dispenser of the medication. 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. True if the dispense was not performed for some reason. Indicates the reason why a dispense was not performed. 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. The device, practitioner, etc. who performed the action. It should be assumed that the actor is the dispenser of the medication. The organization the device or practitioner was acting on behalf of. 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 of (or lack of substitution) from what was prescribed. The person or organization that has primary responsibility for the substitution. Preparation In Progress On Hold Completed Entered in-Error Stopped A coded concept specifying the state of the dispense event. If the element is present, it must have either a @value, an @id, or extensions 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 This records 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. For example a re-imbursement system might issue its own id for each prescription that is created. This is particularly important where FHIR only provides part of an entire workflow process where records must be tracked through an entire system. Protocol or definition followed by this request. 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. A code specifying the current state of the order. Generally this will be active or completed state. Whether the request is a proposal, plan, or an original order. Indicates the type of medication order and where the medication is expected to be consumed or administered. Indicates how quickly the Medication Request should be addressed with respect to other requests. 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. A link to an encounter, or episode of care, that identifies the particular occurrence or set occurrences of contact between patient and health care provider. 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 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 the medication. Condition or observation that supports why the medication was ordered. 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. The healthcare professional responsible for authorizing the initial prescription. The organization the device or practitioner was acting on behalf of. 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. 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. 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. 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 Routine Urgent Stat ASAP 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 Proposal Plan Order Instance Order 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 External identifier - FHIR will generate its own internal identifiers (probably URLs) which do not need to be explicitly managed by the resource. The identifier here is one that would be used by another non-FHIR system - for example an automated medication pump would provide a record each time it operated; an administration while the patient was off the ward might be made with a different system and entered after the event. Particularly important if these records have to be updated. 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. The encounter or episode of care that establishes the context for this MedicationStatement. 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. Indicates where type of medication statement and 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 interval of time during which it is being asserted that the patient was taking the medication (or was not taking, when the wasNotGiven element is true). 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. The person, animal or group who is/was taking the medication. Allows linking the MedicationStatement to the underlying MedicationRequest, or to other information that supports or is used to derive the MedicationStatement. Indicator of the certainty of whether the medication was taken by the patient. A code indicating why the medication was not taken. 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. Active Completed Entered in Error Intended Stopped On Hold A coded concept indicating the current status of a MedicationStatement. If the element is present, it must have either a @value, an @id, or extensions Yes No Unknown Not Applicable A coded concept identifying level of certainty if patient has taken or has not taken the medication If the element is present, it must have either a @value, an @id, or extensions 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 An absolute URI that is used to identify this message definition when it is referenced in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this message definition is (or will be) published. The URL SHOULD include the major version of the message definition. For more information see [Technical and Business Versions](resource.html#versions). 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. 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 if and 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 individual or organization 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 terms 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. Explaination 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. A MessageDefinition that is superseded by this definition. A coded identifier of a supported messaging event. 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. Indicates whether a response is required for this message. Indicates what types of messages may be sent as an application-level response to this message. 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). 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://hl7.org/fhir/message-events". The destination application which the message is intended for. Allows data conveyed by a message to be addressed to a particular person or department when routing to a specific application isn't sufficient. Identifies the sending system to allow the use of a trust relationship. The time that the message was sent. 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. 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. 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 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 if and 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 individual or organization 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 terms 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. For naming systems that are retired, indicates the naming system that should be used in their place (if any). 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 workflow status of the nutrition order/request. 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 modifiers about the type of food 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. 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. Proposed Draft Planned Requested Active On-Hold Completed Cancelled Entered in Error Codes specifying the state of the request. Describes the lifecycle of the nutrition order. If the element is present, it must have either a @value, an @id, or extensions 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. 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 whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed. Comments: Indirect characteristics may be those of a specimen, fetus, donor, other observer (for example a relative or EMT), or any observation made about the subject. 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 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. The assessment made based on the result of the observation. Intended as a simple compact code often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Otherwise known as abnormal flag. May include statements about significant, unexpected or unreliable values, or information about the source of the value where this may be relevant to the interpretation of the result. 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. A reference to another resource (usually another Observation) whose relationship is defined by the relationship type code. 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. 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. A code specifying the kind of relationship that exists with the target resource. A reference to the observation or [[[QuestionnaireResponse]]] resource that is related to this observation. 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.value[x] is missing. The assessment made based on the result of the observation. Intended as a simple compact code often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Otherwise known as abnormal flag. Guidance on how to interpret the value by comparison to a normal or recommended range. Has Member Derived From Sequel To Replaces Qualified By Interfered By Codes specifying how two observations are related. 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. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this operation definition is (or will be) published. The URL SHOULD include the major version of the operation definition. For more information see [Technical and Business Versions](resource.html#versions). 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. 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 if and 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 individual or organization 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 terms 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. Explaination of why this operation definition is needed and why it has been designed as it has. Operations that are idempotent (see [HTTP specification definition of idempotent](http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html)) may be invoked by performing an HTTP GET operation instead of a POST. 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. 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. How the parameter is understood as a search parameter. This is only used if the parameter type is 'string'. A profile the specifies the rules that this parameter must conform to. Binds to a value set if this parameter is coded (code, Coding, CodeableConcept). 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). Name of parameter to include in overload. Comments to go on overload. Address Age Annotation Attachment BackboneElement CodeableConcept Coding ContactDetail ContactPoint Contributor Count DataRequirement Distance Dosage Duration Element ElementDefinition Extension HumanName Identifier Meta Money Narrative ParameterDefinition Period Quantity Range Ratio Reference RelatedArtifact SampledData Signature SimpleQuantity Timing TriggerDefinition UsageContext base64Binary boolean code date dateTime decimal id instant integer markdown oid positiveInt string time unsignedInt uri uuid XHTML Account ActivityDefinition AdverseEvent AllergyIntolerance Appointment AppointmentResponse AuditEvent Basic Binary BodySite Bundle CapabilityStatement CarePlan CareTeam ChargeItem Claim ClaimResponse ClinicalImpression CodeSystem Communication CommunicationRequest CompartmentDefinition Composition ConceptMap Condition Consent Contract Coverage DataElement DetectedIssue Device DeviceComponent DeviceMetric DeviceRequest DeviceUseStatement DiagnosticReport DocumentManifest DocumentReference DomainResource EligibilityRequest EligibilityResponse Encounter Endpoint EnrollmentRequest EnrollmentResponse EpisodeOfCare ExpansionProfile ExplanationOfBenefit FamilyMemberHistory Flag Goal GraphDefinition Group GuidanceResponse HealthcareService ImagingManifest ImagingStudy Immunization ImmunizationRecommendation ImplementationGuide Library Linkage List Location Measure MeasureReport Media Medication MedicationAdministration MedicationDispense MedicationRequest MedicationStatement MessageDefinition MessageHeader NamingSystem NutritionOrder Observation OperationDefinition OperationOutcome Organization Parameters Patient PaymentNotice PaymentReconciliation Person PlanDefinition Practitioner PractitionerRole Procedure ProcedureRequest ProcessRequest ProcessResponse Provenance Questionnaire QuestionnaireResponse ReferralRequest RelatedPerson RequestGroup ResearchStudy ResearchSubject Resource RiskAssessment Schedule SearchParameter Sequence ServiceDefinition Slot Specimen StructureDefinition StructureMap Subscription Substance SupplyDelivery SupplyRequest Task TestReport TestScript ValueSet VisionPrescription Type Any If the element is present, it must have either a @value, an @id, or extensions 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. Typically, this may be a description of how a value is erroneous, or a stack dump to help trace the issue. For resource issues, this will be a simple XPath limited to element names, repetition indicators and the default child access 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 FHIRPath limited to element names, repetition indicators and the default child access 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 Not Found Content Too Long Invalid Code Unacceptable Extension Operation Too Costly Business Rule Violation Edit Version Conflict Incomplete Results Transient Issue Lock Error No Store Available Exception Timeout 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, 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, 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, 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. This special resource type is used to represent an operation request and response (operations.html). It has no other use, and there is no RESTful endpoint associated with it. This special resource type is used to represent an operation request and response (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 special resource type is used to represent an operation request and response (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. 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. Addresses for the individual. This field contains a patient's most recent marital (civil) status. Indicates whether the patient is part of a multiple (bool) or indicates the actual birth order (integer). Image of the patient. A contact party (e.g. guardian, partner, friend) for the patient. This patient is known to be an animal. Languages 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. Identifies the high level taxonomic categorization of the kind of animal. Identifies the detailed categorization of the kind of animal. Indicates the current state of the animal's reproductive organs. 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 Replaces 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 The notice business identifier. 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 the above payment action occurrred. 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. The organization which is responsible for the services rendered to the patient. The payment status, typically paid: payment sent, cleared: payment received. This resource provides payment details and claim references supporting a bulk payment. This resource provides payment details and claim references supporting a bulk payment. 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 period of time for which payments have been gathered into this bulk payment for settlement. The date when the enclosed suite of services were performed or completed. The Insurer who produced this adjudicated response. Original request resource reference. Transaction status: error, complete. A description of the status of the adjudication. The practitioner who is responsible for the services rendered to the patient. The organization which is responsible for the services rendered to the patient. List of individual settlement amounts and the corresponding transaction. The form to be used for printing the content. Total payment amount. Suite of notes. This resource provides payment details and claim references supporting a bulk payment. Code to indicate the nature of the payment, adjustment, funds advance, etc. The claim or financial resource. The claim response resource. The Organization which submitted the claim or financial transaction. The organization which is receiving the payment. The date of the invoice or financial resource. Amount paid for this detail. This resource provides payment details and claim references supporting a bulk payment. The note purpose: Print/Display. The note text. 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 actually 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. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this plan definition is (or will be) published. The URL SHOULD include the major version of the plan definition. For more information see [Technical and Business Versions](resource.html#versions). 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. The type of asset the plan definition represents, e.g. an order set, protocol, or event-condition-action rule. 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. The date (and optionally time) when the plan definition was published. The date must change if and 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 individual or organization that published the plan definition. A free text natural language description of the plan definition from a consumer's perspective. Explaination of why this plan definition is needed and why it has been designed as it has. A detailed description of how the asset is used from a clinical perspective. 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 doesn't change the original approval date. The period during which the plan definition content was or is planned to be in active use. The content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching for appropriate plan definition instances. A legal or geographic region in which the plan definition is intended to be used. 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. A contributor to the content of the asset, including authors, editors, reviewers, and endorsers. Contact details to assist a user in finding and communicating with the publisher. 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. 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 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 weigth, 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. Whan 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 label 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 may not be capable of interpreting it dynamically. A code that provides meaning for the action or action group. For example, a section may have a LOINC code for a 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 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 requiredness 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. A brief, natural language description of the condition that effectively communicates the intended semantics. The media type of the language for the expression. An expression that returns true or false, indicating whether or not 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. A brief, natural language description of the intended semantics of the dynamic value. 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 media type of the language for the expression. An expression specifying the value of the customized element. Must Could Must Unless Documented Defines requiredness behavior for selecting an action or an action group 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. Qualifications obtained by training and certification. A language the practitioner is able to 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's 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 organation. 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 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 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 a patient. This can be a physical intervention like an operation, or less invasive like counseling or hypnotherapy. An action that is or was performed on a patient. This can be a physical intervention like an operation, or less invasive like counseling or hypnotherapy. If the element is present, it must have either a @value, an @id, or extensions This records identifiers associated with this procedure 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). A protocol, guideline, orderset or other definition that was 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 in-progress or completed state. Set this to true if the record is saying that the procedure was NOT performed. A code indicating why the procedure was not performed. 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 the procedure was performed. The date(time)/period over which 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. 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 coded entity of some type, or may simply be present as text. The condition that is the reason 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 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 followup 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 about the procedure. E.g. the operative notes. 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 a patient. This can be a physical intervention like an operation, or less invasive like counseling or hypnotherapy. For example: surgeon, anaethetist, 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 a patient. This can be a physical intervention like an operation, or less invasive like counseling or hypnotherapy. The kind of change that happened to the device during the procedure. The device that was manipulated (changed) during the procedure. A record of a request for diagnostic investigations, treatments, or operations to be performed. A record of a request for 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. Protocol or definition followed by this request. 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 procedure or diagnostic 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. Indicates how quickly the ProcedureRequest should be addressed with respect to other requests. Set this to true if the record is saying that the procedure should NOT be performed. A code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure"). A code that identifies a particular procedure, diagnostic investigation, or panel of investigations, that have been requested. On whom or what the procedure or diagnostic 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 or episode of care that provides additional information about the healthcare context in which this request is made. The date/time at which the diagnostic testing should occur. If a CodeableConcept is present, it indicates the pre-condition for performing the procedure. 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 diagnostic testing. The desired perfomer for doing the diagnostic testing. For example, the surgeon, dermatopathologist, endoscopist, etc. An explanation or justification for why this diagnostic investigation is being requested in coded or textual form. This is often for billing purposes. May relate to the resources referred to in supportingInformation. Indicates another resource that provides a justification for why this diagnostic investigation is being requested. May relate to the resources referred to in supportingInformation. Additional clinical information about the patient or specimen that may influence the procedure or diagnostics 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, letting provider know that "patient hates needles" or other provider instructions. Key events in the history of the request. A record of a request for diagnostic investigations, treatments, or operations to be performed. The device, practitioner or organization who initiated the request. The organization the device or practitioner was acting on behalf of. Proposal Plan Order Original Order Reflex Order Filler Order Instance Order Option The kind of procedure or diagnostic request If the element is present, it must have either a @value, an @id, or extensions This resource provides the target, request and response, and action details for an action to be performed by the target on or about existing resources. This resource provides the target, request and response, and action details for an action to be performed by the target on or about existing resources. If the element is present, it must have either a @value, an @id, or extensions The ProcessRequest business identifier. The status of the resource instance. The type of processing action being requested, for example Reversal, Readjudication, StatusRequest,PendedRequest. The organization which is the target of the request. The date when this resource was created. The practitioner who is responsible for the action specified in this request. The organization which is responsible for the action speccified in this request. Reference of resource which is the target or subject of this action. Reference of a prior response to resource which is the target or subject of this action. If true remove all history excluding audit. A reference to supply which authenticates the process. List of top level items to be re-adjudicated, if none specified then the entire submission is re-adjudicated. Names of resource types to include. Names of resource types to exclude. A period of time during which the fulfilling resources would have been created. This resource provides the target, request and response, and action details for an action to be performed by the target on or about existing resources. A service line number. Cancel, Reverse or Nullify Poll Re-Process Status Check List of allowable action which this resource can request. If the element is present, it must have either a @value, an @id, or extensions This resource provides processing status, errors and notes from the processing of a resource. This resource provides processing status, errors and notes from the processing of a 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. The date when the enclosed suite of services were performed or completed. The organization who produced this adjudicated response. Original request resource reference. Transaction status: error, complete, held. A description of the status of the adjudication or processing. The practitioner who is responsible for the services rendered to the patient. The organization which is responsible for the services rendered to the patient. The form to be used for printing the content. Suite of processing notes or additional requirements if the processing has been held. Processing errors. Request for additional supporting or authorizing information, such as: documents, images or resources. This resource provides processing status, errors and notes from the processing of a resource. The note purpose: Print/Display. The note text. 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 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. The type of relationship between agents. 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. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this questionnaire is (or will be) published. The URL SHOULD include the major version of the questionnaire. For more information see [Technical and Business Versions](resource.html#versions). 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 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 date (and optionally time) when the questionnaire was published. The date must change if and 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 individual or organization that published the questionnaire. A free text natural language description of the questionnaire from a consumer's perspective. Explaination of why this questionnaire is needed and why it has been designed as it has. 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 doesn't change the original approval date. The period during which the questionnaire content was or is planned to be in active use. The content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching for appropriate questionnaire instances. A legal or geographic region in which the questionnaire is intended to be used. Contact details to assist a user in finding and communicating with the publisher. 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. An identifier for this question or group of questions in a particular terminology such as LOINC. The types of subjects that can be the subject of responses created for the questionnaire. 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. A reference to an [[[ElementDefinition]]] that provides the details for the item. If a definition is provided, then the following element values can be inferred from the definition: * code (ElementDefinition.code) * type (ElementDefinition.type) * required (ElementDefinition.min) * repeats (ElementDefinition.max) * maxLength (ElementDefinition.maxLength) * options (ElementDefinition.binding) Any information provided in these elements on a Questionnaire Item overrides the information from the definition. 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. 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 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. The value that should be defaulted 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. An indication that this item should be enabled only if the specified question is answered (hasAnswer=true) or not answered (hasAnswer=false). An answer that the referenced question must match 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. 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 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 ProcedureRequest 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 or episode of care with primary association to the questionnaire response. 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. More specific subject this section's answers are about, details the subject given in QuestionnaireResponse. 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 Used to record and send details about a request for referral service or transfer of a patient to the care of another provider or provider organization. Used to record and send details about a request for referral service or transfer of a patient to the care of another provider or provider organization. If the element is present, it must have either a @value, an @id, or extensions Business identifier that uniquely identifies the referral/care transfer request instance. A protocol, guideline, orderset or other definition that is adhered to in whole or in part by this request. Indicates any plans, proposals or orders that this request is intended to satisfy - in whole or in part. Completed or terminated request(s) whose function is taken by this new request. The business identifier of the logical "grouping" request/order that this referral is a part of. The status of the authorization/intention reflected by the referral request record. Distinguishes the "level" of authorization/demand implicit in this request. An indication of the type of referral (or where applicable the type of transfer of care) request. An indication of the urgency of referral (or where applicable the type of transfer of care) request. The service(s) that is/are requested to be provided to the patient. For example: cardiac pacemaker insertion. The patient who is the subject of a referral or transfer of care request. The encounter at which the request for referral or transfer of care is initiated. The period of time within which the services identified in the referral/transfer of care is specified or required to occur. Date/DateTime of creation for draft requests and date of activation for active requests. The individual who initiated the request and has responsibility for its activation. Indication of the clinical domain or discipline to which the referral or transfer of care request is sent. For example: Cardiology Gastroenterology Diabetology. The healthcare provider(s) or provider organization(s) who/which is to receive the referral/transfer of care request. Description of clinical condition indicating why referral/transfer of care is requested. For example: Pathological Anomalies, Disabled (physical or mental), Behavioral Management. Indicates another resource whose existence justifies this request. The reason element gives a short description of why the referral is being made, the description expands on this to support a more complete clinical summary. Any additional (administrative, financial or clinical) information required to support request for referral or transfer of care. For example: Presenting problems/chief complaints Medical History Family History Alerts Allergy/Intolerance and Adverse Reactions Medications Observations/Assessments (may include cognitive and fundtional assessments) Diagnostic Reports Care Plan. Comments made about the referral request by any of the participants. 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. Used to record and send details about a request for referral service or transfer of a patient to the care of another provider or provider organization. The device, practitioner, etc. who initiated the request. The organization the device or practitioner was acting on behalf of. 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 that this relationship is considered to be valid. If there are no dates defined, then the interval is unknown. 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 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. 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. Indicates the reason the request group was created. 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. 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 label 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 may not be capable of interpreting it dynamically. A code that provides meaning for the action or action group. For example, a section may have a LOINC code for a the 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 the requiredness behavior for the action. 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. A brief, natural language description of the condition that effectively communicates the intended semantics. The media type of the language for the expression. 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. 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. Codes categorizing the type of study such as investigational vs. observational, type of blinding, type of randomization, safety vs. efficacy, etc. The condition(s), medication(s), food(s), therapy(ies), device(s) or other concerns or interventions that the study is seeking to gain more information about. 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. The organization responsible for the execution of the study. Indicates the individual who has primary oversite of the execution of the study. Clinic, hospital or other healthcare location that is participating in the study. A description and/or code explaining the premature termination of the study. Comments made about the event 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 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. Draft In-progress Suspended Stopped Completed Entered in error 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 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. 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 Enrolled Active Suspended Withdrawn Completed 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. Indicates the source data considered as part of the assessment (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). How likely is the outcome (in the specified timeframe). How likely is the outcome (in the specified timeframe), expressed as a qualitative value (e.g. low, medium, 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. 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 categorisation 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 resource this Schedule resource is providing availability information for. These are expected to usually be one of HealthcareService, Location, Practitioner, PractitionerRole, Device, Patient or RelatedPerson. The period of time that the slots that are attached to 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. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this search parameter is (or will be) published. The URL SHOULD include the major version of the search parameter. For more information see [Technical and Business Versions](resource.html#versions). 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. 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 if and 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 individual or organization that published the search parameter. 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 terms 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. Explaination 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 a search parameter refers to, and how the content is interpreted. 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. A free text natural language description of the search parameter from a consumer's perspective. and how it used. 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). 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 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 Then 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 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 seqeunce 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 starts 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. 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. Reference identifier of reference sequence submitted to NCBI. It must match the type in the Sequence.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 Sequence entity as reference sequence. A string like "ACGT". Directionality of DNA sequence. Available values are "1" for the plus strand (5' to 3')/Watson/Sense/positive and "-1" for the minus strand(3' to 5')/Crick/Antisense/negative. 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 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 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 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). 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. 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 The ServiceDefinition describes a unit of decision support functionality that is made available as a service, such as immunization modules or drug-drug interaction checking. The ServiceDefinition describes a unit of decision support functionality that is made available as a service, such as immunization modules or drug-drug interaction checking. If the element is present, it must have either a @value, an @id, or extensions An absolute URI that is used to identify this service definition when it is referenced in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this service definition is (or will be) published. The URL SHOULD include the major version of the service definition. For more information see [Technical and Business Versions](resource.html#versions). A formal identifier that is used to identify this service definition when it is represented in other formats, or referenced in a specification, model, design or an instance. This is used for 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 service definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the service 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 service 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 service definition. The status of this service definition. Enables tracking the life-cycle of the content. A boolean value to indicate that this service 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 service definition was published. The date must change if and 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 service definition changes. The name of the individual or organization that published the service definition. A free text natural language description of the service definition from a consumer's perspective. Explaination of why this service definition is needed and why it has been designed as it has. A detailed description of how the module is used from a clinical perspective. 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 doesn't change the original approval date. The period during which the service definition content was or is planned to be in active use. The content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching for appropriate service definition instances. A legal or geographic region in which the service definition is intended to be used. Descriptive topics related to the module. Topics provide a high-level categorization of the module that can be useful for filtering and searching. A contributor to the content of the module, including authors, editors, reviewers, and endorsers. Contact details to assist a user in finding and communicating with the publisher. A copyright statement relating to the service definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the service definition. Related resources such as additional documentation, justification, or bibliographic references. The trigger element defines when the rule should be invoked. This information is used by consumers of the rule to determine how to integrate the rule into a specific workflow. Data requirements are a machine processable description of the data required by the module in order to perform a successful evaluation. A reference to the operation that is used to invoke this service. 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 categorisation 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 the patient(s) or from the environment 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 test or procedure 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. 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 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. 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 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. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this structure definition is (or will be) published. The URL SHOULD include the major version of the structure definition. For more information see [Technical and Business Versions](resource.html#versions). 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 if and 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 individual or organization 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 terms 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. Explaination 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. 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 3.0.1 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. If this is an extension, Identifies the context within FHIR resources where the extension can be used. Identifies the types of resource or data type elements to which the extension can be applied. A set of rules as Fluent Invariants about when the extension can be used (e.g. co-occurrence variants for the extension). 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). 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 stand alone 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. 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 Model 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 Resource Datatype Extension 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. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this structure map is (or will be) published. The URL SHOULD include the major version of the structure map. For more information see [Technical and Business Versions](resource.html#versions). 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 if and 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 individual or organization 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 terms 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. Explaination 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 managable chunks for human review/ease of maintenance. A Map of relationships between 2 structures that can be used to transform data. The canonical URL that identifies 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 thie 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 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 is able to 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 is able to 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. A tag to add to any resource that matches the criteria, after the subscription is processed. 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 is able to take an appropriate action. The type of channel to send notifications on. The uri 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. 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 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 assigned by the dispensing facility when the item(s) is dispensed. 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 Unique identifier for this supply request. 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 being requested. When the request should be fulfilled. When the request was made. The individual who initiated the request and has responsibility for its activation. Who is intended to fulfill the request. 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. The amount that is being ordered of the indicated item. 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. A record of a request for a medication, substance or device used in the healthcare setting. The device, practitioner, etc. who initiated the request. The organization the device or practitioner was acting on behalf of. 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. A reference to a formal or informal definition of the task. For example, a protocol, a step within a defined workflow definition, etc. BasedOn refers to a higher-level authorization that triggered the creation of the task. It references a "request" resource such as a ProcedureRequest, MedicationRequest, ProcedureRequest, CarePlan, etc. which is distinct from the "request" resource the task is seeking to fulfil. This latter resource is referenced by FocusOn. For example, based on a ProcedureRequest (= BasedOn), a task is created to fulfil 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. Is 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 type of participant that can execute the task. Individual organization or Device currently responsible for task execution. A description or code indicating why this task needs to be performed. 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. The device, practitioner, etc. who initiated the task. The organization the device or practitioner was acting on behalf of when they initiated 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 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 the 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 implementation to determine compliance against the FHIR specification. A structured set of tests against a FHIR server 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. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this test script is (or will be) published. The URL SHOULD include the major version of the test script. For more information see [Technical and Business Versions](resource.html#versions). 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 if and 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 individual or organization 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 terms 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. Explaination 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. Assert rule to be used in one or more asserts within the test script. Contains one or more rules. Offers a way to group rules so assertions could reference the group of rules and have them all applied. A series of required setup operations before tests are executed. A test in this script. A series of operations required to clean up after the all the tests are executed (successfully or otherwise). A structured set of tests against a FHIR server 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 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 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 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 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 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 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 fluentpath 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 implementation to determine compliance against the FHIR specification. Reference to the resource (containing the contents of the rule needed for assertions). Each rule template can take one or more parameters for rule evaluation. A structured set of tests against a FHIR server implementation to determine compliance against the FHIR specification. Descriptive name for this parameter that matches the external assert rule parameter name. The explicit or dynamic value for the parameter that will be passed on to the external rule template. A structured set of tests against a FHIR server implementation to determine compliance against the FHIR specification. Reference to the resource (containing the contents of the ruleset needed for assertions). The referenced rule within the external ruleset template. A structured set of tests against a FHIR server implementation to determine compliance against the FHIR specification. Id of the referenced rule within the external ruleset template. Each rule template can take one or more parameters for rule evaluation. A structured set of tests against a FHIR server implementation to determine compliance against the FHIR specification. Descriptive name for this parameter that matches the external assert ruleset rule parameter name. The value for the parameter that will be passed on to the external ruleset rule template. A structured set of tests against a FHIR server 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 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 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 content-type or mime-type to use for RESTful operation in the 'Accept' header. The content-type or 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 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 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 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 fluentpath 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 content-type or mime-type to use for RESTful operation in the 'Content-Type' header. The fluentpath 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. The TestScript.rule this assert will evaluate. The TestScript.ruleset this assert will evaluate. 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 implementation to determine compliance against the FHIR specification. The TestScript.rule id value this assert will evaluate. Each rule template can take one or more parameters for rule evaluation. A structured set of tests against a FHIR server implementation to determine compliance against the FHIR specification. Descriptive name for this parameter that matches the external assert rule parameter name. The value for the parameter that will be passed on to the external rule template. A structured set of tests against a FHIR server implementation to determine compliance against the FHIR specification. The TestScript.ruleset id value this assert will evaluate. The referenced rule within the external ruleset template. A structured set of tests against a FHIR server implementation to determine compliance against the FHIR specification. Id of the referenced rule within the external ruleset template. Each rule template can take one or more parameters for rule evaluation. A structured set of tests against a FHIR server implementation to determine compliance against the FHIR specification. Descriptive name for this parameter that matches the external assert ruleset rule parameter name. The value for the parameter that will be passed on to the external ruleset rule template. A structured set of tests against a FHIR server 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 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 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 implementation to determine compliance against the FHIR specification. An operation would involve a REST request to a server. Address Age Annotation Attachment BackboneElement CodeableConcept Coding ContactDetail ContactPoint Contributor Count DataRequirement Distance Dosage Duration Element ElementDefinition Extension HumanName Identifier Meta Money Narrative ParameterDefinition Period Quantity Range Ratio Reference RelatedArtifact SampledData Signature SimpleQuantity Timing TriggerDefinition UsageContext base64Binary boolean code date dateTime decimal id instant integer markdown oid positiveInt string time unsignedInt uri uuid XHTML Account ActivityDefinition AdverseEvent AllergyIntolerance Appointment AppointmentResponse AuditEvent Basic Binary BodySite Bundle CapabilityStatement CarePlan CareTeam ChargeItem Claim ClaimResponse ClinicalImpression CodeSystem Communication CommunicationRequest CompartmentDefinition Composition ConceptMap Condition Consent Contract Coverage DataElement DetectedIssue Device DeviceComponent DeviceMetric DeviceRequest DeviceUseStatement DiagnosticReport DocumentManifest DocumentReference DomainResource EligibilityRequest EligibilityResponse Encounter Endpoint EnrollmentRequest EnrollmentResponse EpisodeOfCare ExpansionProfile ExplanationOfBenefit FamilyMemberHistory Flag Goal GraphDefinition Group GuidanceResponse HealthcareService ImagingManifest ImagingStudy Immunization ImmunizationRecommendation ImplementationGuide Library Linkage List Location Measure MeasureReport Media Medication MedicationAdministration MedicationDispense MedicationRequest MedicationStatement MessageDefinition MessageHeader NamingSystem NutritionOrder Observation OperationDefinition OperationOutcome Organization Parameters Patient PaymentNotice PaymentReconciliation Person PlanDefinition Practitioner PractitionerRole Procedure ProcedureRequest ProcessRequest ProcessResponse Provenance Questionnaire QuestionnaireResponse ReferralRequest RelatedPerson RequestGroup ResearchStudy ResearchSubject Resource RiskAssessment Schedule SearchParameter Sequence ServiceDefinition Slot Specimen StructureDefinition StructureMap Subscription Substance SupplyDelivery SupplyRequest Task TestReport TestScript ValueSet VisionPrescription If the element is present, it must have either a @value, an @id, or extensions xml json ttl none The content or mime type. If the element is present, it must have either a @value, an @id, or extensions 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 The allowable request method or HTTP operation codes. If the element is present, it must have either a @value, an @id, or extensions A value set specifies a set of codes drawn from one or more code systems. A value set specifies a set of codes drawn from one or more code systems. 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. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this value set is (or will be) published. The URL SHOULD include the major version of the value set. For more information see [Technical and Business Versions](resource.html#versions). 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. 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 published. The date must change if and 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 value set changes. (e.g. the 'content logical definition'). The name of the individual or organization 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 content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching for appropriate 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. Explaination 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. Whether this is intended to be used with an extensible binding or not. A set of criteria that define the content logical definition of the value set by including or excluding codes from outside this value set. This I 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 value set specifies a set of codes drawn from one or more code systems. If a locked date is defined, then the Content Logical Definition must be evaluated using the current version as of the locked date for referenced code system(s) and value set instances where ValueSet.compose.include.version is not defined. 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 ExpansionProfile (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 value set specifies a set of codes drawn from one or more code systems. 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. Specifies a concept to be included or excluded. Select concepts by specify a matching criteria based on the properties (including relationships) defined by the system. If multiple filters are specified, they SHALL all be true. Selects concepts found in this value set. This is an absolute URI that is a reference to ValueSet.url. A value set specifies a set of codes drawn from one or more code systems. 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 value set specifies a set of codes drawn from one or more code systems. The language this designation is defined for. A code that details how this designation would be used. The text value for this designation. A value set specifies a set of codes drawn from one or more code systems. A code that identifies a property 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 when the operation is 'regex', or one of the values (true and false), when the operation is 'exists'. A value set specifies a set of codes drawn from one or more code systems. An identifier that uniquely identifies this expansion of the valueset. Systems may re-use the same identifier as long as the expansion and the definition remain the same, but are not required to do so. 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 value set specifies a set of codes drawn from one or more code systems. The name of the parameter. The value of the parameter. A value set specifies a set of codes drawn from one or more code systems. 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. The version of this code system that defined this code and/or display. This should only be used with code systems that do not enforce concept permanence. 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. An authorization for the supply of glasses and/or contact lenses to a patient. An authorization for the supply of glasses and/or contact lenses to a patient. If the element is present, it must have either a @value, an @id, or extensions Business identifier which may be used by other parties to reference or identify the prescription. The status of the resource instance. A link to a resource representing the person to whom the vision products will be supplied. A link to a resource that identifies the particular occurrence of contact between patient and health care provider. The date (and perhaps time) when the prescription was written. The healthcare professional responsible for authorizing the prescription. Can be the reason or the indication for writing the prescription. Deals with details of the dispense part of the supply specification. An authorization for the supply 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 applies. Lens power measured in diopters (0.25 units). Power adjustment for astigmatism measured in diopters (0.25 units). Adjustment for astigmatism measured in integer degrees. Amount of prism to compensate for eye alignment in fractional units. The relative base, or reference lens edge, for the prism. Power adjustment for multifocal lenses measured in diopters (0.25 units). Contact lens power measured in diopters (0.25 units). Back curvature measured in millimeters. Contact lens diameter measured in millimeters. 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. 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