# entry[].resource.description
The C-CDA on FHIR Authorization Extension contains the C-CDA on FHIR Consent profile which represents information about a patient's consent.

For further information see the C-CDA specification here: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=408.

# entry[].resource.text.div
Resource Text Observation Display Test

# entry[].resource.snapshot.element[].short
Information about an individual or animal receiving health care services

# entry[].resource.snapshot.element[].definition
Demographics and other administrative information about an individual or animal receiving care or other health-related services.

# entry[].resource.snapshot.element[].definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The version specific identifier, as it appears in the version portion of the URL. This values changes when the resource is created, updated, or deleted.

# entry[].resource.snapshot.element[].definition
When the resource last changed - e.g. when the version changed.

# entry[].resource.snapshot.element[].short
Profiles this resource claims to conform to

# entry[].resource.snapshot.element[].definition
A list of profiles [[[StructureDefinition]]]s that this resource claims to conform to. The URL is a reference to [[[StructureDefinition.url]]].

# entry[].resource.snapshot.element[].short
Security Labels applied to this resource

# entry[].resource.snapshot.element[].definition
Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.

# entry[].resource.snapshot.element[].binding.description
Security Labels from the Healthcare Privacy and Security Classification System.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The identification of the code system that defines the meaning of the symbol in the code.

# entry[].resource.snapshot.element[].requirements
Need to be unambiguous about the source of the definition of the symbol.

# entry[].resource.snapshot.element[].definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

# entry[].resource.snapshot.element[].definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

# entry[].resource.snapshot.element[].requirements
Need to refer to a particular code in the system.

# entry[].resource.snapshot.element[].definition
A representation of the meaning of the code in the system, following the rules of the system.

# entry[].resource.snapshot.element[].requirements
Need to be able to carry a human-readable meaning of the code for readers that do not know  the system.

# entry[].resource.snapshot.element[].mapping[].map
C*E.2 - but note this is not well followed

# entry[].resource.snapshot.element[].short
If this coding was chosen directly by the user

# entry[].resource.snapshot.element[].definition
Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

# entry[].resource.snapshot.element[].requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

# entry[].resource.snapshot.element[].mapping[].map
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map;   fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [     fhir:source "true";     fhir:target dt:CDCoding.codingRationale\#O   ]

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].binding.description
Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones"

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The identification of the code system that defines the meaning of the symbol in the code.

# entry[].resource.snapshot.element[].requirements
Need to be unambiguous about the source of the definition of the symbol.

# entry[].resource.snapshot.element[].definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

# entry[].resource.snapshot.element[].definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

# entry[].resource.snapshot.element[].requirements
Need to refer to a particular code in the system.

# entry[].resource.snapshot.element[].definition
A representation of the meaning of the code in the system, following the rules of the system.

# entry[].resource.snapshot.element[].requirements
Need to be able to carry a human-readable meaning of the code for readers that do not know  the system.

# entry[].resource.snapshot.element[].mapping[].map
C*E.2 - but note this is not well followed

# entry[].resource.snapshot.element[].short
If this coding was chosen directly by the user

# entry[].resource.snapshot.element[].definition
Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

# entry[].resource.snapshot.element[].requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

# entry[].resource.snapshot.element[].mapping[].map
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map;   fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [     fhir:source "true";     fhir:target dt:CDCoding.codingRationale\#O   ]

# entry[].resource.snapshot.element[].short
A set of rules under which this content was created

# entry[].resource.snapshot.element[].definition
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

# entry[].resource.snapshot.element[].definition
The base language in which the resource is written.

# entry[].resource.snapshot.element[].short
Text summary of the resource, for human interpretation

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].short
generated | extensions | additional | empty

# entry[].resource.snapshot.element[].definition
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data.

# entry[].resource.snapshot.element[].definition
The actual narrative content, a stripped down version of XHTML.

# entry[].resource.snapshot.element[].constraint[].human
The narrative SHALL contain only the basic html formatting attributes described in chapters 7-11 (except section 4 of chapter 9) and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained style attributes

# entry[].resource.snapshot.element[].constraint[].xpath
not(descendant-or-self::*/@*[not(name(.)=('abbr', 'accesskey', 'align', 'alt', 'axis', 'bgcolor', 'border', 'cellhalign', 'cellpadding', 'cellspacing', 'cellvalign', 'char', 'charoff', 'charset', 'cite', 'class', 'colspan', 'compact', 'coords', 'dir', 'frame', 'headers', 'height', 'href', 'hreflang', 'hspace', 'id', 'lang', 'longdesc', 'name', 'nowrap', 'rel', 'rev', 'rowspan', 'rules', 'scope', 'shape', 'span', 'src', 'start', 'style', 'summary', 'tabindex', 'title', 'type', 'valign', 'value', 'vspace', 'width'))])

# entry[].resource.snapshot.element[].constraint[].human
The narrative SHALL contain only the basic html formatting elements described in chapters 7-11 (except section 4 of chapter 9) and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained style attributes

# entry[].resource.snapshot.element[].constraint[].human
The narrative SHALL have some non-whitespace content

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The version specific identifier, as it appears in the version portion of the URL. This values changes when the resource is created, updated, or deleted.

# entry[].resource.snapshot.element[].definition
When the resource last changed - e.g. when the version changed.

# entry[].resource.snapshot.element[].short
Profiles this resource claims to conform to

# entry[].resource.snapshot.element[].definition
A list of profiles [[[StructureDefinition]]]s that this resource claims to conform to. The URL is a reference to [[[StructureDefinition.url]]].

# entry[].resource.snapshot.element[].short
Security Labels applied to this resource

# entry[].resource.snapshot.element[].definition
Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.

# entry[].resource.snapshot.element[].binding.description
Security Labels from the Healthcare Privacy and Security Classification System.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The identification of the code system that defines the meaning of the symbol in the code.

# entry[].resource.snapshot.element[].requirements
Need to be unambiguous about the source of the definition of the symbol.

# entry[].resource.snapshot.element[].definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

# entry[].resource.snapshot.element[].definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

# entry[].resource.snapshot.element[].requirements
Need to refer to a particular code in the system.

# entry[].resource.snapshot.element[].definition
A representation of the meaning of the code in the system, following the rules of the system.

# entry[].resource.snapshot.element[].requirements
Need to be able to carry a human-readable meaning of the code for readers that do not know  the system.

# entry[].resource.snapshot.element[].mapping[].map
C*E.2 - but note this is not well followed

# entry[].resource.snapshot.element[].short
If this coding was chosen directly by the user

# entry[].resource.snapshot.element[].definition
Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

# entry[].resource.snapshot.element[].requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

# entry[].resource.snapshot.element[].mapping[].map
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map;   fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [     fhir:source "true";     fhir:target dt:CDCoding.codingRationale\#O   ]

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].binding.description
Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones"

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The identification of the code system that defines the meaning of the symbol in the code.

# entry[].resource.snapshot.element[].requirements
Need to be unambiguous about the source of the definition of the symbol.

# entry[].resource.snapshot.element[].definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

# entry[].resource.snapshot.element[].definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

# entry[].resource.snapshot.element[].requirements
Need to refer to a particular code in the system.

# entry[].resource.snapshot.element[].definition
A representation of the meaning of the code in the system, following the rules of the system.

# entry[].resource.snapshot.element[].requirements
Need to be able to carry a human-readable meaning of the code for readers that do not know  the system.

# entry[].resource.snapshot.element[].mapping[].map
C*E.2 - but note this is not well followed

# entry[].resource.snapshot.element[].short
If this coding was chosen directly by the user

# entry[].resource.snapshot.element[].definition
Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

# entry[].resource.snapshot.element[].requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

# entry[].resource.snapshot.element[].mapping[].map
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map;   fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [     fhir:source "true";     fhir:target dt:CDCoding.codingRationale\#O   ]

# entry[].resource.snapshot.element[].short
A set of rules under which this content was created

# entry[].resource.snapshot.element[].definition
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

# entry[].resource.snapshot.element[].definition
The base language in which the resource is written.

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].requirements
Patients are almost always assigned specific numerical identifiers.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].short
usual | official | temp | secondary (If known)

# entry[].resource.snapshot.element[].requirements
Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

# entry[].resource.snapshot.element[].binding.description
Identifies the purpose for this identifier, if known .

# entry[].resource.snapshot.element[].definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.

# entry[].resource.snapshot.element[].requirements
Allows users to make use of identifiers when the identifier system is not known.

# entry[].resource.snapshot.element[].binding.description
A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
A reference to a code defined by a terminology system.

# entry[].resource.snapshot.element[].requirements
Allows for translations and alternate encodings within a code system.  Also supports communication of the same instance to systems requiring different encodings.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The identification of the code system that defines the meaning of the symbol in the code.

# entry[].resource.snapshot.element[].requirements
Need to be unambiguous about the source of the definition of the symbol.

# entry[].resource.snapshot.element[].definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

# entry[].resource.snapshot.element[].definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

# entry[].resource.snapshot.element[].requirements
Need to refer to a particular code in the system.

# entry[].resource.snapshot.element[].definition
A representation of the meaning of the code in the system, following the rules of the system.

# entry[].resource.snapshot.element[].requirements
Need to be able to carry a human-readable meaning of the code for readers that do not know  the system.

# entry[].resource.snapshot.element[].mapping[].map
C*E.2 - but note this is not well followed

# entry[].resource.snapshot.element[].short
If this coding was chosen directly by the user

# entry[].resource.snapshot.element[].definition
Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

# entry[].resource.snapshot.element[].requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

# entry[].resource.snapshot.element[].mapping[].map
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map;   fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [     fhir:source "true";     fhir:target dt:CDCoding.codingRationale\#O   ]

# entry[].resource.snapshot.element[].short
Plain text representation of the concept

# entry[].resource.snapshot.element[].definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

# entry[].resource.snapshot.element[].requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

# entry[].resource.snapshot.element[].mapping[].map
C*E.9. But note many systems use C*E.2 for this

# entry[].resource.snapshot.element[].definition
Establishes the namespace in which set of possible id values is unique.

# entry[].resource.snapshot.element[].requirements
There are many sequences of identifiers.  To perform matching, we need to know what sequence we're dealing with. The system identifies a particular sequence or set of unique identifiers.

# entry[].resource.snapshot.element[].definition
The portion of the identifier typically displayed to the user and which is unique within the context of the system.

# entry[].resource.snapshot.element[].mapping[].map
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)

# entry[].resource.snapshot.element[].short
Time period when id is/was valid for use

# entry[].resource.snapshot.element[].definition
Time period during which identifier is/was valid for use.

# entry[].resource.snapshot.element[].mapping[].map
Role.effectiveTime or implied by context

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The start of the period. The boundary is inclusive.

# entry[].resource.snapshot.element[].short
End time with inclusive boundary, if not ongoing

# entry[].resource.snapshot.element[].definition
The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.

# entry[].resource.snapshot.element[].meaningWhenMissing
If the end of the period is missing, it means that the period is ongoing

# entry[].resource.snapshot.element[].short
Organization that issued id (may be just text)

# entry[].resource.snapshot.element[].definition
Organization that issued/manages the identifier.

# entry[].resource.snapshot.element[].mapping[].map
II.assigningAuthorityName but note that this is an improper use by the definition of the field.  Also Role.scoper

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].short
Relative, internal or absolute URL reference

# entry[].resource.snapshot.element[].definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

# entry[].resource.snapshot.element[].definition
Plain text narrative that identifies the resource in addition to the resource reference.

# entry[].resource.snapshot.element[].requirements
Patients are almost always assigned specific numerical identifiers.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].short
usual | official | temp | secondary (If known)

# entry[].resource.snapshot.element[].requirements
Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

# entry[].resource.snapshot.element[].binding.description
Identifies the purpose for this identifier, if known .

# entry[].resource.snapshot.element[].definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.

# entry[].resource.snapshot.element[].requirements
Allows users to make use of identifiers when the identifier system is not known.

# entry[].resource.snapshot.element[].binding.description
A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
A reference to a code defined by a terminology system.

