• bdl-7: 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()
• bdl-9: A document must have an identifier with a system and a value
  type = 'document' implies (identifier.system.exists() and identifier.value.exists())
• bdl-3: entry.request mandatory for batch/transaction/history, otherwise prohibited
  entry.all(request.exists() = (%resource.type = 'batch' or %resource.type = 'transaction' or %resource.type = 'history'))
• bdl-4: 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'))
• bdl-12: A message must have a MessageHeader as the first resource
  type = 'message' implies entry.first().resource.is(MessageHeader)
• bdl-1: total only when a search or history
  total.empty() or (type = 'searchset') or (type = 'history')
• bdl-2: entry.search only when a search
  entry.search.empty() or (type = 'searchset')
• bdl-11: A document must have a Composition as the first resource
  type = 'document' implies entry.first().resource.is(Composition)
• bdl-10: A document must have a date
  type = 'document' implies (timestamp.hasValue())
• DOC-1: Document must be signed by author of document
  Bundle.entry.resource.ofType(Composition).author.resolve().ofType(Practitioner) = Bundle.signature.who.resolve()

• rim: Entity. Role, or Act
• v2: N/A
• rim: N/A
• cda: ClinicalDocument, if bundle.type = document

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a
• rim: N/A

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

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

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• DOC-2: Document identifier must be in OID format ad begin with urn:oid:([1-9][0-9]{0,3}|0){1,4}(\\.([1-9][0-9]{0,32}|0)){5,13}$
  value.matches("^urn:oid:.*")

• rim: n/a
• v2: CX / EI (occasionally, more often EI maps to a resource id or a URL)
• rim: II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
• servd: Identifier
• w5: FiveWs.identifier
• cda: ClinicalDocument.id

• rim: n/a

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• ext-1: Must have either extensions or value[x], not both
  extension.exists() != value.exists()

• rim: n/a
• rim: N/A

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a
• v2: N/A
• rim: Role.code or implied by context

Allows users to make use of identifiers when the identifier system is not known.

This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a
• v2: CE/CNE/CWE
• rim: CD
• orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
• v2: CX.5
• rim: Role.code or implied by context

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

Identifier.system is always case sensitive.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

urn:ietf:rfc:3986

• rim: n/a
• v2: CX.4 / EI-2-4
• rim: II.root or Role.id.root
• servd: ./IdentifierType

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a
• v2: CX.1 / EI.1
• rim: II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
• servd: ./Value

A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times").

Period is not used for a duration (a measure of elapsed time). See Duration.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• per-1: If present, start SHALL have a lower value than end
  start.hasValue().not() or end.hasValue().not() or (start <= end)

• rim: n/a
• v2: DR
• rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"]
• v2: CX.7 + CX.8
• rim: Role.effectiveTime or implied by context
• servd: ./StartDate and ./EndDate

The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• ref-1: SHALL have a contained resource if a local reference is provided
  reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))

• rim: n/a
• rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity)
• v2: CX.4 / (CX.4,CX.9,CX.10)
• rim: II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
• servd: ./IdentifierIssuingAuthority

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

document

• rim: n/a
• w5: FiveWs.class

For many bundles, the timestamp is equal to .meta.lastUpdated, because they are not stored (e.g. search results). When a bundle is placed in a persistent store, .meta.lastUpdated will be usually be changed by the server. When the bundle is a message, a middleware agent altering the message (even if not stored) SHOULD update .meta.lastUpdated. .timestamp is used to track the original time of the Bundle, and SHOULD be populated.

Usage:

• document : the date the document was created. Note: the composition may predate the document, or be associated with multiple documents. The date of the composition - the authoring time - may be earlier than the document assembly time
• message : the date that the content of the message was assembled. This date is not changed by middleware engines unless they add additional data that changes the meaning of the time of the message
• history : the date that the history was assembled. This time would be used as the _since time to ask for subsequent updates
• searchset : the time that the search set was assembled. Note that different pages MAY have different timestamps but need not. Having different timestamps does not imply that subsequent pages will represent or include changes made since the initial query
• transaction | transaction-response | batch | batch-response | collection : no particular assigned meaning

The timestamp value should be greater than the lastUpdated and other timestamps in the resources in the bundle, and it should be equal or earlier than the .meta.lastUpdated on the Bundle itself.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a
• w5: FiveWs.init
• cda: ClinicalDocument.effectiveTime

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. HATEOAS).

Bundle.entry.link corresponds to links found in the HTTP header if the resource in the entry was read directly.

This specification defines some specific uses of Bundle.link for searching and paging, but no specific uses for Bundle.entry.link, and no defined function in a transaction - the meaning is implementation specific.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

