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