# entry[].resource.snapshot.element[].requirements
Allows for translations and alternate encodings within a code system.  Also supports communication of the same instance to systems requiring different encodings.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The identification of the code system that defines the meaning of the symbol in the code.

# entry[].resource.snapshot.element[].requirements
Need to be unambiguous about the source of the definition of the symbol.

# entry[].resource.snapshot.element[].definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

# entry[].resource.snapshot.element[].definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

# entry[].resource.snapshot.element[].requirements
Need to refer to a particular code in the system.

# entry[].resource.snapshot.element[].definition
A representation of the meaning of the code in the system, following the rules of the system.

# entry[].resource.snapshot.element[].requirements
Need to be able to carry a human-readable meaning of the code for readers that do not know  the system.

# entry[].resource.snapshot.element[].mapping[].map
C*E.2 - but note this is not well followed

# entry[].resource.snapshot.element[].short
If this coding was chosen directly by the user

# entry[].resource.snapshot.element[].definition
Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

# entry[].resource.snapshot.element[].requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

# entry[].resource.snapshot.element[].mapping[].map
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map;   fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [     fhir:source "true";     fhir:target dt:CDCoding.codingRationale\#O   ]

# entry[].resource.snapshot.element[].short
Plain text representation of the concept

# entry[].resource.snapshot.element[].definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

# entry[].resource.snapshot.element[].requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

# entry[].resource.snapshot.element[].mapping[].map
C*E.9. But note many systems use C*E.2 for this

# entry[].resource.snapshot.element[].definition
Establishes the namespace in which set of possible id values is unique.

# entry[].resource.snapshot.element[].requirements
There are many sequences of identifiers.  To perform matching, we need to know what sequence we're dealing with. The system identifies a particular sequence or set of unique identifiers.

# entry[].resource.snapshot.element[].definition
The portion of the identifier typically displayed to the user and which is unique within the context of the system.

# entry[].resource.snapshot.element[].mapping[].map
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)

# entry[].resource.snapshot.element[].short
Time period when id is/was valid for use

# entry[].resource.snapshot.element[].definition
Time period during which identifier is/was valid for use.

# entry[].resource.snapshot.element[].mapping[].map
Role.effectiveTime or implied by context

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The start of the period. The boundary is inclusive.

# entry[].resource.snapshot.element[].short
End time with inclusive boundary, if not ongoing

# entry[].resource.snapshot.element[].definition
The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.

# entry[].resource.snapshot.element[].meaningWhenMissing
If the end of the period is missing, it means that the period is ongoing

# entry[].resource.snapshot.element[].short
Organization that issued id (may be just text)

# entry[].resource.snapshot.element[].definition
Organization that issued/manages the identifier.

# entry[].resource.snapshot.element[].mapping[].map
II.assigningAuthorityName but note that this is an improper use by the definition of the field.  Also Role.scoper

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].short
Relative, internal or absolute URL reference

# entry[].resource.snapshot.element[].definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

# entry[].resource.snapshot.element[].definition
Plain text narrative that identifies the resource in addition to the resource reference.

# entry[].resource.snapshot.element[].short
Whether this patient's record is in active use

# entry[].resource.snapshot.element[].definition
Whether this patient record is in active use.

# entry[].resource.snapshot.element[].requirements
Need to be able to mark a patient record as not to be used because it was created in error.

# entry[].resource.snapshot.element[].requirements
Need to be able to track the patient by multiple names. Examples are your official name and a partner name.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].short
usual | official | temp | nickname | anonymous | old | maiden

# entry[].resource.snapshot.element[].requirements
Allows the appropriate name for a particular context of use to be selected from among a set of names.

# entry[].resource.snapshot.element[].mapping[].map
XPN.7, but often indicated by which field contains the name

# entry[].resource.snapshot.element[].definition
The part of a name that links to the genealogy. In some cultures (e.g. Eritrea) the family name of a son is the first name of his father.

# entry[].resource.snapshot.element[].short
Given names (not always 'first'). Includes middle names

# entry[].resource.snapshot.element[].definition
Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the start of the name.

# entry[].resource.snapshot.element[].definition
Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the end of the name.

# entry[].resource.snapshot.element[].definition
Indicates the period of time when this name was valid for the named person.

# entry[].resource.snapshot.element[].requirements
Allows names to be placed in historical context.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The start of the period. The boundary is inclusive.

# entry[].resource.snapshot.element[].short
End time with inclusive boundary, if not ongoing

# entry[].resource.snapshot.element[].definition
The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.

# entry[].resource.snapshot.element[].meaningWhenMissing
If the end of the period is missing, it means that the period is ongoing

# entry[].resource.snapshot.element[].definition
A contact detail (e.g. a telephone number or an email address) by which the individual may be contacted.

# entry[].resource.snapshot.element[].requirements
People have (primary) ways to contact them in some way such as phone, email.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
Telecommunications form for contact point - what communications system is required to make use of the contact.

# entry[].resource.snapshot.element[].binding.description
Telecommunications form for contact point

# entry[].resource.snapshot.element[].definition
The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address).

# entry[].resource.snapshot.element[].requirements
Need to support legacy numbers that are not in a tightly controlled format.

# entry[].resource.snapshot.element[].short
home | work | temp | old | mobile - purpose of this contact point

# entry[].resource.snapshot.element[].definition
Identifies the purpose for the contact point.

# entry[].resource.snapshot.element[].requirements
Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose.

# entry[].resource.snapshot.element[].short
Specify preferred order of use (1 = highest)

# entry[].resource.snapshot.element[].definition
Specifies a preferred order in which to use a set of contacts. Contacts are ranked with lower values coming before higher values.

# entry[].resource.snapshot.element[].short
Time period when the contact point was/is in use

# entry[].resource.snapshot.element[].definition
Time period when the contact point was/is in use.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The start of the period. The boundary is inclusive.

# entry[].resource.snapshot.element[].short
End time with inclusive boundary, if not ongoing

# entry[].resource.snapshot.element[].definition
The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.

# entry[].resource.snapshot.element[].meaningWhenMissing
If the end of the period is missing, it means that the period is ongoing

# entry[].resource.snapshot.element[].definition
Administrative Gender - the gender that the patient is considered to have for administration and record keeping purposes.

# entry[].resource.snapshot.element[].requirements
Needed for identification of the individual, in combination with (at least) name and birth date. Gender of individual drives many clinical processes.

# entry[].resource.snapshot.element[].binding.description
The gender of a person used for administrative purposes.

# entry[].resource.snapshot.element[].requirements
Age of the individual drives many clinical processes.

# entry[].resource.snapshot.element[].short
Indicates if the individual is deceased or not

# entry[].resource.snapshot.element[].definition
Indicates if the individual is deceased or not.

# entry[].resource.snapshot.element[].requirements
The fact that a patient is deceased influences the clinical process. Also, in human communication and relation management it is necessary to know whether the person is alive.

# entry[].resource.snapshot.element[].requirements
May need to keep track of patient addresses for contacting, billing or reporting requirements and also to help with identification.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].short
home | work | temp | old - purpose of this address

# entry[].resource.snapshot.element[].requirements
Allows an appropriate address to be chosen from a list of many.

# entry[].resource.snapshot.element[].definition
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.

# entry[].resource.snapshot.element[].binding.description
The type of an address (physical / postal)

# entry[].resource.snapshot.element[].definition
A full text representation of the address.

# entry[].resource.snapshot.element[].short
Street name, number, direction & P.O. Box etc.

# entry[].resource.snapshot.element[].definition
This component contains the house number, apartment number, street name, street direction,  P.O. Box number, delivery hints, and similar address information.

# entry[].resource.snapshot.element[].requirements
home | work | temp | old - purpose of this address.

# entry[].resource.snapshot.element[].mapping[].map
XAD.1 + XAD.2 (note: XAD.1 and XAD.2 have different meanings for a company address than for a person address)

# entry[].resource.snapshot.element[].definition
The name of the city, town, village or other community or delivery center.

# entry[].resource.snapshot.element[].definition
The name of the administrative area (county).

# entry[].resource.snapshot.element[].definition
Sub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (i.e. US 2 letter state codes).

# entry[].resource.snapshot.element[].definition
A postal code designating a region defined by the postal service.

# entry[].resource.snapshot.element[].definition
Country - a nation as commonly understood or generally accepted.

# entry[].resource.snapshot.element[].requirements
Allows addresses to be placed in historical context.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The start of the period. The boundary is inclusive.

# entry[].resource.snapshot.element[].short
End time with inclusive boundary, if not ongoing

# entry[].resource.snapshot.element[].definition
The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.

# entry[].resource.snapshot.element[].meaningWhenMissing
If the end of the period is missing, it means that the period is ongoing

# entry[].resource.snapshot.element[].definition
This field contains a patient's most recent marital (civil) status.

# entry[].resource.snapshot.element[].binding.description
The domestic partnership status of a person.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
A reference to a code defined by a terminology system.

# entry[].resource.snapshot.element[].requirements
Allows for translations and alternate encodings within a code system.  Also supports communication of the same instance to systems requiring different encodings.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The identification of the code system that defines the meaning of the symbol in the code.

# entry[].resource.snapshot.element[].requirements
Need to be unambiguous about the source of the definition of the symbol.

# entry[].resource.snapshot.element[].definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

# entry[].resource.snapshot.element[].definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

# entry[].resource.snapshot.element[].requirements
Need to refer to a particular code in the system.

# entry[].resource.snapshot.element[].definition
A representation of the meaning of the code in the system, following the rules of the system.

# entry[].resource.snapshot.element[].requirements
Need to be able to carry a human-readable meaning of the code for readers that do not know  the system.

# entry[].resource.snapshot.element[].mapping[].map
C*E.2 - but note this is not well followed

# entry[].resource.snapshot.element[].short
If this coding was chosen directly by the user

# entry[].resource.snapshot.element[].definition
Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

# entry[].resource.snapshot.element[].requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

# entry[].resource.snapshot.element[].mapping[].map
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map;   fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [     fhir:source "true";     fhir:target dt:CDCoding.codingRationale\#O   ]

# entry[].resource.snapshot.element[].short
Plain text representation of the concept

# entry[].resource.snapshot.element[].definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

# entry[].resource.snapshot.element[].requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

# entry[].resource.snapshot.element[].mapping[].map
C*E.9. But note many systems use C*E.2 for this

# entry[].resource.snapshot.element[].short
Whether patient is part of a multiple birth

# entry[].resource.snapshot.element[].definition
Indicates whether the patient is part of a multiple or indicates the actual birth order.

# entry[].resource.snapshot.element[].requirements
For disambiguation of multiple-birth children, especially relevant where the care provider doesn't meet the patient, such as labs.

# entry[].resource.snapshot.element[].requirements
Many EHR systems have the capability to capture an image of the patient. Fits with newer social media usage too.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].short
Mime type of the content, with charset etc.

# entry[].resource.snapshot.element[].definition
Identifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate.

# entry[].resource.snapshot.element[].requirements
Processors of the data need to be able to know how to interpret the data.

# entry[].resource.snapshot.element[].binding.description
The mime type of an attachment. Any valid mime type is allowed.

# entry[].resource.snapshot.element[].mapping[].map
ED.2+ED.3/RP.2+RP.3. Note conversion may be needed if old style values are being used

# entry[].resource.snapshot.element[].definition
The human language of the content. The value can be any valid value according to BCP 47.

# entry[].resource.snapshot.element[].requirements
Users need to be able to choose between the languages in a set of attachments.

# entry[].resource.snapshot.element[].definition
The actual data of the attachment - a sequence of bytes. In XML, represented using base64.

# entry[].resource.snapshot.element[].requirements
The data needs to able to be transmitted inline.

# entry[].resource.snapshot.element[].definition
An alternative location where the data can be accessed.

# entry[].resource.snapshot.element[].requirements
The data needs to be transmitted by reference.

# entry[].resource.snapshot.element[].mapping[].map
RP.1+RP.2 - if they refer to a URL (see v2.6)

# entry[].resource.snapshot.element[].short
Number of bytes of content (if url provided)

# entry[].resource.snapshot.element[].definition
The number of bytes of data that make up this attachment.

