Generated Narrative: StructureDefinition profile-GraphDefinition Name Flags Card. Type Description & Constraints GraphDefinition 0..* GraphDefinition Definition of an graph of resources #xD; start #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:start 0..1 code R4: start URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-GraphDefinition.start Binding: R4ResourceTypesForR3 (0.1.0) (required): One of the resource types defined as part of this version of FHIR. #xD; link #xD; target #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:params 0..1 string R4: Criteria for reverse lookup (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-GraphDefinition.link.target.params #xD; type #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:type 0..1 code R4: type URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-GraphDefinition.link.target.type Binding: R4ResourceTypesForR3 (0.1.0) (required): One of the resource types defined as part of this version of FHIR. #xD; compartment #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:use 1..1 code R4: condition | requirement (new) URL: http://hl7.org/fhir/4.0/StructureDefinition/extension-GraphDefinition.link.target.compartment.use Binding: R4GraphCompartmentUseForR3 (0.1.0) (required): Defines how a compartment rule is used. #xD; Documentation for this format
Cross-version Profile for R4.GraphDefinition for use in FHIR STU3
This cross-version profile allows R4 GraphDefinition content to be represented via FHIR STU3 GraphDefinition resources.
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 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 NOT contain any narrative
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 the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource
contained.where(('#'+id in %resource.descendants().reference).not()).empty()
not(exists(for $id in f:contained/*/@id return $id[not(ancestor::f:contained/parent::*/descendant::f:reference/@value=concat('#', $id))]))
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 may not always be associated with version changes to the resource.
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.
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. This element is labelled 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 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. 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 in formation 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.
Additional Content defined by implementations
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.
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.
Logical URI to reference this graph definition (globally unique)
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](http://hl7.org/fhir/STU3/resource.html#versions).
Can be a urn:uuid: or a urn:oid:, but real http: addresses are preferred. Multiple instances may share the same url if they have a distinct version.
Allows the graph definition to be referenced by a single globally unique identifier.
Business version of the graph definition
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.
There may be different graph definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a refrence to a particular business version of the graph definition with the format [url]|[version].
Name for this graph definition (computer friendly)
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 name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly.
Support human navigation and code generation.
The status of this graph definition. Enables tracking the life-cycle of the content.
Allows filtering of graph definitions that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use a retired graph definition without due consideration.
The lifecycle status of a Value Set or Concept Map.
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.
Allows filtering of graph definition that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use an experimental graph definition in production.
Enables experimental content to be developed following the same lifecycle that would be used for a production-level graph definition.
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.
Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the graph definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
Name of the publisher (organization or individual)
The name of the individual or organization that published the graph definition.
Usually an organization, but may be an individual. The publisher (or steward) of the graph definition is the organization or individual primarily responsible for the maintenance and upkeep of the graph definition. 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 graph definition. This item SHOULD be populated unless the information is available from context.
Helps establish the "authority/credibility" of the graph definition. May also allow for contact.
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.
Natural language description of the graph definition
A free text natural language description of the graph definition from a consumer's perspective.
This description can be used to capture details such as why the graph definition 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 graph definition 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 is presumed to be the predominant language in the place the profile was created).
Context the content is intended to support
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.
When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.
Assist in searching for appropriate content.
Intended jurisdiction for graph definition (if applicable)
A legal or geographic region in which the graph definition is intended to be used.
It may be possible for the graph definition 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
Explaination of why this graph definition is needed and why it has been designed as it has.
This element does not describe the usage of the graph definition 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 graph definition.
Type of resource at which the graph starts
The type of FHIR resource at which instances of this graph start.
One of the resource types defined as part of FHIR.
unique id for the element within a resource (for internal references)
Element `GraphDefinition.start` is mapped to FHIR STU3 element `GraphDefinition.start` as `SourceIsBroaderThanTarget`.
All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
The profile that describes the use of the base resource.
The code does not include the '$' prefix that is always included in the URL when the operation is invoked.
unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
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.
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.
Path in the resource that contains the link
Path in the resource that contains the link.
The path can be a literal path (e.g. Observation.subject), or it can be a query for reverse links (e.g. Provenance?target=[id]).
Information about why this link is of interest in this graph definition.
R4: `GraphDefinition.link.target.params` (new:string)
Element `GraphDefinition.link.target.params` has a context of GraphDefinition.link.target based on following the parent source element upwards and mapping to `GraphDefinition`. Element `GraphDefinition.link.target.params` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). At least one of the parameters must have the value {ref} which identifies the focus resource.
Element `GraphDefinition.link.target.type` is mapped to FHIR STU3 element `GraphDefinition.link.target.type` as `SourceIsBroaderThanTarget`.
R4: `GraphDefinition.link.target.compartment.use` (new:code)
Element `GraphDefinition.link.target.compartment.use` has a context of GraphDefinition.link.target.compartment based on following the parent source element upwards and mapping to `GraphDefinition`. Element `GraphDefinition.link.target.compartment.use` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). All conditional rules are evaluated; if they are true, then the rules are evaluated.
identical | matching | different | custom
identical | matching | different | no-rule | custom.