Profile Comparison between http://hl7.org/fhir/uv/livd/StructureDefinition/bundle-uv-livd vs http://hl7.org/fhir/uv/livd/StructureDefinition/bundle-uv-livd

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/Bundle
copyright
date	2018-08-14T00:00:00-04:00	2018-08-14	Values Differ
description	Explanation of what this profile contains/is for	LIVD constraints on the Bundle resource	Values Differ
experimental	false
fhirVersion	4.0.0	4.0.1	Values Differ
jurisdiction
jurisdiction[0]		http://unstats.un.org/unsd/methods/m49/m49.htm#001	Added the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#001'
kind	resource
name	LIVDBundle
publisher	Health Level Seven, Inc. - Orders and Observations WG	HL7 International - Orders and Observations Work Group	Values Differ
purpose
status	draft
title	LIVDBundle
type	Bundle
url	http://hl7.org/fhir/uv/livd/StructureDefinition/bundle-uv-livd
version	0.2.0	0.3.0	Values Differ

Structure

Name	L Flags	L Card.	L Type	L Description & Constraints	R Flags	R Card.	L Type	L Description & Constraints	Comments
Bundle	I				I
id	Σ				Σ
meta	Σ				Σ
implicitRules	?!Σ				?!Σ
language
identifier	SΣ				SΣ				Elements differ in definition: "A persistent identifier for the batch that won't change as a batch is copied from server to server." "A persistent identifier for the bundle that won't change as a bundle is copied from server to server."
type	SΣ				SΣ
timestamp	Σ				Σ
total	ΣI				ΣI				Elements differ in definition: "If a set of search matches, this is the total number of matches for the search (as opposed to the number of results in this bundle)." "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."
link	Σ				Σ
id
extension			Extension				Extension
modifierExtension	?!Σ				?!Σ
relation	Σ				Σ
url	Σ				Σ
entry	SΣI				SΣI				Elements differ in short: "Entry in the bundle - will have a resource, or information" "Entry in the bundle - will have a resource or information" Elements differ in definition: "An entry in a bundle resource - will either contain a resource, or information about a resource (transactions and history only)." "An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only)." Elements differ in comments: "The bundles must contain exactly one LIVDCatalogProfile instance, at least one LIVDCatalogEntryProfile instance, at least one LIVDDeviceDefinitionProfile instance, at least one LIVDConceptMapProfile instance, and at least one LIVDCodeSystemProfile instance." "The bundle must contain at least 6 entries such that there is at exactly one LIVDCatalogProfile instance, at least one LIVDCatalogEntryProfile instance, at least one LIVDDeviceDefinitionProfile instance, at least one LIVDConceptMapProfile instance, and at least one LIVDCodeSystemProfile instance."
id
extension			Extension				Extension
modifierExtension	?!Σ				?!Σ
link	Σ				Σ
fullUrl	SΣ				SΣ				Elements differ in short: "Absolute URL for resource (server address, or UUID/OID)" "URI for resource (Absolute URL server address or URI for UUID/OID)" Elements differ in definition: "The Absolute URL for the resource. The fullUrl SHALL not disagree with the id in the resource. 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." "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." Elements differ in comments: "fullUrl may not be [unique in the context of a resource]. Note that since [FHIR resources do not need to be served through the FHIR API], the absolute URL may not end with the logical id of the resource (Resource.id), but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex], then it SHALL end with the Resource.id." "fullUrl might not be [unique in the context of a resource]. Note that since [FHIR resources do not need to be served through the FHIR API], 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], 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)."
resource	SΣ				SΣ
search	ΣI				ΣI
id
extension			Extension				Extension
modifierExtension	?!Σ				?!Σ
mode	Σ				Σ				Elements differ in definition: "Why this entry is in the result set - whether it's included as a match or because of an _include requirement." "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."
score	Σ				Σ				Elements differ in comments: "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." "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] for the EMPI search which relates to this element."
request	SΣI				SΣI
id
extension			Extension				Extension
modifierExtension	?!Σ				?!Σ
method	SΣ				SΣ
url	SΣ				SΣ				Elements differ in comments: "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]"." "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]"."
ifNoneMatch	Σ				Σ
ifModifiedSince	Σ				Σ				Elements differ in short: "For managing update contention" "For managing cache currency"
ifMatch	Σ				Σ
ifNoneExist	Σ				Σ
response	ΣI				ΣI				Elements differ in short: "Transaction Related Information" "Results of execution (transaction/batch/history)" Elements differ in definition: "Additional information about how this entry should be processed as part of a transaction." "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."
id
extension			Extension				Extension
modifierExtension	?!Σ				?!Σ
status	Σ				Σ
location	Σ				Σ				Elements differ in short: "The location, if the operation returns a location" "The location (if the operation returns a location)" Elements differ in definition: "The location header created by processing this operation." "The location header created by processing this operation, populated if the operation returns a location."
etag	Σ				Σ				Elements differ in definition: "The etag for the resource, it the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning] and [Managing Resource Contention])." "The Etag for the resource, if the operation for the entry produced a versioned resource (see [Resource Metadata and Versioning] and [Managing Resource Contention])."
lastModified	Σ				Σ				Elements differ in comments: "This has to match the same time in the meta header if a resource is included." "This has to match the same time in the meta header (meta.lastUpdated) if a resource is included."
outcome	Σ				Σ				Elements differ in comments: "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." "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."
signature	SΣ				Σ				Elements differ in requirements: "This element allows capturing signatures on documents. It also allows signatures on messages, transactions or even query responses. It may 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." "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." Elements differ in definition for mustSupport: "true" "false"
Documentation for this format