A knowledge module is a description of a quality improvement function made available by a knowledge evaluation service. A module may correspond directly to an artifact or group of related artifacts, or it may correspond to functionality provided by the service and not necessarily associated with any tangible knowledge artifact. The knowledge module serves as the descriptive unit for functionality supported by a knowledge service such as a decision support service, measure evaluation service, or other quality improvement service.

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. Bundles always have an id, though it is usually a generated UUID.

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.

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 as much as possible.

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).

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.

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.

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.

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.

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.

• unordered
• Open
• discriminators: url

The version of the module, if any. 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 modules, refer to the Decision Support Service specification.

A short, descriptive title for the module.

A description of the module from the consumer perspective.

A brief description of the purpose of the module.

Notes about usage of the module.

The date on which the module was published.

The date on which the module content was last reviewed.

The period during which the module content is effective.

Clinical topics related to the content of the module.

Keywords associated with the module.

A contributor to the content of the module.

The organization responsible for publishing the module.

The organization responsible for stewardship of the module content.

The legal rights declaration for the module.

Related resources such as additional documentation, supporting evidence, or bibliographic references.

A model reference used by the content.

A library referenced by the module. The reference must consist of either an id, or a document reference.

A code system definition used within the knowledge module.

A value set definition used by the knowledge module.

Parameters to the module.

Describes a required data item for evaluation in terms of the type of data, and optional code- or date-based filters of the data.

The content of the module, if any. If this is a library, this would be the CQL or ELM representation of the library contents.

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.

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.

• unordered
• Open
• discriminators: url

The status of the module.

Indicates whether or not the service supports evaluation of the module. If evaluation is supported, an evaluation operation must be exposed as defined by this implementation guide.

A logical identifier for the knowledge module.

Identifies the 'type' of resource - equivalent to the resource name for other resources.

Must be able to distinguish different types of "basic" resources.

Because resource references will only be able to indicate 'Basic', the type of reference will need to be specified in a Profile identified as part of the resource. Refer to the resource notes section for information on appropriate terminologies for this code.

Identifies the patient, practitioner, device or any other resource that is the "focus" of this resoruce.

Needed for partitioning the resource by Patient.

Optional as not all resources potential resources will have subjects. Resources associated with multiple subjects can handle this via extension.

Indicates who was responsible for creating the resource instance.

Needed for partitioning the resource.

Identifies when the resource was first created.

Allows ordering resource instances by time.