• rim: n/a

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• ext-1: Must have either extensions or value[x], not both
  extension.exists() != value.exists()

• rim: n/a
• rim: N/A

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.

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• ext-1: Must have either extensions or value[x], not both
  extension.exists() != value.exists()

• rim: n/a
• rim: N/A

Note that FHIR strings SHALL NOT exceed 1MB in size

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

see http://en.wikipedia.org/wiki/Uniform_resource_identifier

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• bdl-8: fullUrl cannot be a version specific reference
  fullUrl.contains('/_history/').not()
• bdl-5: must be a resource unless there's a request or response
  resource.exists() or request.exists() or response.exists()

• rim: n/a

• rim: n/a

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• ext-1: Must have either extensions or value[x], not both
  extension.exists() != value.exists()

• rim: n/a
• rim: N/A

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.

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• ext-1: Must have either extensions or value[x], not both
  extension.exists() != value.exists()

• rim: n/a
• rim: N/A

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

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

• rim: Entity. Role, or Act

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

• rim: n/a

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• ext-1: Must have either extensions or value[x], not both
  extension.exists() != value.exists()

• rim: n/a
• rim: N/A

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.

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• ext-1: Must have either extensions or value[x], not both
  extension.exists() != value.exists()

• rim: n/a
• rim: N/A

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

• rim: n/a

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• ext-1: Must have either extensions or value[x], not both
  extension.exists() != value.exists()

• rim: n/a
• rim: N/A

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.

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• ext-1: Must have either extensions or value[x], not both
  extension.exists() != value.exists()

• rim: n/a
• rim: N/A

Note that FHIR strings SHALL NOT exceed 1MB in size

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

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]".

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

Note that FHIR strings SHALL NOT exceed 1MB in size

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

Note: This is intended for where precisely observed times are required, typically system logs etc., and not human-reported times - for them, see date and dateTime (which can be as precise as instant, but is not required to be) below. Time zone is always required

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

Note that FHIR strings SHALL NOT exceed 1MB in size

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

Note that FHIR strings SHALL NOT exceed 1MB in size

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

• rim: n/a

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• ext-1: Must have either extensions or value[x], not both
  extension.exists() != value.exists()

• rim: n/a
• rim: N/A

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.

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• ext-1: Must have either extensions or value[x], not both
  extension.exists() != value.exists()

• rim: n/a
• rim: N/A

Note that FHIR strings SHALL NOT exceed 1MB in size

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

see http://en.wikipedia.org/wiki/Uniform_resource_identifier

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

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.

• rim: Entity. Role, or Act

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.

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a
• rim: N/A

• rim: n/a

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• ext-1: Must have either extensions or value[x], not both
  extension.exists() != value.exists()

• rim: n/a
• rim: N/A

Examples include attesting to: authorship, correct transcription, and witness of specific event. Also known as a "Commitment Type Indication".

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

{
  "system": "urn:iso-astm:E1762-95:2013",
  "code": "1.2.840.10065.1.12.1.1"
}

• rim: n/a
• v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6
• rim: CV
• orim: fhir:Coding rdfs:subClassOf dt:CDCoding

This should agree with the information in the signature.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

This should agree with the information in the signature.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• ref-1: SHALL have a contained resource if a local reference is provided
  reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
• DOC-3: Local reference must be used to specify signer of document
  reference.matches("^urn:uuid:.*")

• rim: n/a
• rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity)

• rim: n/a

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.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• ext-1: Must have either extensions or value[x], not both
  extension.exists() != value.exists()

• rim: n/a
• rim: N/A

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a
• rim: N/A

This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a
• rim: N/A

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a
• v2: CX / EI (occasionally, more often EI maps to a resource id or a URL)
• rim: II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
• servd: Identifier
• rim: .identifier

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a
• rim: N/A

used when the signature is on behalf of a non-signer.

The party that can't sign. For example a child.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())
• ref-1: SHALL have a contained resource if a local reference is provided
  reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))

• rim: n/a
• rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity)

"xml", "json" and "ttl" are allowed, which describe the simple encodings described in the specification (and imply appropriate bundle support). Otherwise, mime types are legal here.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

Note that FHIR strings SHALL NOT exceed 1MB in size

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a

Where the signature type is an XML DigSig, the signed content is a FHIR Resource(s), the signature is of the XML form of the Resource(s) using XML-Signature (XMLDIG) "Detached Signature" form.

• ele-1: All FHIR elements must have a @value or children
  hasValue() or (children().count() > id.count())

• rim: n/a