# entry[].resource.snapshot.element[].requirements
Representing the size allows applications to determine whether they should fetch the content automatically in advance, or refuse to fetch it at all.

# entry[].resource.snapshot.element[].definition
The calculated hash of the data using SHA-1. Represented using base64.

# entry[].resource.snapshot.element[].requirements
Included so that applications can verify that the contents of a location have not changed and so that a signature of the content can implicitly sign the content of an image without having to include the data in the instance or reference the url in the signature.

# entry[].resource.snapshot.element[].definition
A label or set of text to display in place of the data.

# entry[].resource.snapshot.element[].requirements
Applications need a label to display to a human user in place of the actual data if the data cannot be rendered or perceived by the viewer.

# entry[].resource.snapshot.element[].definition
The date that the attachment was first created.

# entry[].resource.snapshot.element[].requirements
This is often tracked as an integrity issue for use of the attachment.

# entry[].resource.snapshot.element[].short
A contact party (e.g. guardian, partner, friend) for the patient

# entry[].resource.snapshot.element[].definition
A contact party (e.g. guardian, partner, friend) for the patient.

# entry[].resource.snapshot.element[].requirements
Need to track people you can contact about the patient.

# entry[].resource.snapshot.element[].constraint[].human
SHALL at least contain a contact's details or a reference to an organization

# entry[].resource.snapshot.element[].constraint[].xpath
f:name or f:telecom or f:address or f:organization

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The nature of the relationship between the patient and the contact person.

# entry[].resource.snapshot.element[].requirements
Used to determine which contact person is the most relevant to approach, depending on circumstances.

# entry[].resource.snapshot.element[].binding.description
The nature of the relationship between a patient and a contact person for that patient.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
A reference to a code defined by a terminology system.

# entry[].resource.snapshot.element[].requirements
Allows for translations and alternate encodings within a code system.  Also supports communication of the same instance to systems requiring different encodings.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The identification of the code system that defines the meaning of the symbol in the code.

# entry[].resource.snapshot.element[].requirements
Need to be unambiguous about the source of the definition of the symbol.

# entry[].resource.snapshot.element[].definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

# entry[].resource.snapshot.element[].definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

# entry[].resource.snapshot.element[].requirements
Need to refer to a particular code in the system.

# entry[].resource.snapshot.element[].definition
A representation of the meaning of the code in the system, following the rules of the system.

# entry[].resource.snapshot.element[].requirements
Need to be able to carry a human-readable meaning of the code for readers that do not know  the system.

# entry[].resource.snapshot.element[].mapping[].map
C*E.2 - but note this is not well followed

# entry[].resource.snapshot.element[].short
If this coding was chosen directly by the user

# entry[].resource.snapshot.element[].definition
Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

# entry[].resource.snapshot.element[].requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

# entry[].resource.snapshot.element[].mapping[].map
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map;   fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [     fhir:source "true";     fhir:target dt:CDCoding.codingRationale\#O   ]

# entry[].resource.snapshot.element[].short
Plain text representation of the concept

# entry[].resource.snapshot.element[].definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

# entry[].resource.snapshot.element[].requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

# entry[].resource.snapshot.element[].mapping[].map
C*E.9. But note many systems use C*E.2 for this

# entry[].resource.snapshot.element[].short
A name associated with the contact person

# entry[].resource.snapshot.element[].definition
A name associated with the contact person.

# entry[].resource.snapshot.element[].requirements
Contact persons need to be identified by name, but it is uncommon to need details about multiple other names for that contact person.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].short
usual | official | temp | nickname | anonymous | old | maiden

# entry[].resource.snapshot.element[].requirements
Allows the appropriate name for a particular context of use to be selected from among a set of names.

# entry[].resource.snapshot.element[].mapping[].map
XPN.7, but often indicated by which field contains the name

# entry[].resource.snapshot.element[].definition
The part of a name that links to the genealogy. In some cultures (e.g. Eritrea) the family name of a son is the first name of his father.

# entry[].resource.snapshot.element[].short
Given names (not always 'first'). Includes middle names

# entry[].resource.snapshot.element[].definition
Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the start of the name.

# entry[].resource.snapshot.element[].definition
Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the end of the name.

# entry[].resource.snapshot.element[].definition
Indicates the period of time when this name was valid for the named person.

# entry[].resource.snapshot.element[].requirements
Allows names to be placed in historical context.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The start of the period. The boundary is inclusive.

# entry[].resource.snapshot.element[].short
End time with inclusive boundary, if not ongoing

# entry[].resource.snapshot.element[].definition
The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.

# entry[].resource.snapshot.element[].meaningWhenMissing
If the end of the period is missing, it means that the period is ongoing

# entry[].resource.snapshot.element[].definition
A contact detail for the person, e.g. a telephone number or an email address.

# entry[].resource.snapshot.element[].requirements
People have (primary) ways to contact them in some way such as phone, email.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
Telecommunications form for contact point - what communications system is required to make use of the contact.

# entry[].resource.snapshot.element[].binding.description
Telecommunications form for contact point

# entry[].resource.snapshot.element[].definition
The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address).

# entry[].resource.snapshot.element[].requirements
Need to support legacy numbers that are not in a tightly controlled format.

# entry[].resource.snapshot.element[].short
home | work | temp | old | mobile - purpose of this contact point

# entry[].resource.snapshot.element[].definition
Identifies the purpose for the contact point.

# entry[].resource.snapshot.element[].requirements
Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose.

# entry[].resource.snapshot.element[].short
Specify preferred order of use (1 = highest)

# entry[].resource.snapshot.element[].definition
Specifies a preferred order in which to use a set of contacts. Contacts are ranked with lower values coming before higher values.

# entry[].resource.snapshot.element[].short
Time period when the contact point was/is in use

# entry[].resource.snapshot.element[].definition
Time period when the contact point was/is in use.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The start of the period. The boundary is inclusive.

# entry[].resource.snapshot.element[].short
End time with inclusive boundary, if not ongoing

# entry[].resource.snapshot.element[].definition
The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.

# entry[].resource.snapshot.element[].meaningWhenMissing
If the end of the period is missing, it means that the period is ongoing

# entry[].resource.snapshot.element[].requirements
Need to keep track where the contact person can be contacted per postal mail or visited.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].short
home | work | temp | old - purpose of this address

# entry[].resource.snapshot.element[].requirements
Allows an appropriate address to be chosen from a list of many.

# entry[].resource.snapshot.element[].definition
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.

# entry[].resource.snapshot.element[].binding.description
The type of an address (physical / postal)

# entry[].resource.snapshot.element[].definition
A full text representation of the address.

# entry[].resource.snapshot.element[].short
Street name, number, direction & P.O. Box etc.

# entry[].resource.snapshot.element[].definition
This component contains the house number, apartment number, street name, street direction,  P.O. Box number, delivery hints, and similar address information.

# entry[].resource.snapshot.element[].requirements
home | work | temp | old - purpose of this address.

# entry[].resource.snapshot.element[].mapping[].map
XAD.1 + XAD.2 (note: XAD.1 and XAD.2 have different meanings for a company address than for a person address)

# entry[].resource.snapshot.element[].definition
The name of the city, town, village or other community or delivery center.

# entry[].resource.snapshot.element[].definition
The name of the administrative area (county).

# entry[].resource.snapshot.element[].definition
Sub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (i.e. US 2 letter state codes).

# entry[].resource.snapshot.element[].definition
A postal code designating a region defined by the postal service.

# entry[].resource.snapshot.element[].definition
Country - a nation as commonly understood or generally accepted.

# entry[].resource.snapshot.element[].requirements
Allows addresses to be placed in historical context.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The start of the period. The boundary is inclusive.

# entry[].resource.snapshot.element[].short
End time with inclusive boundary, if not ongoing

# entry[].resource.snapshot.element[].definition
The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.

# entry[].resource.snapshot.element[].meaningWhenMissing
If the end of the period is missing, it means that the period is ongoing

# entry[].resource.snapshot.element[].definition
Administrative Gender - the gender that the contact person is considered to have for administration and record keeping purposes.

# entry[].resource.snapshot.element[].binding.description
The gender of a person used for administrative purposes.

# entry[].resource.snapshot.element[].short
Organization that is associated with the contact

# entry[].resource.snapshot.element[].definition
Organization on behalf of which the contact is acting or for which the contact is working.

# entry[].resource.snapshot.element[].requirements
For guardians or business related contacts, the organization is relevant.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].short
Relative, internal or absolute URL reference

# entry[].resource.snapshot.element[].definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

# entry[].resource.snapshot.element[].definition
Plain text narrative that identifies the resource in addition to the resource reference.

# entry[].resource.snapshot.element[].short
The period during which this contact person or organization is valid to be contacted relating to this patient

# entry[].resource.snapshot.element[].definition
The period during which this contact person or organization is valid to be contacted relating to this patient.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The start of the period. The boundary is inclusive.

# entry[].resource.snapshot.element[].short
End time with inclusive boundary, if not ongoing

# entry[].resource.snapshot.element[].definition
The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.

# entry[].resource.snapshot.element[].meaningWhenMissing
If the end of the period is missing, it means that the period is ongoing

# entry[].resource.snapshot.element[].short
This patient is known to be an animal (non-human)

# entry[].resource.snapshot.element[].requirements
Many clinical systems are extended to care for animal patients as well as human.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
Identifies the high level taxonomic categorization of the kind of animal.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
A reference to a code defined by a terminology system.

# entry[].resource.snapshot.element[].requirements
Allows for translations and alternate encodings within a code system.  Also supports communication of the same instance to systems requiring different encodings.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The identification of the code system that defines the meaning of the symbol in the code.

# entry[].resource.snapshot.element[].requirements
Need to be unambiguous about the source of the definition of the symbol.

# entry[].resource.snapshot.element[].definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

# entry[].resource.snapshot.element[].definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

# entry[].resource.snapshot.element[].requirements
Need to refer to a particular code in the system.

# entry[].resource.snapshot.element[].definition
A representation of the meaning of the code in the system, following the rules of the system.

# entry[].resource.snapshot.element[].requirements
Need to be able to carry a human-readable meaning of the code for readers that do not know  the system.

# entry[].resource.snapshot.element[].mapping[].map
C*E.2 - but note this is not well followed

# entry[].resource.snapshot.element[].short
If this coding was chosen directly by the user

# entry[].resource.snapshot.element[].definition
Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

# entry[].resource.snapshot.element[].requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

