The Library resource is a general-purpose container for knowledge asset artifact definitions. It can be used to describe and expose existing knowledge assets artifacts such as logic libraries and information model descriptions, as well as to describe a collection of knowledge assets. artifacts.

An absolute URI that is used to identify this library when it is referenced in a specification, model, design or an instance. instance; also called its canonical identifier. This SHALL be a URL, SHOULD be globally unique, unique and SHOULD be an a literal address at which an authoritative instance of this library is (or will be) published. The This URL SHOULD include can be the major version target of a canonical reference. It SHALL remain the library. For more information see Technical and Business Versions . same when the library is stored on different servers.

Allows the library to be referenced by a single globally unique identifier.

Can be a urn:uuid: or a urn:oid:, urn:oid: but real http: addresses are preferred. Multiple instances may share the same url URL if they have a distinct version.

The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions .

In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.

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.

Allows externally provided and/or usable business identifiers to be easily associated with the module.

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, artifacts, refer to the Decision Support Service specification. Note that a version is required for non-experimental active artifacts.

There may be different library instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a refrence reference to a particular business version of the library with the format [url]|[version]. The version SHOULD NOT contain a '#' - see Business Version .

Indicates the mechanism used to compare versions to determine which is more current.

If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined.

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.

Support human navigation and code generation.

The name is not expected to be globally unique. The name should be a simple alpha-numeric alphanumeric type name to ensure that it is computable machine-processing friendly.

A short, descriptive, user-friendly title for the library.

This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

An explanatory or alternate title for the library giving additional information about its content.

The status of this library. Enables tracking the life-cycle of the content.

Allows filtering of librarys libraries that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use a retired library without due consideration.

See guidance around (not) making local changes to elements here .

A boolean Boolean value to indicate that this library is authored for testing purposes (or education/evaluation/marketing), education/evaluation/marketing) and is not intended to no version of this resource will ever be used intended for genuine usage.

Enables experimental content to be developed following the same lifecycle that would be used for a production-level library.

Allows filtering of library librarys that are appropriate for use vs. versus not. This Experimental resources might include example instances in implementation guides, instances created solely for testing purposes, etc. If experimental is labeled as "Is Modifier" because applications 'true' for any version of a resource, it should not use an be true for all versions of the resource. (If experimental library in production. changes, then it is being misused or a resource that was never intended for real-world use has unexpectedly changed its purpose.).

Experimental resources are not expected to be stable and may well have breaking changes without a corresponding change to the 'version' element.

Identifies the type of library such as a Logic Library, Model Definition, Asset Collection, or Module Definition.

A code or group definition that describes the intended subject of the contents of the library.

The date (and optionally time) when the library was published. last significantly changed. 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 date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the library. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.

See guidance around (not) making local changes to elements here .

The name of the individual or organization that published or individual responsible for the release and ongoing maintenance of the library.

Helps establish the "authority/credibility" "authority/credibility" of the library. May also allow for contact.

Usually an organization, organization but may be an individual. The publisher (or steward) of the library is the organization or individual primarily responsible for the maintenance and upkeep of the library. 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 library. This item SHOULD be populated unless the information is available from context.

Contact details to assist a user in finding and communicating with the publisher.

May be a web site, an email address, a telephone number, etc.

See guidance around (not) making local changes to elements here .

A free text natural language description of the library from a consumer's perspective.

This description can be used to capture details such as why the library 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 library 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 profile library is presumed to be the predominant language in the place the profile library 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 library instances.

Assist in searching for appropriate content.

When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.

A legal or geographic region in which the authority that maintains the resource is operating. In general, the jurisdiction is also found in the useContext. The useContext may reference additional jurisdictions because the defining jurisdiction does not necessarily limit the jurisdictions of use.

It may be possible for the library to be used in jurisdictions other than those for which it was originally designed or intended.

DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)

Explaination Explanation of why this library is needed and why it has been designed as it has.

This element does not describe the usage of the library Instead library. 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 library.

A detailed description of how the library is used from a clinical perspective.

A copyright statement relating to the library and/or its contents. Copyright statements are notices of intellectual property ownership and can include restrictions on the use and publishing of the library.

Consumers must be able to determine any legal restrictions on the use of the library and/or its content.

The short copyright declaration (e.g. (c) '2015+ xyz organization') should be sent in the copyrightLabel element without the copyright prefix (i.e., do not include '(c)' or the symbol).

A short string (<50 characters), suitable for inclusion in a page footer that identifies the copyright holder, effective period, and optionally whether rights are restricted. (e.g. 'All rights reserved', 'Some rights reserved').

Defines the content expected to be rendered in all representations of the artifact.

The copyright symbol and the '(c)' textual representation SHOULD NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.

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.

See guidance around (not) making local changes to elements here .

The date on which the resource content was last reviewed. Review happens periodically after approval, approval but doesn't does not change the original approval date.

Gives a sense of how "current" "current" the content is. Resources that have not been reviewed in a long time may have a risk of being less appropriate/relevant.

If specified, this is usually after date follows the original approval date.

See guidance around (not) making local changes to elements here .

The period during which the library content was or is planned to be in active use.

Allows establishing a transition before a resource comes into effect and also allows for a sunsetting process when new versions of a the library are or are expected to be used instead.

The effective period for a library determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure library intended to be used for the year 2016 might be published in 2015.

See guidance around (not) making local changes to elements here .

The Descriptive topics related to the content was developed with of the library. Topics provide a focus and intent high-level categorization of supporting the contexts library that are listed. These terms may can be used to assist with indexing and searching useful for appropriate library instances. filtering and searching.

Assist in searching for appropriate content. Repositories must be able to determine how to categorize the library so that it can be found by topical searches.

When multiple useContexts DEPRECATION NOTE: For consistency, implementations are specified, there is no expectation whether all or any of encouraged to migrate to using the contexts apply. new 'topic' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#topic and useContext.valueCodeableConcept indicating the topic)

A legal An individiual or geographic region organization primarily involved in which the library is intended to be used. creation and maintenance of the content.

Descriptive topics related to the content of the library. Topics provide a high-level categorization An individual or organization primarily responsible for internal coherence of the library that can be useful for filtering and searching. content.

Consumers of An individual or organization asserted by the content must be able to quickly determine who contributed publisher to the content be primarily responsible for review of some aspect of the library. content.

May be a web site, an email address, a telephone number, etc. See guidance around (not) making local changes to elements here .

A copyright statement relating to An individual or organization asserted by the library and/or its contents. Copyright statements are generally legal restrictions on publisher to be responsible for officially endorsing the content for use and publishing of the library. in some setting.

See guidance around (not) making local changes to elements here .

Related artifacts such as additional documentation, justification, or bibliographic references.

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

Each related artifact is either an attachment, or a reference to another resource, but not both. In addition, the successor or predecessor of a Library SHOULD be a Library, and dependencies and components of a Library SHOULD reference a resource.

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.