Name Flags Card. Type Description & Constraints<img src="[binary]" alt="doco" style="background-color: inherit"/> Measure 0..* PublicHealthMeasure A quality measure definition text S 0..1 Narrative Text summary of the resource, for human interpretation group 1..1 BackboneElement Population criteria group code S 1..1 CodeableConceptTW 概念（Concept）— 參照一個專門術語或只是文字表述 Required Pattern: At least the following coding 1..* Coding Code defined by a terminology system Fixed Value: (complex) system 1..1 uri Identity of the terminology system Fixed Value: http://hl7.org/fhir/uv/saner/CodeSystem/MeasureGroupSystem code 1..1 code Symbol in syntax defined by the system Fixed Value: Beds population 1..* BackboneElement Population criteria code 1..1 CodeableConceptTW 概念（Concept）— 參照一個專門術語或只是文字表述 <img src="[binary]" alt="doco" style="background-color: inherit"/> Documentation for this format
The Measure resource provides the definition of a quality measure.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
Name should be usable as an identifier for the module by machine processing applications such as code generation
not(exists(f:name/@value)) or matches(f:name/@value, '[A-Z]([A-Za-z0-9_]){0,254}')
Stratifier SHALL be either a single criteria or a set of criteria components
group.stratifier.all((code | description | criteria).exists() xor component.exists())
exists(f:group/stratifier/code) or exists(f:group/stratifier/component)
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
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.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Enables specification of proposed measure reporting
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
An absolute URI that is used to identify this measure when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this measure is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the measure is stored on different servers.
The url for resource defined in The Situation Awareness for Novel Epidemic Response IG will follow IG URL naming conventions.
Allows the measure to be referenced by a single globally unique identifier.
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.
Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this measure outside of FHIR, where it is not possible to use the logical URI.
Allows externally provided and/or usable business identifiers to be easily associated with the module.
Resources are versioned like IG's 0.1.0 = first development version, 0.2.0 - first published for review version, 1.0.0 first official version ...
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.
There may be different measure instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the measure with the format [url]|[version].
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.
The name should be in PascalCase, and should represent the Author's title of the resource. Identify the Author to clarify
Support human navigation and code generation.
A short, descriptive, user-friendly title for the measure.
This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
An explanatory or alternate title for the measure giving additional information about its content.
The status of this measure. Enables tracking the life-cycle of the content.
draft - The resource is still in development. active - The resource is ready for piloting or normal use. retired - resource has been deprecated or replaced.
This is labeled as "Is Modifier" because applications should not use a retired {{title}} without due consideration
A resource must indicate its experimental status
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.
true - development, testing or pilots, false - production use
Enables experimental content to be developed following the same lifecycle that would be used for a production-level measure.
E.g. Patient, Practitioner, RelatedPerson, Organization, Location, Device
The intended subjects for the measure. If this element is not provided, a Patient subject is assumed, but the subject of the measure can be anything.
The subject of the measure is critical in interpreting the criteria definitions, as the logic in the measures is evaluated with respect to a particular subject. This corresponds roughly to the notion of a Compartment in that it limits what content is available based on its relationship to the subject. In CQL, this corresponds to the context declaration.
The possible types of subjects for a measure (E.g. Patient, Practitioner, Organization, Location, etc.).
The date (and optionally time) when the measure was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the measure changes.
Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the measure. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
The name of the organization publishing this resource
The name of the organization or individual that published the measure.
Usually an organization but may be an individual. The publisher (or steward) of the measure is the organization or individual primarily responsible for the maintenance and upkeep of the measure. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the measure. This item SHOULD be populated unless the information is available from context.
Helps establish the "authority/credibility" of the measure. May also allow for contact.
The contact information for whom to contact about this resource
Contact details to assist a user in finding and communicating with the publisher.
Natural language description of the measure
A free text natural language description of the measure from a consumer's perspective.
This description can be used to capture details such as why the measure was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the measure as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the measure is presumed to be the predominant language in the place the measure was created).
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate measure instances.
When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
Assist in searching for appropriate content.
Intended jurisdiction for measure (if applicable)
A legal or geographic region in which the measure is intended to be used.
It may be possible for the measure to be used in jurisdictions other than those for which it was originally designed or intended.
Countries and regions within which this artifact is targeted for use.
Explanation of why this measure is needed and why it has been designed as it has.
This element does not describe the usage of the measure. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this measure.
Describes the clinical usage of the measure
A detailed description, from a clinical perspective, of how the measure is used.
A copyright statement relating to the measure and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the measure.
Consumers must be able to determine any legal restrictions on the use of the measure and/or its content.
When the measure was approved by publisher
The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage.
The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.
The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date.
If specified, this date follows the original approval date.
Gives a sense of how "current" the content is. Resources that have not been reviewed in a long time may have a risk of being less appropriate/relevant.
The period during which the measure content was or is planned to be in active use.
The effective period for a measure determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.
Allows establishing a transition before a resource comes into effect and also allows for a sunsetting process when new versions of the measure are or are expected to be used instead.
The category of the measure, such as Education, Treatment, Assessment, etc.
Descriptive topics related to the content of the measure. Topics provide a high-level categorization grouping types of measures that can be useful for filtering and searching.
Repositories must be able to determine how to categorize the measure so that it can be found by topical searches.
High-level categorization of the definition, used for searching, sorting, and filtering.
The original author of the measure content, may be same as publisher, when otherwise, must include a relatedArtifact for the original author's publication
An individiual or organization primarily involved in the creation and maintenance of the content.
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
The author must be identified by name. Can be the name of an individual or an organization.
If there is no named individual, the telecom information is for the organization as a whole.
There must be contact information for the author.
The contact details for the individual (if a name was provided) or the organization.
At least on author contact should be an email address.
An individual or organization primarily responsible for internal coherence of the content.
An individual or organization primarily responsible for review of some aspect of the content.
.participation[typeCode=VRF] {not clear whether VRF best corresponds to reviewer or endorser}
An individual or organization responsible for officially endorsing the content for use in some setting.
There must be at least one artifact describing the measure in human readable form.
Related artifacts such as additional documentation, justification, or bibliographic references.
Each related artifact is either an attachment, or a reference to another resource, but not both.
Measures must be able to provide enough information for consumers of the content (and/or interventions or results produced by the content) to be able to determine and understand the justification for and evidence in support of the content.
A reference to a Library resource containing the formal logic used by the measure.
Disclaimer for use of the measure or its referenced content
Notices and disclaimers regarding the use of the measure or related to intellectual property (such as code systems) referenced by the measure.
Some organizations require that notices and disclosures be included when publishing measures that reference their intellecutal property.
proportion | ratio | continuous-variable | cohort
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.
opportunity | all-or-nothing | linear | weighted
If this is a composite measure, the scoring method used to combine the component measures to determine the composite score.
The composite scoring method of the measure.
process | outcome | structure | patient-reported-outcome | composite
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.
The type of measure (includes codes from 2.16.840.1.113883.1.11.20368).
How risk adjustment is applied for this measure
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 the method of adjusting for clinical severity and conditions present at the start of care that can influence patient outcomes for making valid comparisons of outcome measures across providers. Indicates whether a measure is subject to the statistical process for reducing, removing, or clarifying the influences of confounding factors to allow for more useful comparisons.
How is rate aggregation performed for this measure
Describes how to combine the information calculated, based on logic in each of several populations, into one summarized result.
The measure rate for an organization or clinician is based upon the entities’ aggregate data and summarizes the performance of the entity over a given time period (e.g., monthly, quarterly, yearly). The aggregated data are derived from the results of a specific measure algorithm and, if appropriate, the application of specific risk adjustment models. Can also be used to describe how to risk adjust the data based on supplemental data elements described in the eMeasure (e.g., pneumonia hospital measures antibiotic selection in the ICU versus non-ICU and then the roll-up of the two). This could be applied to aggregated cohort measure definitions (e.g., CDC's aggregate reporting for TB at the state level).
Detailed description of why the measure exists
Provides a succinct statement of the need for the measure. Usually includes statements pertaining to importance criterion: impact, gap in care, and evidence.
Measure developers need to be able to provide a detailed description of the purpose of the measure. This element provides detailed rationale, where the purpose element provides a summary of the rationale.
Provides a summary of relevant clinical guidelines or other clinical recommendations supporting the measure.
Information on whether an increase or decrease in score is the preferred result (e.g., a higher score indicates better quality OR a lower score indicates better quality OR quality is within a range).
Measure consumers and implementers must be able to determine how to interpret a measure score.
Observation values that indicate what change in a measurement value or score is indicative of an improvement in the measured item or scored issue.
Defined terms used in the measure documentation
Provides a description of an individual term used within the measure.
Measure developers must be able to provide precise definitions of terms used within measure descriptions and guidance to help communicate the intent of the measure.
Additional guidance for the measure including how it can be used in a clinical context, and the intent of the measure.
Measure developers must be able to provide additional guidance for implementers to understand the intent with greater specificity than that provided in the population criteria of the measure. This element provides detailed guidance, where the usage element provides a summary of the guidance.
A group of population criteria for the measure.
Describes the attributes of one or more sections of the measure (form) being reported
Attributes describing the group of measures
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).
availability : Use availability to measure the point-in-time availability of a resource (e.g., protective equipment, medications, supplies). capacity : Use capacity to measure point-in-time capacity or utilization for a resource (e.g., beds, ventilators). event-growth : Use event-growth to count current and cumulative totals of events. queue-length : Use queue-length to measure the numbers of people, organizations or other entities awaiting service. service-time : Use service-time to measure the average time it takes to provide service (e.g., length of stay, time to report a lab result). continuous-variable : Use continuous-variable when reporting a group of counts of the same type of resource, with different constraints on when to count it. Also use continuous variable to report measures with computations over measure-observation values (e.g., average length of stay). proportion : Use proportion to report percentages, or ratios from the (generally) same initial population. ratio : Use ratio to report ratios from different initial populations. cohort: : Use cohort to report counts of unrelated or orthogonal categories (e.g., masks, gowns, gloves) within a group, where proportions aren't of significance. Also use cohort to count answers to categorical questions, where each question is one cohort, and is stratified by possible answers (e.g., Yes/No, 0 days/1-3 days/4-6 days/7-9 days/more than 9 days supply).
Like Measure.compositeScoring, but applies to group
structure : Use when the measure is about capacity of a facility or organization to provide services, e.g., quantities of resources, staff, expendibles, et cetera. process : Use when the measure is about the execution of a process, things that are done, in process, et cetera. outcome : Use when the measure describes the outcome or result. If by the measure you know a patient is getting better or worse, it's an outcome measure. patient-reported-outcome : Use when the outcome is reported by a patient or their authorized representative (usually used with "satisfaction scores", but could be used with other outcomes). composite : Use when two or more of the above are appropriate. Consider subdividing the group further.
Like Measure.riskAdjustment, but applies to group
count : Use this when the value being reported can be aggregated (added to) values in other periods and retain meaning (e.g., adding admissions on day 1 and day 2 reporting period gives admissions for the combined reporting period)" point-in-time : Use this when the value being reported is a point-in-time (e.g. instantanious value) that cannot be meaningfully combined with a value from another reporting period cumulative : Use this when the value being reported is a point-in-time cumulative value over all reports
increase : Use when a higher score indicates more patients are having better outcomes, are being treated, or can be treated, et cetera. decrease: : Use when a higher score indicates more patients are having worse outcomes, are not be treated, or cannot be treated, et cetera.
Concept - reference to a terminology or just text
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
Describe the subject being enumerated that is associated with the measure. The first code should identify the FHIR Resource type. The second should further describe it using SNOMED CT. Subsequent codes may describe it using other coding systems.
fhir:CodeableConcept rdfs:subClassOf dt:CD
Identifies the ValueSet describing the subject elements to count based on a code.
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
概念（Concept）— 參照一個專門術語或只是文字表述
Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
The human readable description of this population group.
The coding gives a 'name' for this population and must be supplied
A reference to a code defined by a terminology system.
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
Allows for alternative encodings within a code system, and translations to other code systems.
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
A human readable description of what this population is
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.
Very often the text is the same as a displayName of one of the codings.
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
Human readable instructions for counting or measuring this population
The human readable description of this population criteria.
An expression that can be used to generate a value
A expression that is evaluated in a specified context and returns a value. The context of use of the expression must specify the context in which the expression is evaluated, and how the result of the expression is used.
In the case of a continuous-variable or ratio measure, this may be the name of a function that calculates the value of the individual observation for each patient or event in the population. For these types of measures, individual observations are reported as observation resources included in the evaluatedResources bundle for each patient. See the MeasureReport resource or the Quality Reporting topic for more information.
An expression or a reference must be provided
expression.exists() or reference.exists()
exists(f:expression) or exists(f:reference)
A group may have none, some or many strata
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.
Describes the purpose of this stratifier
Indicates a meaning for the stratifier. This can be as simple as a unique identifier, or it can establish meaning in a broader context by drawing from a terminology, allowing stratifiers to be correlated across measures.
Optional code uniquely identifying the strata
The identification of the code system that defines the meaning of the symbol in the code.
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
Need to be unambiguous about the source of the definition of the symbol.
fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
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.
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
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).
Need to refer to a particular code in the system.
fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
Provides a human readable name for the strata
A representation of the meaning of the code in the system, following the rules of the system.
Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
C*E.2 - but note this is not well followed
fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
Describes the function of the stratifier.
Describes the overall function of the strata.
The human readable description of this stratifier criteria.
A component of the stratifier criteria for the measure report, specified as either the name of a valid CQL expression defined within a referenced library or a valid FHIR Resource Path.
Stratifiers are defined either as a single criteria, or as a set of component criteria.
Indicates a meaning for the stratifier component. This can be as simple as a unique identifier, or it can establish meaning in a broader context by drawing from a terminology, allowing stratifiers to be correlated across measures.
The human readable description of this stratifier component
The human readable description of this stratifier criteria component.
Component of how the measure should be stratified
An expression that specifies the criteria for this component of the stratifier. This is typically the name of an expression defined within a referenced library, but it may also be a path to a stratifier element.
What other data should be reported with 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.
Note that supplemental data are reported as observations for each patient and included in the evaluatedResources bundle. See the MeasureReport resource or the Quality Reporting topic for more information.
Resource type included in the supplementalData
Indicates a meaning for the supplemental data. This can be as simple as a unique identifier, or it can establish meaning in a broader context by drawing from a terminology, allowing supplemental data to be correlated across measures.
supplemental-data | risk-adjustment-factor
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 intended usage for supplemental data elements in the measure.
The human readable description of this supplemental data
The human readable description of this supplemental data.