# entry[].resource.snapshot.element[].mapping[].map
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map;   fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [     fhir:source "true";     fhir:target dt:CDCoding.codingRationale\#O   ]

# entry[].resource.snapshot.element[].short
Plain text representation of the concept

# entry[].resource.snapshot.element[].definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

# entry[].resource.snapshot.element[].requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

# entry[].resource.snapshot.element[].mapping[].map
C*E.9. But note many systems use C*E.2 for this

# entry[].resource.snapshot.element[].definition
Identifies the detailed categorization of the kind of animal.

# entry[].resource.snapshot.element[].requirements
May need to know the specific kind within the species.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
A reference to a code defined by a terminology system.

# entry[].resource.snapshot.element[].requirements
Allows for translations and alternate encodings within a code system.  Also supports communication of the same instance to systems requiring different encodings.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The identification of the code system that defines the meaning of the symbol in the code.

# entry[].resource.snapshot.element[].requirements
Need to be unambiguous about the source of the definition of the symbol.

# entry[].resource.snapshot.element[].definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

# entry[].resource.snapshot.element[].definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

# entry[].resource.snapshot.element[].requirements
Need to refer to a particular code in the system.

# entry[].resource.snapshot.element[].definition
A representation of the meaning of the code in the system, following the rules of the system.

# entry[].resource.snapshot.element[].requirements
Need to be able to carry a human-readable meaning of the code for readers that do not know  the system.

# entry[].resource.snapshot.element[].mapping[].map
C*E.2 - but note this is not well followed

# entry[].resource.snapshot.element[].short
If this coding was chosen directly by the user

# entry[].resource.snapshot.element[].definition
Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

# entry[].resource.snapshot.element[].requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

# entry[].resource.snapshot.element[].mapping[].map
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map;   fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [     fhir:source "true";     fhir:target dt:CDCoding.codingRationale\#O   ]

# entry[].resource.snapshot.element[].short
Plain text representation of the concept

# entry[].resource.snapshot.element[].definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

# entry[].resource.snapshot.element[].requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

# entry[].resource.snapshot.element[].mapping[].map
C*E.9. But note many systems use C*E.2 for this

# entry[].resource.snapshot.element[].definition
Indicates the current state of the animal's reproductive organs.

# entry[].resource.snapshot.element[].requirements
Gender status can affect housing and animal behavior.

# entry[].resource.snapshot.element[].binding.description
The state of the animal's reproductive organs.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
A reference to a code defined by a terminology system.

# entry[].resource.snapshot.element[].requirements
Allows for translations and alternate encodings within a code system.  Also supports communication of the same instance to systems requiring different encodings.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The identification of the code system that defines the meaning of the symbol in the code.

# entry[].resource.snapshot.element[].requirements
Need to be unambiguous about the source of the definition of the symbol.

# entry[].resource.snapshot.element[].definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

# entry[].resource.snapshot.element[].definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

# entry[].resource.snapshot.element[].requirements
Need to refer to a particular code in the system.

# entry[].resource.snapshot.element[].definition
A representation of the meaning of the code in the system, following the rules of the system.

# entry[].resource.snapshot.element[].requirements
Need to be able to carry a human-readable meaning of the code for readers that do not know  the system.

# entry[].resource.snapshot.element[].mapping[].map
C*E.2 - but note this is not well followed

# entry[].resource.snapshot.element[].short
If this coding was chosen directly by the user

# entry[].resource.snapshot.element[].definition
Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

# entry[].resource.snapshot.element[].requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

# entry[].resource.snapshot.element[].mapping[].map
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map;   fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [     fhir:source "true";     fhir:target dt:CDCoding.codingRationale\#O   ]

# entry[].resource.snapshot.element[].short
Plain text representation of the concept

# entry[].resource.snapshot.element[].definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

# entry[].resource.snapshot.element[].requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

# entry[].resource.snapshot.element[].mapping[].map
C*E.9. But note many systems use C*E.2 for this

# entry[].resource.snapshot.element[].short
A list of Languages which may be used to communicate with the patient about his or her health

# entry[].resource.snapshot.element[].definition
Languages which may be used to communicate with the patient about his or her health.

# entry[].resource.snapshot.element[].requirements
If a patient does not speak the local language, interpreters may be required, so languages spoken and proficiency is an important things to keep track of both for patient and other persons of interest.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].short
The language which can be used to communicate with the patient about his or her health

# entry[].resource.snapshot.element[].definition
The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English.

# entry[].resource.snapshot.element[].requirements
Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
A reference to a code defined by a terminology system.

# entry[].resource.snapshot.element[].requirements
Allows for translations and alternate encodings within a code system.  Also supports communication of the same instance to systems requiring different encodings.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
The identification of the code system that defines the meaning of the symbol in the code.

# entry[].resource.snapshot.element[].requirements
Need to be unambiguous about the source of the definition of the symbol.

# entry[].resource.snapshot.element[].definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

# entry[].resource.snapshot.element[].definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

# entry[].resource.snapshot.element[].requirements
Need to refer to a particular code in the system.

# entry[].resource.snapshot.element[].definition
A representation of the meaning of the code in the system, following the rules of the system.

# entry[].resource.snapshot.element[].requirements
Need to be able to carry a human-readable meaning of the code for readers that do not know  the system.

# entry[].resource.snapshot.element[].mapping[].map
C*E.2 - but note this is not well followed

# entry[].resource.snapshot.element[].short
If this coding was chosen directly by the user

# entry[].resource.snapshot.element[].definition
Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

# entry[].resource.snapshot.element[].requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

# entry[].resource.snapshot.element[].mapping[].map
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map;   fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [     fhir:source "true";     fhir:target dt:CDCoding.codingRationale\#O   ]

# entry[].resource.snapshot.element[].short
Plain text representation of the concept

# entry[].resource.snapshot.element[].definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

# entry[].resource.snapshot.element[].requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

# entry[].resource.snapshot.element[].mapping[].map
C*E.9. But note many systems use C*E.2 for this

# entry[].resource.snapshot.element[].definition
Indicates whether or not the patient prefers this language (over other languages he masters up a certain level).

# entry[].resource.snapshot.element[].requirements
People that master multiple languages up to certain level may prefer one or more, i.e. feel more confident in communicating in a particular language making other languages sort of a fall back method.

# entry[].resource.snapshot.element[].short
Patient's nominated primary care provider

# entry[].resource.snapshot.element[].short
Organization that is the custodian of the patient record

# entry[].resource.snapshot.element[].definition
Organization that is the custodian of the patient record.

# entry[].resource.snapshot.element[].requirements
Need to know who recognizes this patient record, manages and updates it.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].short
Relative, internal or absolute URL reference

# entry[].resource.snapshot.element[].definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

# entry[].resource.snapshot.element[].definition
Plain text narrative that identifies the resource in addition to the resource reference.

# entry[].resource.snapshot.element[].short
Link to another patient resource that concerns the same actual person

# entry[].resource.snapshot.element[].definition
Link to another patient resource that concerns the same actual patient.

# entry[].resource.snapshot.element[].requirements
There are multiple usecases:   * Duplicate patient records due to the clerical errors associated with the difficulties of identifying humans consistently, and * Distribution of patient information across multiple servers.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].short
The other patient resource that the link refers to

# entry[].resource.snapshot.element[].definition
The other patient resource that the link refers to.

# entry[].resource.snapshot.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.snapshot.element[].short
Additional Content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].short
Relative, internal or absolute URL reference

# entry[].resource.snapshot.element[].definition
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

# entry[].resource.snapshot.element[].definition
Plain text narrative that identifies the resource in addition to the resource reference.

# entry[].resource.snapshot.element[].short
replace | refer | seealso - type of link

# entry[].resource.snapshot.element[].definition
The type of link between this patient resource and another patient resource.

# entry[].resource.snapshot.element[].binding.description
The type of link between this patient resource and another patient resource.

# entry[].resource.differential.element[].short
Information about an individual or animal receiving health care services

# entry[].resource.differential.element[].definition
Demographics and other administrative information about an individual or animal receiving care or other health-related services.

# entry[].resource.differential.element[].requirements
Patients are almost always assigned specific numerical identifiers.

# entry[].resource.differential.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.differential.element[].short
usual | official | temp | secondary (If known)

# entry[].resource.differential.element[].requirements
Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

# entry[].resource.differential.element[].binding.description
Identifies the purpose for this identifier, if known .

# entry[].resource.differential.element[].definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.

# entry[].resource.differential.element[].requirements
Allows users to make use of identifiers when the identifier system is not known.

# entry[].resource.differential.element[].binding.description
A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

# entry[].resource.differential.element[].definition
Establishes the namespace in which set of possible id values is unique.

# entry[].resource.differential.element[].requirements
There are many sequences of identifiers.  To perform matching, we need to know what sequence we're dealing with. The system identifies a particular sequence or set of unique identifiers.

# entry[].resource.differential.element[].definition
The portion of the identifier typically displayed to the user and which is unique within the context of the system.

# entry[].resource.differential.element[].mapping[].map
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)

# entry[].resource.differential.element[].short
Time period when id is/was valid for use

# entry[].resource.differential.element[].definition
Time period during which identifier is/was valid for use.

# entry[].resource.differential.element[].mapping[].map
Role.effectiveTime or implied by context

# entry[].resource.differential.element[].short
Organization that issued id (may be just text)

# entry[].resource.differential.element[].definition
Organization that issued/manages the identifier.

# entry[].resource.differential.element[].mapping[].map
II.assigningAuthorityName but note that this is an improper use by the definition of the field.  Also Role.scoper

# entry[].resource.differential.element[].requirements
Patients are almost always assigned specific numerical identifiers.

# entry[].resource.differential.element[].definition
unique id for the element within a resource (for internal references).

# entry[].resource.differential.element[].short
usual | official | temp | secondary (If known)

# entry[].resource.differential.element[].requirements
Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

# entry[].resource.differential.element[].binding.description
Identifies the purpose for this identifier, if known .

# entry[].resource.differential.element[].definition
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.

# entry[].resource.differential.element[].requirements
Allows users to make use of identifiers when the identifier system is not known.

# entry[].resource.differential.element[].binding.description
A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

# entry[].resource.differential.element[].definition
Establishes the namespace in which set of possible id values is unique.

# entry[].resource.differential.element[].requirements
There are many sequences of identifiers.  To perform matching, we need to know what sequence we're dealing with. The system identifies a particular sequence or set of unique identifiers.

# entry[].resource.differential.element[].definition
The portion of the identifier typically displayed to the user and which is unique within the context of the system.

# entry[].resource.differential.element[].mapping[].map
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)

# entry[].resource.differential.element[].short
Time period when id is/was valid for use

# entry[].resource.differential.element[].definition
Time period during which identifier is/was valid for use.

# entry[].resource.differential.element[].mapping[].map
Role.effectiveTime or implied by context

# entry[].resource.differential.element[].short
Organization that issued id (may be just text)

# entry[].resource.differential.element[].definition
Organization that issued/manages the identifier.

# entry[].resource.differential.element[].mapping[].map
II.assigningAuthorityName but note that this is an improper use by the definition of the field.  Also Role.scoper

# entry[].resource.differential.element[].requirements
Need to be able to track the patient by multiple names. Examples are your official name and a partner name.

# entry[].resource.differential.element[].definition
Administrative Gender - the gender that the patient is considered to have for administration and record keeping purposes.

# entry[].resource.differential.element[].requirements
Needed for identification of the individual, in combination with (at least) name and birth date. Gender of individual drives many clinical processes.

# entry[].resource.differential.element[].binding.description
The gender of a person used for administrative purposes.

# entry[].resource.differential.element[].requirements
Age of the individual drives many clinical processes.

# entry[].resource.differential.element[].definition
A URI that identifies a participation agreement/policy       to which the patient has agreed

# entry[].resource.differential.element[].definition
A URI that identifies a participation agreement/policy       to which the patient has agreed

# entry[].resource.description
additional gender values for the gernder field

# entry[].resource.snapshot.element[].definition
Source of the definition for the extension code - a logical name or a URL.

# entry[].resource.snapshot.element[].comment
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

# entry[].resource.snapshot.element[].definition
Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).

# entry[].resource.description
additional gender values for the gernder field

# entry[].resource.snapshot.element[].definition
Source of the definition for the extension code - a logical name or a URL.

# entry[].resource.snapshot.element[].comment
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

# entry[].resource.snapshot.element[].definition
Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).

# entry[].resource.description
additional gender values for the gernder field

# entry[].resource.snapshot.element[].definition
Source of the definition for the extension code - a logical name or a URL.

# entry[].resource.snapshot.element[].comment
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

# entry[].resource.snapshot.element[].definition
Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list).

# entry[].resource.text.div
to do

# entry[].resource.extension[].valueMarkdown
#### Complete Summary of the Mandatory Requirements

1.  One code in `Observation.code` which must have
    -   a fixed `Observation.code.coding.system`=**'http ://loinc.org'**
    -   a fixed  `Observation.code.coding.code`= **85354-9'**
    -   Other additional Codings are allowed in `Observation.code`- e.g. more specific LOINC
        Codes, SNOMED CT concepts, system specific codes. All codes
        SHALL have an system value
2.  One  `Observation.component.code`  which must have
    -   a fixed `Observation.component.code.coding.system`=**'http://loinc.org'**
    -   fixed  `Observation.component.code.coding.code`= **'8480-6'**
    -   Other additional Codings are allowed in `Observation.code`- e.g. more specific LOINC
        Codes, SNOMED CT concepts, system specific codes. All codes
        SHALL have an system value
