Name Flags Card. Type Description & Constraints Bundle 0..* Bundle 保健指導結果報告書 meta S 0..1 Meta Metadata about the resource profile S 0..* canonical(StructureDefinition) 保健指導結果報告書のプロファイルを識別するURL type S 1..1 code ドキュメント型 Fixed Value: document timestamp S 0..1 instant 保健指導結果報告書を⽣成した⽇時 Slices for entry 0..* BackboneElement リソースエントリー Slice: Unordered, Open by value:fullUrl entry:Composition S 0..* BackboneElement ⽂書構成情報のエントリー fullUrl S 0..1 uri ⽂書構成情報のUUID resource S 0..1 Composition ⽂書構成情報 entry:Patient S 0..* BackboneElement 受診者情報のエントリー fullUrl S 0..1 uri 受診者情報のUUID resource S 0..1 Patient 受診者情報 entry:PractitionerRole S 0..* BackboneElement 保健指導結果作成者役割情報のエントリー fullUrl S 0..1 uri 保健指導結果作成者役割情報のUUID resource S 0..1 PractitionerRole 保健指導結果作成者役割情報 entry:Organization S 0..* BackboneElement 保健指導結果作成組織情報のエントリー fullUrl S 0..1 uri 保健指導結果作成組織情報のUUID resource S 0..1 Organization 保健指導結果作成組織情報 entry:Practitioner S 0..* BackboneElement 保健指導結果作成者情報のエントリー fullUrl S 0..1 uri 保健指導結果作成者情報のUUID resource S 0..1 Practitioner 保健指導結果作成者情報 entry:Encounter S 0..* BackboneElement 保健指導実施情報のエントリー fullUrl S 0..1 uri 保健指導実施情報のUUID resource S 0..1 Encounter 保健指導実施情報 entry:Coverage1 S 0..* BackboneElement 受診券情報のエントリー fullUrl S 0..1 uri 受診券情報のUUID resource S 0..1 Coverage 受診券情報 entry:Coverage2 S 0..* BackboneElement 保険情報のエントリー fullUrl S 0..1 uri 保険情報のUUID resource S 0..1 Coverage 保険情報 entry:ServiceRequest S 0..* BackboneElement 保健指導項⽬情報のエントリー fullUrl S 0..1 uri 保健指導項⽬情報のUUID resource S 0..1 ServiceRequest 保健指導項⽬情報 entry:Specimen S 0..* BackboneElement 検体情報のエントリー fullUrl S 0..1 uri 検体情報のUUID resource S 0..1 Specimen 検体情報 entry:DiagnosticReport S 0..* BackboneElement 健診結果画像情報のエントリー fullUrl S 0..1 uri 健診結果画像情報のUUID resource S 0..1 DiagnosticReport 健診結果画像情報 entry:Media S 0..* BackboneElement 保健指導結果画像情報のエントリー fullUrl S 0..1 uri 保健指導結果画像情報のUUID resource S 0..1 Media 保健指導結果画像情報 entry:DocumentReference S 0..* BackboneElement 添付⽂書情報のエントリー fullUrl S 0..1 uri 添付⽂書情報のUUID resource S 0..1 DocumentReference 添付⽂書情報 Documentation for this format
total.empty() or (type = 'searchset') or (type = 'history')
not(f:total) or (f:type/@value = 'searchset') or (f:type/@value = 'history')
entry.search.empty() or (type = 'searchset')
not(f:entry/f:search) or (f:type/@value = 'searchset')
entry.request mandatory for batch/transaction/history, otherwise prohibited
entry.all(request.exists() = (%resource.type = 'batch' or %resource.type = 'transaction' or %resource.type = 'history'))
not(f:entry/f:request) or (f:type/@value = 'batch') or (f:type/@value = 'transaction') or (f:type/@value = 'history')
entry.response mandatory for batch-response/transaction-response/history, otherwise prohibited
entry.all(response.exists() = (%resource.type = 'batch-response' or %resource.type = 'transaction-response' or %resource.type = 'history'))
not(f:entry/f:response) or (f:type/@value = 'batch-response') or (f:type/@value = 'transaction-response') or (f:type/@value = 'history')
FullUrl must be unique in a bundle, or else entries with the same fullUrl must have different meta.versionId (except in history bundles)
(type = 'history') or entry.where(fullUrl.exists()).select(fullUrl&resource.meta.versionId).isDistinct()
(f:type/@value = 'history') or (count(for $entry in f:entry[f:resource] return $entry[count(parent::f:Bundle/f:entry[f:fullUrl/@value=$entry/f:fullUrl/@value and ((not(f:resource/*/f:meta/f:versionId/@value) and not($entry/f:resource/*/f:meta/f:versionId/@value)) or f:resource/*/f:meta/f:versionId/@value=$entry/f:resource/*/f:meta/f:versionId/@value)])!=1])=0)
A document must have an identifier with a system and a value
type = 'document' implies (identifier.system.exists() and identifier.value.exists())
not(f:type/@value = 'document') or exists(f:identifier/f:system) or exists(f:identifier/f:value)
type = 'document' implies (timestamp.hasValue())
not(f:type/@value = 'document') or exists(f:timestamp/@value)
A document must have a Composition as the first resource
type = 'document' implies entry.first().resource.is(Composition)
not(f:type/@value='document') or f:entry[1]/f:resource/f:Composition
A message must have a MessageHeader as the first resource
type = 'message' implies entry.first().resource.is(MessageHeader)
not(f:type/@value='message') or f:entry[1]/f:resource/f:MessageHeader
ClinicalDocument, if bundle.type = document
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())
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.
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
The version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted.
The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
When the resource last changed - e.g. when the version changed.
This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a [read](http://hl7.org/fhir/R4/http.html#read) interaction.
Identifies where the resource comes from
A uri that identifies the source system of the resource. This provides a minimal amount of [Provenance](http://hl7.org/fhir/R4/provenance.html#) information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc.
In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
保健指導結果報告書のプロファイルを識別するURL
保健指導結果報告書のプロファイルを識別するURLです。
It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.
Security Labels applied to this resource
Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.
The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.
Security Labels from the Healthcare Privacy and Security Classification System.
Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.
The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.
Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
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).
A persistent identifier for the bundle that won't change as a bundle is copied from server to server.
Persistent identity generally only matters for batches of type Document, Message, and Collection. It would not normally be populated for search and history results and servers ignore Bundle.identifier when processing batches and transactions. For Documents the .identifier SHALL be populated such that the .identifier is globally unique.
It's possible to use a bundle for other purposes (e.g. a document can be accepted as a transaction). This is primarily defined so that there can be specific rules for some of the bundle types.
Indicates the purpose of a bundle - how it is intended to be used.
保健指導結果報告書を⽣成した⽇時です。
If a set of search matches, this is the total number of entries of type 'match' across all pages in the search. It does not include search.mode = 'include' or 'outcome' entries and it does not provide a count of the number of entries in the Bundle.
Only used if the bundle is a search result set. The total does not include resources such as OperationOutcome and included resources, only the total number of matching resources.
A series of links that provide context to this bundle.
Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. [HATEOAS](http://en.wikipedia.org/wiki/HATEOAS)). Bundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was [read](http://hl7.org/fhir/R4/http.html#read) directly. This specification defines some specific uses of Bundle.link for [searching](http://hl7.org/fhir/R4/search.html#conformance) and [paging](http://hl7.org/fhir/R4/http.html#paging), but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific.
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 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 element that contains them
See http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1
A name which details the functional use for this link - see [http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1](http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1).
For bundles of type 'document' and 'message', the first resource is special (must be Composition or MessageHeader respectively). For all bundles, the meaning of the order of entries depends on the bundle type
must be a resource unless there's a request or response
resource.exists() or request.exists() or response.exists()
exists(f:resource) or exists(f:request) or exists(f:response)
fullUrl cannot be a version specific reference
not(exists(f:fullUrl[contains(string(@value), '/_history/')]))
A series of links that provide context to this entry.
URI for resource (Absolute URL server address or URI for UUID/OID)
The Absolute URL for the resource. The fullUrl SHALL NOT disagree with the id in the resource - i.e. if the fullUrl is not a urn:uuid, the URL shall be version-independent URL consistent with the Resource.id. The fullUrl is a version independent reference to the resource. The fullUrl element SHALL have a value except that: * fullUrl can be empty on a POST (although it does not need to when specifying a temporary id for reference in the bundle) * Results from operations might involve resources that are not identified.
fullUrl might not be [unique in the context of a resource](http://hl7.org/fhir/R4/bundle.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](http://hl7.org/fhir/R4/references.html), the fullURL might be a URN or an absolute URL that does not end with the logical id of the resource (Resource.id). However, but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](http://hl7.org/fhir/R4/references.html#regex), then the 'id' portion of the fullUrl SHALL end with the Resource.id. Note that the fullUrl is not the same as the canonical URL - it's an absolute url for an endpoint serving the resource (these will happen to have the same value on the canonical server for the resource with the canonical URL).
The Resource for the entry. The purpose/meaning of the resource is determined by the Bundle.type.
Information about the search process that lead to the creation of this entry.
match | include | outcome - why this is in the result set
Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process.
There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.
Why an entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process.
When searching, the server's search ranking score for the entry.
Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order. See [Patient Match](http://hl7.org/fhir/R4/patient-operation-match.html) for the EMPI search which relates to this element.
Additional execution information (transaction/batch/history)
Additional information about how this entry should be processed as part of a transaction or batch. For history, it shows how the entry was processed to create the version contained in the entry.
GET | HEAD | POST | PUT | DELETE | PATCH
In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred.
HTTP verbs (in the HTTP command line). See [HTTP rfc](https://tools.ietf.org/html/rfc7231) for details.
The URL for this entry, relative to the root (the address to which the request is posted).
E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT and the URL would be "Patient/[id]".
If the ETag values match, return a 304 Not Modified status. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).
Only perform the operation if the last updated date matches. See the API documentation for ["Conditional Read"](http://hl7.org/fhir/R4/http.html#cread).
Only perform the operation if the Etag value matches. For more information, see the API section ["Managing Resource Contention"](http://hl7.org/fhir/R4/http.html#concurrency).
Instruct the server not to perform the create if a specified resource already exists. For further information, see the API documentation for ["Conditional Create"](http://hl7.org/fhir/R4/http.html#ccreate). This is just the query portion of the URL - what follows the "?" (not including the "?").
Results of execution (transaction/batch/history)
Indicates the results of processing the corresponding 'request' entry in the batch or transaction being responded to or what the results of an operation where when returning history.
The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.
The location (if the operation returns a location)
The location header created by processing this operation, populated if the operation returns a location.
The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning](http://hl7.org/fhir/R4/http.html#versioning) and [Managing Resource Contention](http://hl7.org/fhir/R4/http.html#concurrency)).
Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.
The date/time that the resource was modified on the server.
This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.
OperationOutcome with hints and warnings (for batch/transaction)
An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction.
For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned. This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.
While the focus of this specification is on patient-specific clinical statements, this resource can also apply to other healthcare-related statements such as study protocol designs, healthcare invoices and other activities that are not necessarily patient-specific or clinical.
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
Document[classCode="DOC" and moodCode="EVN" and isNormalAct()]
保健指導結果作成者役割情報のエントリー
保健指導結果作成者役割情報のエントリーです。
保健指導結果作成者役割情報です。
保健指導結果作成組織情報のエントリー
保健指導結果作成組織情報のエントリーです。
保健指導結果作成組織情報のUUIDです。
The organization SHALL at least have a name or an identifier, and possibly more than one
Organization(classCode=ORG, determinerCode=INST)
保健指導結果作成者情報のエントリー
保健指導結果作成者情報のエントリーです。
保健指導実施情報のエントリーです。
保険対象者(患者)と保険者の間のリンクを提供します。
保健指導項⽬情報のエントリーです。
orderDetail SHALL only be present if code is present
exists(f:code) or not(exists(f:orderDetail))
健診結果画像情報のエントリーです。
This is intended to capture a single report and is not suitable for use in displaying summary information that covers multiple reports. For example, this resource has not been designed for laboratory cumulative reporting formats nor detailed structured reports for sequencing.
Observation[classCode=OBS, moodCode=EVN]
保健指導結果画像情報のエントリー
保健指導結果画像情報のエントリーです。
Usually, this is used for documents other than those defined by FHIR.
Document[classCode="DOC" and moodCode="EVN"]
Digital Signature - base64 encoded. XML-DSig or a JWT.
The signature could be created by the "author" of the bundle or by the originating device. Requirements around inclusion of a signature, verification of signatures and treatment of signed/non-signed bundles is implementation-environment specific.
A Signature holds an electronic representation of a signature and its supporting context in a FHIR accessible form. The signature may either be a cryptographic type (XML DigSig or a JWS), which is able to provide non-repudiation proof, or it may be a graphical image that represents a signature or a signature process. This element allows capturing signatures on documents, messages, transactions or even search responses, to support content-authentication, non-repudiation or other business cases. This is primarily relevant where the bundle may travel through multiple hops or via other mechanisms where HTTPS non-repudiation is insufficient.