3.  One  `Observation.component.code` which must have 
    -   a fixed `Observation.component.code.coding.system`=**'http://loinc.org'**
    -   fixed  `Observation.component.code.coding.code`= **'8462-4'**
    -   Other additional Codings are allowed in `Observation.code`- e.g. more specific LOINC
        Codes, SNOMED CT concepts, system specific codes. All codes
        SHALL have an system value
1. Either one Observation.valueQuantity or, if there is no value, one code in Observation.DataAbsentReason
   - Each Observation.valueQuantity must have:
     - One numeric value in Observation.valueQuantity.value
     - a fixed Observation.valueQuantity.system="http://unitsofmeasure.org"
     - a UCUM unit code in Observation.valueQuantity.code = **'mm[Hg]'**

# entry[].resource.publisher
Health Level Seven International (Orders and Observations Workgroup)

# entry[].resource.snapshot.element[].definition
This profile defines  how to represent Blood Pressure observations in FHIR using a standard LOINC code and UCUM units of measure.  This is a grouping structure. It has no value in Observation.valueQuantity but contains at least one component (systolic and/or diastolic).

# entry[].resource.snapshot.element[].comment
Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc.  Other resources are used to provide context for observations such as laboratory reports, etc.

# entry[].resource.snapshot.element[].constraint[].human
If the resource is contained in another resource, it SHALL NOT contain nested Resources

# entry[].resource.snapshot.element[].constraint[].human
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated

# entry[].resource.snapshot.element[].constraint[].human
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

# entry[].resource.snapshot.element[].constraint[].extension[].valueMarkdown
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.

# entry[].resource.snapshot.element[].constraint[].human
A resource should have narrative for robust management

# entry[].resource.snapshot.element[].constraint[].human
If a resource is contained in another resource, it SHALL NOT have a security label

# entry[].resource.snapshot.element[].constraint[].human
If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present

# entry[].resource.snapshot.element[].constraint[].human
dataAbsentReason SHALL only be present if Observation.value[x] is not present

# entry[].resource.snapshot.element[].constraint[].human
If there is no component or hasMember element then either a value[x] or a data absent reason must be present.

# entry[].resource.snapshot.element[].definition
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

# entry[].resource.snapshot.element[].comment
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].short
A set of rules under which this content was created

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].isModifierReason
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

# entry[].resource.snapshot.element[].definition
The base language in which the resource is written.

# entry[].resource.snapshot.element[].comment
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).

# entry[].resource.snapshot.element[].short
Text summary of the resource, for human interpretation

# entry[].resource.snapshot.element[].definition
A human-readable narrative that contains a summary of the resource and can 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.

# entry[].resource.snapshot.element[].comment
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 information is added later.

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].comment
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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

# entry[].resource.snapshot.element[].short
Additional content defined by implementations

# entry[].resource.snapshot.element[].definition
May be used to represent additional information that is not part of the basic definition of the resource. 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.

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].definition
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 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 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].requirements
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](extensibility.html#modifierExtension).

# entry[].resource.snapshot.element[].isModifierReason
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them

# entry[].resource.snapshot.element[].definition
A unique identifier assigned to this observation.

# entry[].resource.snapshot.element[].requirements
Allows observations to be distinguished and referenced.

# entry[].resource.snapshot.element[].mapping[].map
OBX.21  For OBX segments from systems without OBX-21 support a combination of ORC/OBR and OBX must be negotiated between trading partners to uniquely identify the OBX segment. Depending on how V2 has been implemented each of these may be an option: 1) OBR-3 + OBX-3 + OBX-4 or 2) OBR-3 + OBR-4 + OBX-3 + OBX-4 or 2) some other way to uniquely ID the OBR/ORC + OBX-3 + OBX-4.

# entry[].resource.snapshot.element[].definition
A plan, proposal or order that is fulfilled in whole or in part by this event.  For example, a MedicationRequest may require a patient to have laboratory test performed before  it is dispensed.

# entry[].resource.snapshot.element[].requirements
Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon.

# entry[].resource.snapshot.element[].definition
A larger event of which this particular Observation is a component or step.  For example,  an observation as part of a procedure.

# entry[].resource.snapshot.element[].comment
To link an Observation to an Encounter use `encounter`.  See the  [Notes](observation.html#obsgrouping) below for guidance on referencing another Observation.

# entry[].resource.snapshot.element[].short
registered | preliminary | final | amended +

# entry[].resource.snapshot.element[].comment
This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

# entry[].resource.snapshot.element[].requirements
Need to track the status of individual results. Some results are finalized before the whole report is finalized.

# entry[].resource.snapshot.element[].isModifierReason
This element is labeled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid

# entry[].resource.snapshot.element[].mapping[].map
status  Amended & Final are differentiated by whether it is the subject of a ControlAct event with a type of "revise"

# entry[].resource.snapshot.element[].definition
A code that classifies the general type of observation being made.

# entry[].resource.snapshot.element[].comment
In addition to the required category valueset, this element allows various categorization schemes based on the owner’s definition of the category and effectively multiple categories can be used at once.  The level of granularity is defined by the category concepts in the value set.

# entry[].resource.snapshot.element[].requirements
Used for filtering what observations are retrieved and displayed.

# entry[].resource.snapshot.element[].binding.description
Codes for high level observation categories.

# entry[].resource.snapshot.element[].definition
A code that classifies the general type of observation being made.

# entry[].resource.snapshot.element[].comment
In addition to the required category valueset, this element allows various categorization schemes based on the owner’s definition of the category and effectively multiple categories can be used at once.  The level of granularity is defined by the category concepts in the value set.

# entry[].resource.snapshot.element[].requirements
Used for filtering what observations are retrieved and displayed.

# entry[].resource.snapshot.element[].binding.description
Codes for high level observation categories.

# entry[].resource.snapshot.element[].definition
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

# entry[].resource.snapshot.element[].slicing.description
Extensions are always sliced by (at least) url

# entry[].resource.snapshot.element[].short
Additional content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].definition
A reference to a code defined by a terminology system.

# entry[].resource.snapshot.element[].comment
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.  Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

# entry[].resource.snapshot.element[].requirements
Allows for alternative encodings within a code system, and translations to other code systems.

# entry[].resource.snapshot.element[].definition
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

# entry[].resource.snapshot.element[].slicing.description
Extensions are always sliced by (at least) url

# entry[].resource.snapshot.element[].short
Additional content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].definition
The identification of the code system that defines the meaning of the symbol in the code.

# entry[].resource.snapshot.element[].comment
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...).  OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

# entry[].resource.snapshot.element[].requirements
Need to be unambiguous about the source of the definition of the symbol.

# entry[].resource.snapshot.element[].definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

# entry[].resource.snapshot.element[].comment
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

# entry[].resource.snapshot.element[].definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

# entry[].resource.snapshot.element[].requirements
Need to refer to a particular code in the system.

# entry[].resource.snapshot.element[].definition
A representation of the meaning of the code in the system, following the rules of the system.

# entry[].resource.snapshot.element[].requirements
Need to be able to carry a human-readable meaning of the code for readers that do not know  the system.

# entry[].resource.snapshot.element[].mapping[].map
C*E.2 - but note this is not well followed

# entry[].resource.snapshot.element[].short
If this coding was chosen directly by the user

# entry[].resource.snapshot.element[].definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).

# entry[].resource.snapshot.element[].comment
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

# entry[].resource.snapshot.element[].requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

# entry[].resource.snapshot.element[].mapping[].map
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map;   fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [     fhir:source "true";     fhir:target dt:CDCoding.codingRationale\#O   ]

# entry[].resource.snapshot.element[].short
Plain text representation of the concept

# entry[].resource.snapshot.element[].definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

# entry[].resource.snapshot.element[].comment
Very often the text is the same as a displayName of one of the codings.

# entry[].resource.snapshot.element[].requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

# entry[].resource.snapshot.element[].mapping[].map
C*E.9. But note many systems use C*E.2 for this

# entry[].resource.snapshot.element[].comment
additional codes that translate or map to this code are allowed.  For example a more granular LOINC code or code that is used locally in a system.

# entry[].resource.snapshot.element[].requirements
5. SHALL contain exactly one [1..1] code, where the @code SHOULD be selected from ValueSet HITSP Vital Sign Result Type 2.16.840.1.113883.3.88.12.80.62 DYNAMIC (CONF:7301).

# entry[].resource.snapshot.element[].binding.description
This identifies the vital sign result type.

# entry[].resource.snapshot.element[].mapping[].map
< 363787002 |Observable entity| OR < 386053000 |Evaluation procedure|

# entry[].resource.snapshot.element[].definition
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

# entry[].resource.snapshot.element[].slicing.description
Extensions are always sliced by (at least) url

# entry[].resource.snapshot.element[].short
Additional content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].definition
A reference to a code defined by a terminology system.

# entry[].resource.snapshot.element[].comment
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.  Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

# entry[].resource.snapshot.element[].requirements
Allows for alternative encodings within a code system, and translations to other code systems.

# entry[].resource.snapshot.element[].definition
A reference to a code defined by a terminology system.

# entry[].resource.snapshot.element[].comment
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.  Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

# entry[].resource.snapshot.element[].requirements
Allows for alternative encodings within a code system, and translations to other code systems.

# entry[].resource.snapshot.element[].definition
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

# entry[].resource.snapshot.element[].slicing.description
Extensions are always sliced by (at least) url

# entry[].resource.snapshot.element[].short
Additional content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].definition
The identification of the code system that defines the meaning of the symbol in the code.

# entry[].resource.snapshot.element[].comment
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...).  OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

# entry[].resource.snapshot.element[].requirements
Need to be unambiguous about the source of the definition of the symbol.

# entry[].resource.snapshot.element[].definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

# entry[].resource.snapshot.element[].comment
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

# entry[].resource.snapshot.element[].definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

# entry[].resource.snapshot.element[].requirements
Need to refer to a particular code in the system.

# entry[].resource.snapshot.element[].definition
A representation of the meaning of the code in the system, following the rules of the system.

# entry[].resource.snapshot.element[].requirements
Need to be able to carry a human-readable meaning of the code for readers that do not know  the system.

# entry[].resource.snapshot.element[].mapping[].map
C*E.2 - but note this is not well followed

# entry[].resource.snapshot.element[].short
If this coding was chosen directly by the user

# entry[].resource.snapshot.element[].definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).

# entry[].resource.snapshot.element[].comment
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

# entry[].resource.snapshot.element[].requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

# entry[].resource.snapshot.element[].mapping[].map
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map;   fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [     fhir:source "true";     fhir:target dt:CDCoding.codingRationale\#O   ]

# entry[].resource.snapshot.element[].short
Plain text representation of the concept

# entry[].resource.snapshot.element[].definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

# entry[].resource.snapshot.element[].comment
Very often the text is the same as a displayName of one of the codings.

# entry[].resource.snapshot.element[].requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

# entry[].resource.snapshot.element[].mapping[].map
C*E.9. But note many systems use C*E.2 for this

# entry[].resource.snapshot.element[].short
Who and/or what the observation is about

# entry[].resource.snapshot.element[].definition
The patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the `focus` element or the `code` itself specifies the actual focus of the observation.

# entry[].resource.snapshot.element[].comment
One would expect this element to be a cardinality of 1..1. The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

# entry[].resource.snapshot.element[].requirements
Observations have no value if you don't know who or what they're about.

# entry[].resource.snapshot.element[].short
What the observation is about, when it is not about the subject of record

# entry[].resource.snapshot.element[].definition
The actual focus of an observation when it is not the patient of record representing something or someone associated with the patient such as a spouse, parent, fetus, or donor. For example, fetus observations in a mother's record.  The focus of an observation could also be an existing condition,  an intervention, the subject's diet,  another observation of the subject,  or a body structure such as tumor or implanted device.   An example use case would be using the Observation resource to capture whether the mother is trained to change her child's tracheostomy tube. In this example, the child is the patient of record and the mother is the focus.

# entry[].resource.snapshot.element[].comment
Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., "Blood Glucose") and does not need to be represented separately using this element.  Use `specimen` if a reference to a specimen is required.  If a code is required instead of a resource use either  `bodysite` for bodysites or the standard extension [focusCode](extension-observation-focuscode.html).

# entry[].resource.snapshot.element[].short
Healthcare event during which this observation is made

# entry[].resource.snapshot.element[].definition
The healthcare event  (e.g. a patient and healthcare provider interaction) during which this observation is made.

# entry[].resource.snapshot.element[].comment
This will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission laboratory tests).

# entry[].resource.snapshot.element[].requirements
For some observations it may be important to know the link between an observation and a particular encounter.

# entry[].resource.snapshot.element[].comment
At least a date should be present unless this observation is a historical report.  For recording imprecise or "fuzzy" times (For example, a blood glucose measurement taken "after breakfast") use the [Timing](datatypes.html#timing) datatype which allow the measurement to be tied to regular life events.

# entry[].resource.snapshot.element[].requirements
Knowing when an observation was deemed true is important to its relevance as well as determining trends.

# entry[].resource.snapshot.element[].constraint[].human
if Observation.effective[x] is dateTime and has a value then that value shall be precise to the day

# entry[].resource.snapshot.element[].constraint[].expression
($this as dateTime).toString().length() >= 8

# entry[].resource.snapshot.element[].mapping[].map
OBX-14, and/or OBX-19 after v2.4  (depends on who observation made)

# entry[].resource.snapshot.element[].short
Date/Time this version was made available

# entry[].resource.snapshot.element[].definition
The date and time this version of the observation was made available to providers, typically after the results have been reviewed and verified.

# entry[].resource.snapshot.element[].comment
For Observations that don’t require review and verification, it may be the same as the [`lastUpdated` ](resource-definitions.html#Meta.lastUpdated) time of the resource itself.  For Observations that do require review and verification for certain updates, it might not be the same as the `lastUpdated` time of the resource itself due to a non-clinically significant update that doesn’t require the new version to be reviewed and verified again.

# entry[].resource.snapshot.element[].mapping[].map
OBR.22 (or MSH.7), or perhaps OBX-19 (depends on who observation made)

# entry[].resource.snapshot.element[].definition
Who was responsible for asserting the observed value as "true".

# entry[].resource.snapshot.element[].requirements
May give a degree of confidence in the observation and also indicates where follow-up questions should be directed.

# entry[].resource.snapshot.element[].short
Vital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.

# entry[].resource.snapshot.element[].definition
Vital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.

# entry[].resource.snapshot.element[].comment
An observation may have; 1)  a single value here, 2)  both a value and a set of related or component values,  or 3)  only a set of related or component values. If a value is present, the datatype for this element should be determined by Observation.code.  A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value.  For additional guidance, see the [Notes section](observation.html#notes) below.

# entry[].resource.snapshot.element[].requirements
9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305).

# entry[].resource.snapshot.element[].definition
Provides a reason why the expected value in the element Observation.value[x] is missing.

# entry[].resource.snapshot.element[].comment
Null or exceptional values can be represented two ways in FHIR Observations.  One way is to simply include them in the value set and represent the exceptions in the value.  For example, measurement values for a serology test could be  "detected", "not detected", "inconclusive", or  "specimen unsatisfactory".   

The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values.  For example, the dataAbsentReason code "error" could be used when the measurement was not completed. Note that an observation may only be reported if there are values to report. For example differential cell counts values may be reported only when > 0.  Because of these options, use-case agreements are required to interpret general observations for null or exceptional values.

# entry[].resource.snapshot.element[].requirements
For many results it is necessary to handle exceptional values in measurements.

# entry[].resource.snapshot.element[].binding.description
Codes specifying why the result (`Observation.value[x]`) is missing.

# entry[].resource.snapshot.element[].definition
A categorical assessment of an observation value.  For example, high, low, normal.

# entry[].resource.snapshot.element[].comment
Historically used for laboratory results (known as 'abnormal flag' ),  its use extends to other use cases where coded interpretations  are relevant.  Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result.

# entry[].resource.snapshot.element[].requirements
For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result.

# entry[].resource.snapshot.element[].definition
Comments about the observation or the results.

# entry[].resource.snapshot.element[].comment
May include general statements about the observation, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation.

# entry[].resource.snapshot.element[].requirements
Need to be able to provide free text additional information.

# entry[].resource.snapshot.element[].mapping[].map
NTE.3 (partner NTE to OBX, or sometimes another (child?) OBX)

# entry[].resource.snapshot.element[].definition
Indicates the site on the subject's body where the observation was made (i.e. the target site).

# entry[].resource.snapshot.element[].comment
Only used if not implicit in code found in Observation.code.  In many systems, this may be represented as a related observation instead of an inline component.   

If the use case requires BodySite to be handled as a separate resource (e.g. to identify and track separately) then use the standard extension[ bodySite](extension-bodysite.html).

# entry[].resource.snapshot.element[].binding.description
Codes describing anatomical locations. May include laterality.

# entry[].resource.snapshot.element[].definition
Indicates the mechanism used to perform the observation.

# entry[].resource.snapshot.element[].comment
Only used if not implicit in code for Observation.code.

# entry[].resource.snapshot.element[].requirements
In some cases, method can impact results and is thus used for determining whether results can be compared or determining significance of results.

# entry[].resource.snapshot.element[].definition
The specimen that was used when this observation was made.

# entry[].resource.snapshot.element[].comment
Should only be used if not implicit in code found in `Observation.code`.  Observations are not made on specimens themselves; they are made on a subject, but in many cases by the means of a specimen. Note that although specimens are often involved, they are not always tracked and reported explicitly. Also note that observation resources may be used in contexts that track the specimen explicitly (e.g. Diagnostic Report).

# entry[].resource.snapshot.element[].definition
The device used to generate the observation data.

# entry[].resource.snapshot.element[].comment
Note that this is not meant to represent a device involved in the transmission of the result, e.g., a gateway.  Such devices may be documented using the Provenance resource where relevant.

# entry[].resource.snapshot.element[].definition
Guidance on how to interpret the value by comparison to a normal or recommended range.  Multiple reference ranges are interpreted as an "OR".   In other words, to represent two distinct target populations, two `referenceRange` elements would be used.

# entry[].resource.snapshot.element[].comment
Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.

# entry[].resource.snapshot.element[].requirements
Knowing what values are considered "normal" can help evaluate the significance of a particular result. Need to be able to provide multiple reference ranges for different contexts.

# entry[].resource.snapshot.element[].constraint[].human
All FHIR elements must have a @value or children

# entry[].resource.snapshot.element[].constraint[].expression
hasValue() or (children().count() > id.count())

# entry[].resource.snapshot.element[].constraint[].human
Must have at least a low or a high or text

# entry[].resource.snapshot.element[].constraint[].expression
low.exists() or high.exists() or text.exists()

# entry[].resource.snapshot.element[].definition
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

# entry[].resource.snapshot.element[].short
Additional content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].short
Extensions that cannot be ignored even if unrecognized

# entry[].resource.snapshot.element[].definition
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).

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].requirements
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](extensibility.html#modifierExtension).

# entry[].resource.snapshot.element[].isModifierReason
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them

# entry[].resource.snapshot.element[].definition
The value of the low bound of the reference range.  The low bound of the reference range endpoint is inclusive of the value (e.g.  reference range is >=5 - <=9). If the low bound is omitted,  it is assumed to be meaningless (e.g. reference range is <=2.3).

# entry[].resource.snapshot.element[].definition
The value of the high bound of the reference range.  The high bound of the reference range endpoint is inclusive of the value (e.g.  reference range is >=5 - <=9). If the high bound is omitted,  it is assumed to be meaningless (e.g. reference range is >= 2.3).

# entry[].resource.snapshot.element[].definition
Codes to indicate the what part of the targeted reference population it applies to. For example, the normal or therapeutic range.

# entry[].resource.snapshot.element[].comment
This SHOULD be populated if there is more than one range.  If this element is not present then the normal range is assumed.

# entry[].resource.snapshot.element[].requirements
Need to be able to say what kind of reference range this is - normal, recommended, therapeutic, etc.,  - for proper interpretation.

# entry[].resource.snapshot.element[].binding.description
Code for the meaning of a reference range.

# entry[].resource.snapshot.element[].mapping[].map
< 260245000 |Findings values| OR  
< 365860008 |General clinical state finding| 
OR 
< 250171008 |Clinical history or observation findings| OR  
< 415229000 |Racial group| OR 
< 365400002 |Finding of puberty stage| OR
< 443938003 |Procedure carried out on subject|

# entry[].resource.snapshot.element[].definition
Codes to indicate the target population this reference range applies to.  For example, a reference range may be based on the normal population or a particular sex or race.  Multiple `appliesTo`  are interpreted as an "AND" of the target populations.  For example, to represent a target population of African American females, both a code of female and a code for African American would be used.

# entry[].resource.snapshot.element[].comment
This SHOULD be populated if there is more than one range.  If this element is not present then the normal population is assumed.

# entry[].resource.snapshot.element[].requirements
Need to be able to identify the target population for proper interpretation.

# entry[].resource.snapshot.element[].binding.description
Codes identifying the population the reference range applies to.

# entry[].resource.snapshot.element[].mapping[].map
< 260245000 |Findings values| OR  
< 365860008 |General clinical state finding| 
OR 
< 250171008 |Clinical history or observation findings| OR  
< 415229000 |Racial group| OR 
< 365400002 |Finding of puberty stage| OR
< 443938003 |Procedure carried out on subject|

# entry[].resource.snapshot.element[].definition
The age at which this reference range is applicable. This is a neonatal age (e.g. number of weeks at term) if the meaning says so.

# entry[].resource.snapshot.element[].short
Text based reference range in an observation

# entry[].resource.snapshot.element[].definition
Text based reference range in an observation which may be used when a quantitative range is not appropriate for an observation.  An example would be a reference value of "Negative" or a list or table of "normals".

# entry[].resource.snapshot.element[].short
Used when reporting vital signs panel components

# entry[].resource.snapshot.element[].definition
Used when reporting vital signs panel components.

# entry[].resource.snapshot.element[].comment
When using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases.  For a discussion on the ways Observations can assembled in groups together, see [Notes](observation.html#obsgrouping) below.  Note that a system may calculate results from [QuestionnaireResponse](questionnaireresponse.html)  into a final score and represent the score as an Observation.

# entry[].resource.snapshot.element[].mapping[].map
Relationships established by OBX-4 usage

# entry[].resource.snapshot.element[].short
Related measurements the observation is made from

# entry[].resource.snapshot.element[].definition
The target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image.

# entry[].resource.snapshot.element[].comment
All the reference choices that are listed in this element can represent clinical observations and other measurements that may be the source for a derived value.  The most common reference will be another Observation.  For a discussion on the ways Observations can assembled in groups together, see [Notes](observation.html#obsgrouping) below.

# entry[].resource.snapshot.element[].mapping[].map
Relationships established by OBX-4 usage

# entry[].resource.snapshot.element[].short
Used when reporting systolic and diastolic blood pressure.

# entry[].resource.snapshot.element[].definition
Used when reporting systolic and diastolic blood pressure.

# entry[].resource.snapshot.element[].comment
For a discussion on the ways Observations can be assembled in groups together see [Notes](observation.html#notes) below.

# entry[].resource.snapshot.element[].requirements
Component observations share the same attributes in the Observation resource as the primary observation and are always treated a part of a single observation (they are not separable).   However, the reference range for the primary observation value is not inherited by the component values and is required when appropriate for each component observation.

# entry[].resource.snapshot.element[].constraint[].human
All FHIR elements must have a @value or children

# entry[].resource.snapshot.element[].constraint[].expression
hasValue() or (children().count() > id.count())

# entry[].resource.snapshot.element[].constraint[].human
If there is no a value a data absent reason must be present

# entry[].resource.snapshot.element[].definition
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

# entry[].resource.snapshot.element[].short
Additional content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].short
Extensions that cannot be ignored even if unrecognized

# entry[].resource.snapshot.element[].definition
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).

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].requirements
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](extensibility.html#modifierExtension).

# entry[].resource.snapshot.element[].isModifierReason
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them

# entry[].resource.snapshot.element[].short
Type of component observation (code / type)

# entry[].resource.snapshot.element[].definition
Describes what was observed. Sometimes this is called the observation "code".

# entry[].resource.snapshot.element[].comment
*All* code-value and  component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation.

# entry[].resource.snapshot.element[].requirements
Knowing what kind of observation is being made is essential to understanding the observation.

# entry[].resource.snapshot.element[].binding.description
This identifies the vital sign result type.

# entry[].resource.snapshot.element[].mapping[].map
< 363787002 |Observable entity| OR 
< 386053000 |Evaluation procedure|

# entry[].resource.snapshot.element[].comment
Used when observation has a set of component observations. An observation may have both a value (e.g. an  Apgar score)  and component observations (the observations from which the Apgar score was derived). If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value.  For additional guidance, see the [Notes section](observation.html#notes) below.

# entry[].resource.snapshot.element[].requirements
9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305).

# entry[].resource.snapshot.element[].binding.description
Common UCUM units for recording Vital Signs.

# entry[].resource.snapshot.element[].definition
Provides a reason why the expected value in the element Observation.component.value[x] is missing.

# entry[].resource.snapshot.element[].comment
"Null" or exceptional values can be represented two ways in FHIR Observations.  One way is to simply include them in the value set and represent the exceptions in the value.  For example, measurement values for a serology test could be  "detected", "not detected", "inconclusive", or  "test not done". 

The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values.  For example, the dataAbsentReason code "error" could be used when the measurement was not completed.  Because of these options, use-case agreements are required to interpret general observations for exceptional values.

# entry[].resource.snapshot.element[].requirements
For many results it is necessary to handle exceptional values in measurements.

# entry[].resource.snapshot.element[].binding.description
Codes specifying why the result (`Observation.value[x]`) is missing.

# entry[].resource.snapshot.element[].definition
A categorical assessment of an observation value.  For example, high, low, normal.

# entry[].resource.snapshot.element[].comment
Historically used for laboratory results (known as 'abnormal flag' ),  its use extends to other use cases where coded interpretations  are relevant.  Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result.

# entry[].resource.snapshot.element[].requirements
For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result.

# entry[].resource.snapshot.element[].short
Provides guide for interpretation of component result

# entry[].resource.snapshot.element[].definition
Guidance on how to interpret the value by comparison to a normal or recommended range.

# entry[].resource.snapshot.element[].comment
Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.

# entry[].resource.snapshot.element[].requirements
Knowing what values are considered "normal" can help evaluate the significance of a particular result. Need to be able to provide multiple reference ranges for different contexts.

# entry[].resource.snapshot.element[].short
Used when reporting systolic and diastolic blood pressure.

# entry[].resource.snapshot.element[].definition
Used when reporting systolic and diastolic blood pressure.

# entry[].resource.snapshot.element[].comment
For a discussion on the ways Observations can be assembled in groups together see [Notes](observation.html#notes) below.

# entry[].resource.snapshot.element[].requirements
Component observations share the same attributes in the Observation resource as the primary observation and are always treated a part of a single observation (they are not separable).   However, the reference range for the primary observation value is not inherited by the component values and is required when appropriate for each component observation.

# entry[].resource.snapshot.element[].constraint[].human
All FHIR elements must have a @value or children

# entry[].resource.snapshot.element[].constraint[].expression
hasValue() or (children().count() > id.count())

# entry[].resource.snapshot.element[].constraint[].human
If there is no a value a data absent reason must be present

# entry[].resource.snapshot.element[].definition
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

# entry[].resource.snapshot.element[].short
Additional content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].short
Extensions that cannot be ignored even if unrecognized

# entry[].resource.snapshot.element[].definition
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).

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].requirements
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](extensibility.html#modifierExtension).

# entry[].resource.snapshot.element[].isModifierReason
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them

# entry[].resource.snapshot.element[].short
Type of component observation (code / type)

# entry[].resource.snapshot.element[].definition
Describes what was observed. Sometimes this is called the observation "code".

# entry[].resource.snapshot.element[].comment
additional codes that translate or map to this code are allowed.  For example a more granular LOINC code or code that is used locally in a system.

# entry[].resource.snapshot.element[].requirements
Knowing what kind of observation is being made is essential to understanding the observation.

# entry[].resource.snapshot.element[].binding.description
This identifies the vital sign result type.

# entry[].resource.snapshot.element[].mapping[].map
< 363787002 |Observable entity| OR 
< 386053000 |Evaluation procedure|

# entry[].resource.snapshot.element[].definition
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

# entry[].resource.snapshot.element[].slicing.description
Extensions are always sliced by (at least) url

# entry[].resource.snapshot.element[].short
Additional content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].comment
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.  Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

# entry[].resource.snapshot.element[].requirements
Allows for alternative encodings within a code system, and translations to other code systems.

# entry[].resource.snapshot.element[].comment
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.  Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

# entry[].resource.snapshot.element[].requirements
Allows for alternative encodings within a code system, and translations to other code systems.

# entry[].resource.snapshot.element[].definition
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

# entry[].resource.snapshot.element[].slicing.description
Extensions are always sliced by (at least) url

# entry[].resource.snapshot.element[].short
Additional content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].definition
The identification of the code system that defines the meaning of the symbol in the code.

# entry[].resource.snapshot.element[].comment
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...).  OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

# entry[].resource.snapshot.element[].requirements
Need to be unambiguous about the source of the definition of the symbol.

# entry[].resource.snapshot.element[].definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

# entry[].resource.snapshot.element[].comment
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

# entry[].resource.snapshot.element[].definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

# entry[].resource.snapshot.element[].requirements
Need to refer to a particular code in the system.

# entry[].resource.snapshot.element[].definition
A representation of the meaning of the code in the system, following the rules of the system.

# entry[].resource.snapshot.element[].requirements
Need to be able to carry a human-readable meaning of the code for readers that do not know  the system.

# entry[].resource.snapshot.element[].mapping[].map
C*E.2 - but note this is not well followed

# entry[].resource.snapshot.element[].short
If this coding was chosen directly by the user

# entry[].resource.snapshot.element[].definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).

# entry[].resource.snapshot.element[].comment
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

# entry[].resource.snapshot.element[].requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

# entry[].resource.snapshot.element[].mapping[].map
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map;   fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [     fhir:source "true";     fhir:target dt:CDCoding.codingRationale\#O   ]

# entry[].resource.snapshot.element[].short
Plain text representation of the concept

# entry[].resource.snapshot.element[].definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

# entry[].resource.snapshot.element[].comment
Very often the text is the same as a displayName of one of the codings.

# entry[].resource.snapshot.element[].requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

# entry[].resource.snapshot.element[].mapping[].map
C*E.9. But note many systems use C*E.2 for this

# entry[].resource.snapshot.element[].comment
Used when observation has a set of component observations. An observation may have both a value (e.g. an  Apgar score)  and component observations (the observations from which the Apgar score was derived). If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value.  For additional guidance, see the [Notes section](observation.html#notes) below.

# entry[].resource.snapshot.element[].requirements
9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305).

# entry[].resource.snapshot.element[].binding.description
Common UCUM units for recording Vital Signs.

# entry[].resource.snapshot.element[].definition
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

# entry[].resource.snapshot.element[].slicing.description
Extensions are always sliced by (at least) url

# entry[].resource.snapshot.element[].short
Additional content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].short
Numerical value (with implicit precision)

# entry[].resource.snapshot.element[].definition
The value of the measured amount. The value includes an implicit precision in the presentation of the value.

# entry[].resource.snapshot.element[].comment
The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).

# entry[].resource.snapshot.element[].requirements
Precision is handled implicitly in almost all cases of measurement.

# entry[].resource.snapshot.element[].mapping[].map
PQ.value, CO.value, MO.value, IVL.high or IVL.low depending on the value

# entry[].resource.snapshot.element[].short
< | <= | >= | > - how to understand the value

# entry[].resource.snapshot.element[].definition
How the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues; e.g. if the comparator is "<" , then the real value is < stated value.

# entry[].resource.snapshot.element[].requirements
Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology.

# entry[].resource.snapshot.element[].meaningWhenMissing
If there is no comparator, then there is no modification of the value

# entry[].resource.snapshot.element[].isModifierReason
This is labeled as "Is Modifier" because the comparator modifies the interpretation of the value significantly. If there is no comparator, then there is no modification of the value

# entry[].resource.snapshot.element[].binding.description
How the Quantity should be understood and represented.

# entry[].resource.snapshot.element[].requirements
There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms.

# entry[].resource.snapshot.element[].definition
The identification of the system that provides the coded form of the unit.

# entry[].resource.snapshot.element[].requirements
Need to know the system that defines the coded form of the unit.

# entry[].resource.snapshot.element[].short
Coded responses from the common UCUM units for vital signs value set.

# entry[].resource.snapshot.element[].definition
Coded responses from the common UCUM units for vital signs value set.

# entry[].resource.snapshot.element[].comment
The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency.  The context of use may additionally require a code from a particular system.

# entry[].resource.snapshot.element[].requirements
Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest.

# entry[].resource.snapshot.element[].definition
Provides a reason why the expected value in the element Observation.component.value[x] is missing.

# entry[].resource.snapshot.element[].comment
"Null" or exceptional values can be represented two ways in FHIR Observations.  One way is to simply include them in the value set and represent the exceptions in the value.  For example, measurement values for a serology test could be  "detected", "not detected", "inconclusive", or  "test not done". 

The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values.  For example, the dataAbsentReason code "error" could be used when the measurement was not completed.  Because of these options, use-case agreements are required to interpret general observations for exceptional values.

# entry[].resource.snapshot.element[].requirements
For many results it is necessary to handle exceptional values in measurements.

# entry[].resource.snapshot.element[].binding.description
Codes specifying why the result (`Observation.value[x]`) is missing.

# entry[].resource.snapshot.element[].definition
A categorical assessment of an observation value.  For example, high, low, normal.

# entry[].resource.snapshot.element[].comment
Historically used for laboratory results (known as 'abnormal flag' ),  its use extends to other use cases where coded interpretations  are relevant.  Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result.

# entry[].resource.snapshot.element[].requirements
For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result.

# entry[].resource.snapshot.element[].short
Provides guide for interpretation of component result

# entry[].resource.snapshot.element[].definition
Guidance on how to interpret the value by comparison to a normal or recommended range.

# entry[].resource.snapshot.element[].comment
Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.

# entry[].resource.snapshot.element[].requirements
Knowing what values are considered "normal" can help evaluate the significance of a particular result. Need to be able to provide multiple reference ranges for different contexts.

# entry[].resource.snapshot.element[].short
Used when reporting systolic and diastolic blood pressure.

# entry[].resource.snapshot.element[].definition
Used when reporting systolic and diastolic blood pressure.

# entry[].resource.snapshot.element[].comment
For a discussion on the ways Observations can be assembled in groups together see [Notes](observation.html#notes) below.

# entry[].resource.snapshot.element[].requirements
Component observations share the same attributes in the Observation resource as the primary observation and are always treated a part of a single observation (they are not separable).   However, the reference range for the primary observation value is not inherited by the component values and is required when appropriate for each component observation.

# entry[].resource.snapshot.element[].constraint[].human
All FHIR elements must have a @value or children

# entry[].resource.snapshot.element[].constraint[].expression
hasValue() or (children().count() > id.count())

# entry[].resource.snapshot.element[].constraint[].human
If there is no a value a data absent reason must be present

# entry[].resource.snapshot.element[].definition
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

# entry[].resource.snapshot.element[].short
Additional content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].short
Extensions that cannot be ignored even if unrecognized

# entry[].resource.snapshot.element[].definition
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).

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].requirements
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](extensibility.html#modifierExtension).

# entry[].resource.snapshot.element[].isModifierReason
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them

# entry[].resource.snapshot.element[].short
Type of component observation (code / type)

# entry[].resource.snapshot.element[].definition
Describes what was observed. Sometimes this is called the observation "code".

# entry[].resource.snapshot.element[].comment
additional codes that translate or map to this code are allowed.  For example a more granular LOINC code or code that is used locally in a system.

# entry[].resource.snapshot.element[].requirements
Knowing what kind of observation is being made is essential to understanding the observation.

# entry[].resource.snapshot.element[].binding.description
This identifies the vital sign result type.

# entry[].resource.snapshot.element[].mapping[].map
< 363787002 |Observable entity| OR 
< 386053000 |Evaluation procedure|

# entry[].resource.snapshot.element[].definition
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

# entry[].resource.snapshot.element[].slicing.description
Extensions are always sliced by (at least) url

# entry[].resource.snapshot.element[].short
Additional content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].comment
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.  Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

# entry[].resource.snapshot.element[].requirements
Allows for alternative encodings within a code system, and translations to other code systems.

# entry[].resource.snapshot.element[].comment
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.  Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

# entry[].resource.snapshot.element[].requirements
Allows for alternative encodings within a code system, and translations to other code systems.

# entry[].resource.snapshot.element[].definition
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

# entry[].resource.snapshot.element[].slicing.description
Extensions are always sliced by (at least) url

# entry[].resource.snapshot.element[].short
Additional content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].definition
The identification of the code system that defines the meaning of the symbol in the code.

# entry[].resource.snapshot.element[].comment
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...).  OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

# entry[].resource.snapshot.element[].requirements
Need to be unambiguous about the source of the definition of the symbol.

# entry[].resource.snapshot.element[].definition
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

# entry[].resource.snapshot.element[].comment
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

# entry[].resource.snapshot.element[].definition
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

# entry[].resource.snapshot.element[].requirements
Need to refer to a particular code in the system.

# entry[].resource.snapshot.element[].definition
A representation of the meaning of the code in the system, following the rules of the system.

# entry[].resource.snapshot.element[].requirements
Need to be able to carry a human-readable meaning of the code for readers that do not know  the system.

# entry[].resource.snapshot.element[].mapping[].map
C*E.2 - but note this is not well followed

# entry[].resource.snapshot.element[].short
If this coding was chosen directly by the user

# entry[].resource.snapshot.element[].definition
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).

# entry[].resource.snapshot.element[].comment
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

# entry[].resource.snapshot.element[].requirements
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

# entry[].resource.snapshot.element[].mapping[].map
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map;   fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [     fhir:source "true";     fhir:target dt:CDCoding.codingRationale\#O   ]

# entry[].resource.snapshot.element[].short
Plain text representation of the concept

# entry[].resource.snapshot.element[].definition
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

# entry[].resource.snapshot.element[].comment
Very often the text is the same as a displayName of one of the codings.

# entry[].resource.snapshot.element[].requirements
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

# entry[].resource.snapshot.element[].mapping[].map
C*E.9. But note many systems use C*E.2 for this

# entry[].resource.snapshot.element[].comment
Used when observation has a set of component observations. An observation may have both a value (e.g. an  Apgar score)  and component observations (the observations from which the Apgar score was derived). If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value.  For additional guidance, see the [Notes section](observation.html#notes) below.

# entry[].resource.snapshot.element[].requirements
9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305).

# entry[].resource.snapshot.element[].binding.description
Common UCUM units for recording Vital Signs.

# entry[].resource.snapshot.element[].definition
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

# entry[].resource.snapshot.element[].slicing.description
Extensions are always sliced by (at least) url

# entry[].resource.snapshot.element[].short
Additional content defined by implementations

# entry[].resource.snapshot.element[].definition
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.

# entry[].resource.snapshot.element[].comment
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.

# entry[].resource.snapshot.element[].short
Numerical value (with implicit precision)

# entry[].resource.snapshot.element[].definition
The value of the measured amount. The value includes an implicit precision in the presentation of the value.

# entry[].resource.snapshot.element[].comment
The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).

# entry[].resource.snapshot.element[].requirements
Precision is handled implicitly in almost all cases of measurement.

# entry[].resource.snapshot.element[].mapping[].map
PQ.value, CO.value, MO.value, IVL.high or IVL.low depending on the value

# entry[].resource.snapshot.element[].short
< | <= | >= | > - how to understand the value

# entry[].resource.snapshot.element[].definition
How the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues; e.g. if the comparator is "<" , then the real value is < stated value.

# entry[].resource.snapshot.element[].requirements
Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology.

# entry[].resource.snapshot.element[].meaningWhenMissing
If there is no comparator, then there is no modification of the value

# entry[].resource.snapshot.element[].isModifierReason
This is labeled as "Is Modifier" because the comparator modifies the interpretation of the value significantly. If there is no comparator, then there is no modification of the value

# entry[].resource.snapshot.element[].binding.description
How the Quantity should be understood and represented.

# entry[].resource.snapshot.element[].requirements
There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms.

# entry[].resource.snapshot.element[].definition
The identification of the system that provides the coded form of the unit.

# entry[].resource.snapshot.element[].requirements
Need to know the system that defines the coded form of the unit.

# entry[].resource.snapshot.element[].short
Coded responses from the common UCUM units for vital signs value set.

# entry[].resource.snapshot.element[].definition
Coded responses from the common UCUM units for vital signs value set.

# entry[].resource.snapshot.element[].comment
The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency.  The context of use may additionally require a code from a particular system.

# entry[].resource.snapshot.element[].requirements
Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest.

# entry[].resource.snapshot.element[].definition
Provides a reason why the expected value in the element Observation.component.value[x] is missing.

# entry[].resource.snapshot.element[].comment
"Null" or exceptional values can be represented two ways in FHIR Observations.  One way is to simply include them in the value set and represent the exceptions in the value.  For example, measurement values for a serology test could be  "detected", "not detected", "inconclusive", or  "test not done". 

The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values.  For example, the dataAbsentReason code "error" could be used when the measurement was not completed.  Because of these options, use-case agreements are required to interpret general observations for exceptional values.

# entry[].resource.snapshot.element[].requirements
For many results it is necessary to handle exceptional values in measurements.

# entry[].resource.snapshot.element[].binding.description
Codes specifying why the result (`Observation.value[x]`) is missing.

# entry[].resource.snapshot.element[].definition
A categorical assessment of an observation value.  For example, high, low, normal.

# entry[].resource.snapshot.element[].comment
Historically used for laboratory results (known as 'abnormal flag' ),  its use extends to other use cases where coded interpretations  are relevant.  Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result.

# entry[].resource.snapshot.element[].requirements
For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result.

# entry[].resource.snapshot.element[].short
Provides guide for interpretation of component result

# entry[].resource.snapshot.element[].definition
Guidance on how to interpret the value by comparison to a normal or recommended range.

# entry[].resource.snapshot.element[].comment
Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.

# entry[].resource.snapshot.element[].requirements
Knowing what values are considered "normal" can help evaluate the significance of a particular result. Need to be able to provide multiple reference ranges for different contexts.

# entry[].resource.differential.element[].definition
This profile defines  how to represent Blood Pressure observations in FHIR using a standard LOINC code and UCUM units of measure.  This is a grouping structure. It has no value in Observation.valueQuantity but contains at least one component (systolic and/or diastolic).

# entry[].resource.differential.element[].comment
additional codes that translate or map to this code are allowed.  For example a more granular LOINC code or code that is used locally in a system.

# entry[].resource.differential.element[].comment
additional codes that translate or map to this code are allowed.  For example a more granular LOINC code or code that is used locally in a system.

# entry[].resource.differential.element[].short
Coded responses from the common UCUM units for vital signs value set.

# entry[].resource.differential.element[].definition
Coded responses from the common UCUM units for vital signs value set.

# entry[].resource.differential.element[].comment
additional codes that translate or map to this code are allowed.  For example a more granular LOINC code or code that is used locally in a system.

# entry[].resource.differential.element[].short
Coded responses from the common UCUM units for vital signs value set.

# entry[].resource.differential.element[].definition
Coded responses from the common UCUM units for vital signs value set.

# entry[].resource.text.div
해당 Immunization 리소스는 질병관리본부에서 권장하는 성인 예방접종을 대상으로 Immunization 리소스를 profile을 하였다. 현재 질병관리본부에서 제공하는 예방접종증명서는 단순히 예방 접종하였는지에 대한 정보만 표현하고 있어서 환자가 접종을 하기 전 검사를 통해 항체가 있는지 유무는 전혀 표현하고 있지 않다. 이러한 정보를 리소스에 표현한다. status는 예방 접종을 실시 되었는지 정보를 의미한다. ( completed : 예방 접종이 실시 됨, not-done : 예방 접종 미실시) statusReason은 예방 접종 미실시된 이유를 의미한다. ( IMMUNE : 환자가 이미 항체를 가지고 있다. | MEDPREC : 백신이 억제되거나 예방조치가 보장되는 의학적 상태를 가지고 있다. | OSTOCK : 접종을 수행하기 위한 제품이 없다. | PATOBJ : 환자나 보호자가 접종을 거부한다. ) vaccineCode는 질병관리본부에서 지정한 11가지 질병에 관한 12가지 백신을 http://hl7.org/fhir/ValueSet/vaccine-code에 지정된 코드와 매핑하였다.( Flu : 16 / Tdap : 115 / Td (adult) : 138 / PPSV23 : 33 / PCV13 : 133 / Hep A : 52 / Hep B : 43 / Var : 21 / MMR : 03 / HPV, bivalent : 118 ,quadrivalent : 62, unspecified formulation : 137, HPV9 : 165 / herpes simplex 2 : 60 / MCV 4, unspecified formulation : 147, MCV4O : 136, MCV4P : 114 / Hib, HbOC : 47, PRP-D : 46, PRP-OMP : 49, PRP-T : 48, unspecified formulation : 17, Hib-Hep B : 51 ) patient는 해당 환자에 대한 정보를 의미한다. occurence는 해당 검사가 실시된 날짜를 의미한다. performer는 해당 검사를 수행한 의사나 기관을 의미한다.

# entry[].resource.description
예방접종 기록을 관리하는 리소스. 현재 질병관리본부에서 사용하고 있는 예방접종기록에 자신이 보유한 항체 데이터를 기록하는 기록지

# entry[].resource.purpose
질병관리본부에서 제공하는 예방접종기록(성인권고 예방접종)에 자신이 가진 항체 데이터를 기록, 관리하는 위한 리소스

# entry[].resource.differential.element[].definition
예방접종 기록. 예방접종을 하지 않았다면, 그 이유가 무엇인지를 기록한다. 예를들어 이미 몸 속에 항체가 있다는 것을 기록할 수 있다.

# entry[].resource.differential.element[].definition
현재 예방접종 상태를 나타낸다.
http://hl7.org/fhir/ValueSet/immunization-status 코드를 사용한다.
compeleted는 예방 접종일 실시 됨, not-done은 예방 접종 미실시를 의미한다.

# entry[].resource.differential.element[].short
예방접종 하지 않은 이유

# entry[].resource.differential.element[].definition
예방 접종을 하지 않은 이유
http://terminology.hl7.org/CodeSystem/v3-ActReason에 정의된 코드를 사용. 일치하는 코드가 없다면 추가 가능.
IMMUNE | MEDPREC | OSTOCK | PATOBJ

# entry[].resource.differential.element[].definition
http://hl7.org/fhir에 정의된 vaccine-code ValueSet을 사용하여 현재 한국 성인에게 권장되는 백신 코드를 정의한다.
Flu | Tdap/Td | PPSV23 | PCV13 | HepA | HepB | Var | MMR | HPV | HZV | MCV4 | Hib

# entry[].resource.differential.element[].definition
예방접종 관련 서비스를 받은 환자의 정보

# entry[].resource.differential.element[].short
백신 접종 일자/예정일

# entry[].resource.differential.element[].definition
백신 접종 일자 / 예정일

# entry[].resource.differential.element[].short
의료 서비스를 제공한 사람

# entry[].resource.differential.element[].definition
예방 접종이나 항체 검사를 제공한 사람을 나타낸다.

# entry[].resource.differential.element[].short
의료 서비스를 제공한 사람의 타입

# entry[].resource.differential.element[].definition
http://hl7.org/fhir/에 정의된 immunization-function ValueSet에 있는 코드를 사용하여 표현한다.
Ordering Provider | Administering Provider

# entry[].resource.differential.element[].short
의사나 기관을 나타낸다.