com.babylonhealth.lit.hl7.model

`type`

• Categorizes the account for reporting and searching purposes.

contained

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

coverage

• The party(s) that are responsible for covering the payment of this account, and what order should they be applied to the account.

description

• Provides additional information about what the account tracks and how it is used.

extension

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

guarantor

• The parties responsible for balancing the account if other payment options fall short.

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• Unique identifier used to reference the account. Might or might not be intended for human use (e.g. credit card number).

implicitRules

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

language

• The base language in which the resource is written.

meta

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

modifierExtension

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

name

• Name used for the account when displaying it to humans in reports, etc.

owner

• Indicates the service area, hospital, department, etc. with responsibility for managing the Account.

partOf

• Reference to a parent Account.

servicePeriod

• The date range of services associated with this account.

status

• Indicates whether the account is presently used/usable or not.

subject

• Identifies the entity which incurs the expenses. While the immediate recipients of services or goods might be entities related to the subject, the expenses were ultimately incurred by the subject of the Account.

text

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

Introduces the fields type, name, owner, status, partOf, subject, identifier, description, servicePeriod, coverage, guarantor.

approvalDate

• The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage.

author

• An individiual or organization primarily involved in the creation and maintenance of the content.

bodySite

• Indicates the sites on the subject's body where the procedure should be performed (I.e. the target sites).

code

• Detailed description of the type of activity; e.g. What lab test, what procedure, what kind of encounter.

contact

• Contact details to assist a user in finding and communicating with the publisher.

contained

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

copyright

• A copyright statement relating to the activity definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the activity definition.

date

• The date (and optionally time) when the activity definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the activity definition changes.

description

• A free text natural language description of the activity definition from a consumer's perspective.

doNotPerform

• Set this to true if the definition is to indicate that a particular activity should NOT be performed. If true, this element should be interpreted to reinforce a negative coding. For example NPO as a code with a doNotPerform of true would still indicate to NOT perform the action.

dosage

• Provides detailed dosage instructions in the same way that they are described for MedicationRequest resources.

dynamicValue

• Dynamic values that will be evaluated to produce values for elements of the resulting resource. For example, if the dosage of a medication must be computed based on the patient's weight, a dynamic value would be used to specify an expression that calculated the weight, and the path on the request resource that would contain the result.

editor

• An individual or organization primarily responsible for internal coherence of the content.

effectivePeriod

• The period during which the activity definition content was or is planned to be in active use.

endorser

• An individual or organization responsible for officially endorsing the content for use in some setting.

experimental

• A Boolean value to indicate that this activity definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• A formal identifier that is used to identify this activity definition when it is represented in other formats, or referenced in a specification, model, design or an instance.

implicitRules

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

intent

• Indicates the level of authority/intentionality associated with the activity and where the request should fit into the workflow chain.

jurisdiction

• A legal or geographic region in which the activity definition is intended to be used.

kind

• A description of the kind of resource the activity definition is representing. For example, a MedicationRequest, a ServiceRequest, or a CommunicationRequest. Typically, but not always, this is a Request resource.

language

• The base language in which the resource is written.

lastReviewDate

• The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date.

library

• A reference to a Library resource containing any formal logic used by the activity definition.

location

• Identifies the facility where the activity will occur; e.g. home, hospital, specific clinic, etc.

meta

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

modifierExtension

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

name

• A natural language name identifying the activity definition. This name should be usable as an identifier for the module by machine processing applications such as code generation.

observationRequirement

• Defines observation requirements for the action to be performed, such as body weight or surface area.

observationResultRequirement

• Defines the observations that are expected to be produced by the action.

participant

• Indicates who should participate in performing the action described.

priority

• Indicates how quickly the activity should be addressed with respect to other requests.

product

• Identifies the food, drug or other product being consumed or supplied in the activity.

profile

• A profile to which the target of the activity definition is expected to conform.

publisher

• The name of the organization or individual that published the activity definition.

purpose

• Explanation of why this activity definition is needed and why it has been designed as it has.

quantity

• Identifies the quantity expected to be consumed at once (per dose, per meal, etc.).

relatedArtifact

• Related artifacts such as additional documentation, justification, or bibliographic references.

reviewer

• An individual or organization primarily responsible for review of some aspect of the content.

specimenRequirement

• Defines specimen requirements for the action to be performed, such as required specimens for a lab test.

status

• The status of this activity definition. Enables tracking the life-cycle of the content.

subject

• A code or group definition that describes the intended subject of the activity being defined.

subtitle

• An explanatory or alternate title for the activity definition giving additional information about its content.

text

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

timing

• The period, timing or frequency upon which the described activity is to occur.

title

• A short, descriptive, user-friendly title for the activity definition.

topic

• Descriptive topics related to the content of the activity. Topics provide a high-level categorization of the activity that can be useful for filtering and searching.

transform

• A reference to a StructureMap resource that defines a transform that can be executed to produce the intent resource using the ActivityDefinition instance as the input.

url

• An absolute URI that is used to identify this activity definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this activity definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the activity definition is stored on different servers.

usage

• A detailed description of how the activity definition is used from a clinical perspective.

useContext

• The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate activity definition instances.

version

• The identifier that is used to identify this version of the activity definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the activity definition author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. To provide a version consistent with the Decision Support Service specification, use the format Major.Minor.Revision (e.g. 1.0.0). For more information on versioning knowledge assets, refer to the Decision Support Service specification. Note that a version is required for non-experimental active assets.

Introduces the fields url, name, date, kind, code, title, usage, topic, status, author, editor, intent, dosage, version, contact, purpose, library, profile, subtitle, reviewer, endorser, priority, location, quantity, bodySite, publisher, copyright, timing, transform, identifier, subject, useContext, product, description, experimental, jurisdiction, approvalDate, doNotPerform, lastReviewDate, effectivePeriod, relatedArtifact, specimenRequirement, observationRequirement, observationResultRequirement, participant, dynamicValue.

actuality

• Whether the event actually happened, or just had the potential to. Note that this is independent of whether anyone was affected or harmed or how severely.

category

• The overall type of event, intended for search and filtering purposes.

contained

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

contributor

• Parties that may or should contribute or have contributed information to the adverse event, which can consist of one or more activities. Such information includes information leading to the decision to perform the activity and how to perform the activity (e.g. consultant), information that the activity itself seeks to reveal (e.g. informant of clinical history), or information about what activity was performed (e.g. informant witness).

date

• The date (and perhaps time) when the adverse event occurred.

detected

• Estimated or actual date the AdverseEvent began, in the opinion of the reporter.

encounter

• The Encounter during which AdverseEvent was created or to which the creation of this record is tightly associated.

event

• This element defines the specific type of event that occurred or that was prevented from occurring.

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• Business identifiers assigned to this adverse event by the performer or other systems which remain constant as the resource is updated and propagates from server to server.

implicitRules

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

language

• The base language in which the resource is written.

location

• The information about where the adverse event occurred.

meta

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

modifierExtension

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

outcome

• Describes the type of outcome from the adverse event.

recordedDate

• The date on which the existence of the AdverseEvent was first recorded.

recorder

• Information on who recorded the adverse event. May be the patient or a practitioner.

referenceDocument

• AdverseEvent.referenceDocument.

resultingCondition

• Includes information about the reaction that occurred as a result of exposure to a substance (for example, a drug or a chemical).

seriousness

• Assessment whether this event was of real importance.

severity

• Describes the severity of the adverse event, in relation to the subject. Contrast to AdverseEvent.seriousness - a severe rash might not be serious, but a mild heart problem is.

study

• AdverseEvent.study.

subject

• This subject or group impacted by the event.

subjectMedicalHistory

• AdverseEvent.subjectMedicalHistory.

suspectEntity

• Describes the entity that is suspected to have caused the adverse event.

text

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

Introduces the fields date, event, study, subject, outcome, category, detected, location, severity, recorder, actuality, encounter, identifier, seriousness, contributor, recordedDate, referenceDocument, resultingCondition, subjectMedicalHistory, suspectEntity.

`type`

• Identification of the underlying physiological mechanism for the reaction risk.

asserter

• The source of the information about the allergy that is recorded.

category

• Category of the identified substance.

clinicalStatus

• The clinical status of the allergy or intolerance.

code

• Code for an allergy or intolerance statement (either a positive or a negated/excluded statement). This may be a code for a substance or pharmaceutical product that is considered to be responsible for the adverse reaction risk (e.g., "Latex"), an allergy or intolerance condition (e.g., "Latex allergy"), or a negated/excluded code for a specific substance or class (e.g., "No latex allergy") or a general or categorical negated statement (e.g., "No known allergy", "No known drug allergies"). Note: the substance for a specific reaction may be different from the substance identified as the cause of the risk, but it must be consistent with it. For instance, it may be a more specific substance (e.g. a brand medication) or a composite product that includes the identified substance. It must be clinically safe to only process the 'code' and ignore the 'reaction.substance'. If a receiving system is unable to confirm that AllergyIntolerance.reaction.substance falls within the semantic scope of AllergyIntolerance.code, then the receiving system should ignore AllergyIntolerance.reaction.substance.

contained

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

criticality

• Estimate of the potential clinical harm, or seriousness, of the reaction to the identified substance.

encounter

• The encounter when the allergy or intolerance was asserted.

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• Business identifiers assigned to this AllergyIntolerance by the performer or other systems which remain constant as the resource is updated and propagates from server to server.

implicitRules

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

language

• The base language in which the resource is written.

lastOccurrence

• Represents the date and/or time of the last known occurrence of a reaction event.

meta

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

modifierExtension

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

note

• Additional narrative about the propensity for the Adverse Reaction, not captured in other fields.

onset

• Estimated or actual date, date-time, or age when allergy or intolerance was identified.

patient

• The patient who has the allergy or intolerance.

reaction

• Details about each adverse reaction event linked to exposure to the identified substance.

recordedDate

• The recordedDate represents when this particular AllergyIntolerance record was created in the system, which is often a system-generated date.

recorder

• Individual who recorded the record and takes responsibility for its content.

text

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

verificationStatus

• Assertion about certainty associated with the propensity, or potential risk, of a reaction to the identified substance (including pharmaceutical product).

Introduces the fields type, code, note, patient, category, onset, recorder, asserter, encounter, identifier, criticality, recordedDate, clinicalStatus, lastOccurrence, verificationStatus, reaction.

appointmentType

• The style of appointment or patient that has been booked in the slot (not service type).

basedOn

• The service request this appointment is allocated to assess (e.g. incoming referral or procedure request).

cancelationReason

• The coded reason for the appointment being cancelled. This is often used in reporting/billing/futher processing to determine if further actions are required, or specific fees apply.

comment

• Additional comments about the appointment.

contained

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

created

• The date that this appointment was initially created. This could be different to the meta.lastModified value on the initial entry, as this could have been before the resource was created on the FHIR server, and should remain unchanged over the lifespan of the appointment.

description

• The brief description of the appointment as would be shown on a subject line in a meeting request, or appointment list. Detailed or expanded information should be put in the comment field.

end

• Date/Time that the appointment is to conclude.

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• This records identifiers associated with this appointment concern that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation).

implicitRules

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

language

• The base language in which the resource is written.

meta

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

minutesDuration

• Number of minutes that the appointment is to take. This can be less than the duration between the start and end times. For example, where the actual time of appointment is only an estimate or if a 30 minute appointment is being requested, but any time would work. Also, if there is, for example, a planned 15 minute break in the middle of a long appointment, the duration may be 15 minutes less than the difference between the start and end.

modifierExtension

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

participant

• List of participants involved in the appointment.

patientInstruction

• While Appointment.comment contains information for internal use, Appointment.patientInstructions is used to capture patient facing information about the Appointment (e.g. please bring your referral or fast from 8pm night before).

priority

• The priority of the appointment. Can be used to make informed decisions if needing to re-prioritize appointments. (The iCal Standard specifies 0 as undefined, 1 as highest, 9 as lowest priority).

reasonCode

• The coded reason that this appointment is being scheduled. This is more clinical than administrative.

reasonReference

• Reason the appointment has been scheduled to take place, as specified using information from another resource. When the patient arrives and the encounter begins it may be used as the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure.

requestedPeriod

• A set of date ranges (potentially including times) that the appointment is preferred to be scheduled within. The duration (usually in minutes) could also be provided to indicate the length of the appointment to fill and populate the start/end times for the actual allocated time. However, in other situations the duration may be calculated by the scheduling system.

serviceCategory

• A broad categorization of the service that is to be performed during this appointment.

serviceType

• The specific service that is to be performed during this appointment.

slot

• The slots from the participants' schedules that will be filled by the appointment.

specialty

• The specialty of a practitioner that would be required to perform the service requested in this appointment.

start

• Date/Time that the appointment is to take place.

status

• The overall status of the Appointment. Each of the participants has their own participation status which indicates their involvement in the process, however this status indicates the shared status.

supportingInformation

• Additional information to support the appointment provided when making the appointment.

text

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

Introduces the fields end, slot, start, status, created, comment, basedOn, priority, specialty, identifier, reasonCode, serviceType, description, serviceCategory, appointmentType, reasonReference, minutesDuration, requestedPeriod, cancelationReason, patientInstruction, supportingInformation, participant.

actor

• A Person, Location, HealthcareService, or Device that is participating in the appointment.

appointment

• Appointment that this response is replying to.

comment

• Additional comments about the appointment.

contained

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

end

• This may be either the same as the appointment request to confirm the details of the appointment, or alternately a new time to request a re-negotiation of the end time.

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• This records identifiers associated with this appointment response concern that are defined by business processes and/ or used to refer to it when a direct URL reference to the resource itself is not appropriate.

implicitRules

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

language

• The base language in which the resource is written.

meta

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

modifierExtension

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

participantStatus

• Participation status of the participant. When the status is declined or tentative if the start/end times are different to the appointment, then these times should be interpreted as a requested time change. When the status is accepted, the times can either be the time of the appointment (as a confirmation of the time) or can be empty.

participantType

• Role of participant in the appointment.

start

• Date/Time that the appointment is to take place, or requested new start time.

text

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

Introduces the fields end, start, actor, comment, identifier, appointment, participantType, participantStatus.

`type`

• Identifier for a family of the event. For example, a menu item, program, rule, policy, function code, application name or URL. It identifies the performed function.

action

• Indicator for type of action performed during the event that generated the audit.

agent

• An actor taking an active role in the event or activity that is logged.

contained

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

entity

• Specific instances of data or objects that have been accessed.

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

implicitRules

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

language

• The base language in which the resource is written.

meta

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

modifierExtension

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

outcome

• Indicates whether the event succeeded or failed.

outcomeDesc

• A free text description of the outcome of the event.

period

• The period during which the activity occurred.

purposeOfEvent

• The purposeOfUse (reason) that was used during the event being recorded.

recorded

• The time when the event was recorded.

source

• The system that is reporting the event.

subtype

• Identifier for the category of event.

text

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

Introduces the fields type, action, period, subtype, outcome, recorded, outcomeDesc, purposeOfEvent, source, agent, entity.

author

• Indicates who was responsible for creating the resource instance.

code

• Identifies the 'type' of resource - equivalent to the resource name for other resources.

contained

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

created

• Identifies when the resource was first created.

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• Identifier assigned to the resource for business purposes, outside the context of FHIR.

implicitRules

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

language

• The base language in which the resource is written.

meta

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

modifierExtension

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

subject

• Identifies the patient, practitioner, device or any other resource that is the "focus" of this resource.

text

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

Introduces the fields code, author, subject, created, identifier.

contentType

• MimeType of the binary content represented as a standard MimeType (BCP 13).

data

• The actual content, base64 encoded.

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

implicitRules

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

language

• The base language in which the resource is written.

meta

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

securityContext

• This element identifies another resource that can be used as a proxy of the security sensitivity to use when deciding and enforcing access control rules for the Binary resource. Given that the Binary resource contains very few elements that can be used to determine the sensitivity of the data and relationships to individuals, the referenced resource stands in as a proxy equivalent for this purpose. This referenced resource may be related to the Binary (e.g. Media, DocumentReference), or may be some non-related Resource purely as a security proxy. E.g. to identify that the binary resource relates to a patient, and access should only be granted to applications that have access to the patient.

Introduces the fields data, contentType, securityContext.

collection

• How this product was collected.

contained

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

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• This records identifiers associated with this biologically derived product instance that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation).

implicitRules

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

language

• The base language in which the resource is written.

manipulation

• Any manipulation of product post-collection that is intended to alter the product. For example a buffy-coat enrichment or CD8 reduction of Peripheral Blood Stem Cells to make it more suitable for infusion.

meta

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

modifierExtension

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

parent

• Parent product (if any).

processing

• Any processing of the product during collection that does not change the fundamental nature of the product. For example adding anti-coagulants during the collection of Peripheral Blood Stem Cells.

productCategory

• Broad category of this product.

productCode

• A code that identifies the kind of this biologically derived product (SNOMED Ctcode).

quantity

• Number of discrete units within this product.

request

• Procedure request to obtain this biologically derived product.

status

• Whether the product is currently available.

storage

• Product storage.

text

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

Introduces the fields status, parent, request, quantity, identifier, productCode, productCategory, storage, collection, processing, manipulation.

active

• Whether this body site is in active use.

contained

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

description

• A summary, characterization or explanation of the body structure.

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• Identifier for this instance of the anatomical structure.

image

• Image or images used to identify a location.

implicitRules

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

language

• The base language in which the resource is written.

location

• The anatomical location or region of the specimen, lesion, or body structure.

locationQualifier

• Qualifier to refine the anatomical location. These include qualifiers for laterality, relative location, directionality, number, and plane.

meta

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

modifierExtension

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

morphology

• The kind of structure being represented by the body structure at BodyStructure.location. This can define both normal and abnormal morphologies.

patient

• The person to which the body site belongs.

text

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

Introduces the fields image, active, patient, location, identifier, morphology, description, locationQualifier.

`type`

• Indicates the purpose of this bundle - how it is intended to be used.

entry

• An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• A persistent identifier for the bundle that won't change as a bundle is copied from server to server.

implicitRules

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

language

• The base language in which the resource is written.

link

• A series of links that provide context to this bundle.

meta

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

signature

• Digital Signature - base64 encoded. XML-DSig or a JWT.

timestamp

• The date/time that the bundle was assembled - i.e. when the resources were placed in the bundle.

total

• If a set of search matches, this is the total number of entries of type 'match' across all pages in the search. It does not include search.mode = 'include' or 'outcome' entries and it does not provide a count of the number of entries in the Bundle.

Introduces the fields type, total, timestamp, signature, identifier, link, entry.

contact

• Contact details to assist a user in finding and communicating with the publisher.

contained

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

copyright

• A copyright statement relating to the capability statement and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the capability statement.

date

• The date (and optionally time) when the capability statement was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the capability statement changes.

description

• A free text natural language description of the capability statement from a consumer's perspective. Typically, this is used when the capability statement describes a desired rather than an actual solution, for example as a formal expression of requirements as part of an RFP.

document

• A document definition.

experimental

• A Boolean value to indicate that this capability statement is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.

extension

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

fhirVersion

• The version of the FHIR specification that this CapabilityStatement describes (which SHALL be the same as the FHIR version of the CapabilityStatement itself). There is no default value.

format

• A list of the formats supported by this implementation using their content types.

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

implementation

• Identifies a specific implementation instance that is described by the capability statement - i.e. a particular installation, rather than the capabilities of a software program.

implementationGuide

• A list of implementation guides that the server does (or should) support in their entirety.

implicitRules

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

imports

• Reference to a canonical URL of another CapabilityStatement that this software adds to. The capability statement automatically includes everything in the other statement, and it is not duplicated, though the server may repeat the same resources, interactions and operations to add additional details to them.

instantiates

• Reference to a canonical URL of another CapabilityStatement that this software implements. This capability statement is a published API description that corresponds to a business service. The server may actually implement a subset of the capability statement it claims to implement, so the capability statement must specify the full capability details.

jurisdiction

• A legal or geographic region in which the capability statement is intended to be used.

kind

• The way that this statement is intended to be used, to describe an actual running instance of software, a particular product (kind, not instance of software) or a class of implementation (e.g. a desired purchase).

language

• The base language in which the resource is written.

messaging

• A description of the messaging capabilities of the solution.

meta

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

modifierExtension

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

name

• A natural language name identifying the capability statement. This name should be usable as an identifier for the module by machine processing applications such as code generation.

patchFormat

• A list of the patch formats supported by this implementation using their content types.

publisher

• The name of the organization or individual that published the capability statement.

purpose

• Explanation of why this capability statement is needed and why it has been designed as it has.

rest

• A definition of the restful capabilities of the solution, if any.

software

• Software that is covered by this capability statement. It is used when the capability statement describes the capabilities of a particular software version, independent of an installation.

status

• The status of this capability statement. Enables tracking the life-cycle of the content.

text

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

title

• A short, descriptive, user-friendly title for the capability statement.

url

• An absolute URI that is used to identify this capability statement when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this capability statement is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the capability statement is stored on different servers.

useContext

• The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate capability statement instances.

version

• The identifier that is used to identify this version of the capability statement when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the capability statement author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence.

Introduces the fields url, name, date, kind, title, status, format, version, contact, purpose, imports, publisher, copyright, useContext, description, fhirVersion, patchFormat, experimental, jurisdiction, instantiates, implementationGuide, software, document, implementation, rest, messaging.

activity

• Identifies a planned action to occur as part of the plan. For example, a medication to be used, lab tests to perform, self-monitoring, education, etc.

addresses

• Identifies the conditions/problems/concerns/diagnoses/etc. whose management and/or mitigation are handled by this plan.

author

• When populated, the author is responsible for the care plan. The care plan is attributed to the author.

basedOn

• A care plan that is fulfilled in whole or in part by this care plan.

careTeam

• Identifies all people and organizations who are expected to be involved in the care envisioned by this plan.

category

• Identifies what "kind" of plan this is to support differentiation between multiple co-existing plans; e.g. "Home health", "psychiatric", "asthma", "disease management", "wellness plan", etc.

contained

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

contributor

• Identifies the individual(s) or organization who provided the contents of the care plan.

created

• Represents when this particular CarePlan record was created in the system, which is often a system-generated date.

description

• A description of the scope and nature of the plan.

encounter

• The Encounter during which this CarePlan was created or to which the creation of this record is tightly associated.

extension

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

goal

• Describes the intended objective(s) of carrying out the care plan.

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• Business identifiers assigned to this care plan by the performer or other systems which remain constant as the resource is updated and propagates from server to server.

implicitRules

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

instantiatesCanonical

• The URL pointing to a FHIR-defined protocol, guideline, questionnaire or other definition that is adhered to in whole or in part by this CarePlan.

instantiatesUri

• The URL pointing to an externally maintained protocol, guideline, questionnaire or other definition that is adhered to in whole or in part by this CarePlan.

intent

• Indicates the level of authority/intentionality associated with the care plan and where the care plan fits into the workflow chain.

language

• The base language in which the resource is written.

meta

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

modifierExtension

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

note

• General notes about the care plan not covered elsewhere.

partOf

• A larger care plan of which this particular care plan is a component or step.

period

• Indicates when the plan did (or is intended to) come into effect and end.

replaces

• Completed or terminated care plan whose function is taken by this new care plan.

status

• Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.

subject

• Identifies the patient or group whose intended care is described by the plan.

supportingInfo

• Identifies portions of the patient's record that specifically influenced the formation of the plan. These might include comorbidities, recent procedures, limitations, recent assessments, etc.

text

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

title

• Human-friendly name for the care plan.

Introduces the fields goal, note, title, partOf, status, intent, period, author, basedOn, subject, created, replaces, category, careTeam, encounter, addresses, identifier, description, contributor, supportingInfo, instantiatesUri, instantiatesCanonical, activity.

category

• Identifies what kind of team. This is to support differentiation between multiple co-existing teams, such as care plan team, episode of care team, longitudinal care team.

contained

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

encounter

• The Encounter during which this CareTeam was created or to which the creation of this record is tightly associated.

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• Business identifiers assigned to this care team by the performer or other systems which remain constant as the resource is updated and propagates from server to server.

implicitRules

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

language

• The base language in which the resource is written.

managingOrganization

• The organization responsible for the care team.

meta

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

modifierExtension

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

name

• A label for human use intended to distinguish like teams. E.g. the "red" vs. "green" trauma teams.

note

• Comments made about the CareTeam.

participant

• Identifies all people and organizations who are expected to be involved in the care team.

period

• Indicates when the team did (or is intended to) come into effect and end.

reasonCode

• Describes why the care team exists.

reasonReference

• Condition(s) that this care team addresses.

status

• Indicates the current state of the care team.

subject

• Identifies the patient or group whose intended care is handled by the team.

telecom

• A central contact detail for the care team (that applies to all members).

text

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

Introduces the fields name, note, status, period, subject, telecom, category, encounter, identifier, reasonCode, reasonReference, managingOrganization, participant.

`type`

• The type of item - medication, device, service, protocol or other.

additionalCharacteristic

• Used for examplefor Out of Formulary, or any specifics.

additionalClassification

• User for example for ATC classification, or.

additionalIdentifier

• Used in supporting related concepts, e.g. NDC to RxNorm.

classification

• Classes of devices, or ATC for medication.

contained

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

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• Used in supporting different identifiers for the same product, e.g. manufacturer code and retailer code.

implicitRules

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

language

• The base language in which the resource is written.

lastUpdated

• Typically date of issue is different from the beginning of the validity. This can be used to see when an item was last updated.

meta

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

modifierExtension

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

orderable

• Whether the entry represents an orderable item.

referencedItem

• The item in a catalog or definition.

relatedEntry

• Used for example, to point to a substance, or to a device used to administer a medication.

status

• Used to support catalog exchange even for unsupported products, e.g. getting list of medications even if not prescribable.

text

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

validTo

• The date until which this catalog entry is expected to be active.

validityPeriod

• The time period in which this catalog entry is expected to be active.

Introduces the fields type, status, validTo, orderable, identifier, lastUpdated, referencedItem, classification, validityPeriod, additionalIdentifier, additionalCharacteristic, additionalClassification, relatedEntry.

account

• Account into which this ChargeItems belongs.

bodysite

• The anatomical location where the related service has been applied.

code

• A code that identifies the charge, like a billing code.

contained

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

context

• The encounter or episode of care that establishes the context for this event.

costCenter

• The financial cost center permits the tracking of charge attribution.

definitionCanonical

• References the source of pricing information, rules of application for the code this ChargeItem uses.

definitionUri

• References the (external) source of pricing information, rules of application for the code this ChargeItem uses.

enteredDate

• Date the charge item was entered.

enterer

• The device, practitioner, etc. who entered the charge item.

extension

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

factorOverride

• Factor overriding the factor determined by the rules associated with the code.

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• Identifiers assigned to this event performer or other systems.

implicitRules

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

language

• The base language in which the resource is written.

meta

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

modifierExtension

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

note

• Comments made about the event by the performer, subject or other participants.

occurrence

• Date/time(s) or duration when the charged service was applied.

overrideReason

• If the list price or the rule-based factor associated with the code is overridden, this attribute can capture a text to indicate the reason for this action.

partOf

• ChargeItems can be grouped to larger ChargeItems covering the whole set.

performer

• Indicates who or what performed or participated in the charged service.

performingOrganization

• The organization requesting the service.

priceOverride

• Total price of the charge overriding the list price associated with the code.

product

• Identifies the device, food, drug or other product being charged either by type code or reference to an instance.

quantity

• Quantity of which the charge item has been serviced.

reason

• Describes why the event occurred in coded or textual form.

requestingOrganization

• The organization performing the service.

service

• Indicated the rendered service that caused this charge.

status

• The current state of the ChargeItem.

subject

• The individual or set of individuals the action is being or was performed on.

supportingInformation

• Further information supporting this charge.

text

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

Introduces the fields code, note, status, partOf, reason, subject, context, enterer, service, account, quantity, bodysite, identifier, costCenter, product, enteredDate, definitionUri, occurrence, priceOverride, factorOverride, overrideReason, definitionCanonical, supportingInformation, performingOrganization, requestingOrganization, performer.

applicability

• Expressions that describe applicability criteria for the billing code.

approvalDate

• The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage.

code

• The defined billing details in this resource pertain to the given billing code.

contact

• Contact details to assist a user in finding and communicating with the publisher.

contained

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

copyright

• A copyright statement relating to the charge item definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the charge item definition.

date

• The date (and optionally time) when the charge item definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the charge item definition changes.

derivedFromUri

• The URL pointing to an externally-defined charge item definition that is adhered to in whole or in part by this definition.

description

• A free text natural language description of the charge item definition from a consumer's perspective.

effectivePeriod

• The period during which the charge item definition content was or is planned to be in active use.

experimental

• A Boolean value to indicate that this charge item definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• A formal identifier that is used to identify this charge item definition when it is represented in other formats, or referenced in a specification, model, design or an instance.

implicitRules

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

instance

• The defined billing details in this resource pertain to the given product instance(s).

jurisdiction

• A legal or geographic region in which the charge item definition is intended to be used.

language

• The base language in which the resource is written.

lastReviewDate

• The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date.

meta

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

modifierExtension

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

partOf

• A larger definition of which this particular definition is a component or step.

propertyGroup

• Group of properties which are applicable under the same conditions. If no applicability rules are established for the group, then all properties always apply.

publisher

• The name of the organization or individual that published the charge item definition.

replaces

• As new versions of a protocol or guideline are defined, allows identification of what versions are replaced by a new instance.

status

• The current state of the ChargeItemDefinition.

text

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

title

• A short, descriptive, user-friendly title for the charge item definition.

url

• An absolute URI that is used to identify this charge item definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this charge item definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the charge item definition is stored on different servers.

useContext

• The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate charge item definition instances.

version

• The identifier that is used to identify this version of the charge item definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the charge item definition author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. To provide a version consistent with the Decision Support Service specification, use the format Major.Minor.Revision (e.g. 1.0.0). For more information on versioning knowledge assets, refer to the Decision Support Service specification. Note that a version is required for non-experimental active assets.

Introduces the fields url, date, code, title, partOf, status, version, contact, replaces, instance, publisher, copyright, identifier, useContext, description, experimental, jurisdiction, approvalDate, derivedFromUri, lastReviewDate, effectivePeriod, applicability, propertyGroup.

`type`

• The category of claim, e.g. oral, pharmacy, vision, institutional, professional.

accident

• Details of an accident which resulted in injuries which required the products and services listed in the claim.

billablePeriod

• The period for which charges are being submitted.

careTeam

• The members of the team who provided the products and services.

contained

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

created

• The date this resource was created.

diagnosis

• Information about diagnoses relevant to the claim items.

enterer

• Individual who created the claim, predetermination or preauthorization.

extension

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

facility

• Facility where the services were provided.

fundsReserve

• A code to indicate whether and for whom funds are to be reserved for future claims.

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• A unique identifier assigned to this claim.

implicitRules

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

insurance

• Financial instruments for reimbursement for the health care products and services specified on the claim.

insurer

• The Insurer who is target of the request.

item

• A claim line. Either a simple product or service or a 'group' of details which can each be a simple items or groups of sub-details.

language

• The base language in which the resource is written.

meta

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

modifierExtension

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

originalPrescription

• Original prescription which has been superseded by this prescription to support the dispensing of pharmacy services, medications or products.

patient

• The party to whom the professional services and/or products have been supplied or are being considered and for whom actual or forecast reimbursement is sought.

payee

• The party to be reimbursed for cost of the products and services according to the terms of the policy.

prescription

• Prescription to support the dispensing of pharmacy, device or vision products.

priority

• The provider-required urgency of processing the request. Typical values include: stat, routine deferred.

procedure

• Procedures performed on the patient relevant to the billing items with the claim.

provider

• The provider which is responsible for the claim, predetermination or preauthorization.

referral

• A reference to a referral resource.

related

• Other claims which are related to this claim such as prior submissions or claims for related services or for the same event.

status

• The status of the resource instance.

subType

• A finer grained suite of claim type codes which may convey additional information such as Inpatient vs Outpatient and/or a specialty service.

supportingInfo

• Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues.

text

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

total

• The total value of the all the items in the claim.

use

• A code to indicate whether the nature of the request is: to request adjudication of products and services previously rendered; or requesting authorization and adjudication for provision in the future; or requesting the non-binding adjudication of the listed products and services which could be provided in the future.

Introduces the fields use, type, total, status, subType, patient, created, enterer, insurer, provider, priority, referral, facility, identifier, fundsReserve, prescription, billablePeriod, originalPrescription, payee, related, careTeam, accident, diagnosis, procedure, insurance, supportingInfo, item.

`type`

• A finer grained suite of claim type codes which may convey additional information such as Inpatient vs Outpatient and/or a specialty service.

addItem

• The first-tier service adjudications for payor added product or service lines.

adjudication

• The adjudication results which are presented at the header level rather than at the line-item or add-item levels.

communicationRequest

• Request for additional supporting or authorizing information.

contained

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

created

• The date this resource was created.

disposition

• A human readable description of the status of the adjudication.

error

• Errors encountered during the processing of the adjudication.

extension

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

form

• The actual form, by reference or inclusion, for printing the content or an EOB.

formCode

• A code for the form to be used for printing the content.

fundsReserve

• A code, used only on a response to a preauthorization, to indicate whether the benefits payable have been reserved and for whom.

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• A unique identifier assigned to this claim response.

implicitRules

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

insurance

• Financial instruments for reimbursement for the health care products and services specified on the claim.

insurer

• The party responsible for authorization, adjudication and reimbursement.

item

• A claim line. Either a simple (a product or service) or a 'group' of details which can also be a simple items or groups of sub-details.

language

• The base language in which the resource is written.

meta

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

modifierExtension

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

outcome

• The outcome of the claim, predetermination, or preauthorization processing.

patient

• The party to whom the professional services and/or products have been supplied or are being considered and for whom actual for facast reimbursement is sought.

payeeType

• Type of Party to be reimbursed: subscriber, provider, other.

payment

• Payment details for the adjudication of the claim.

preAuthPeriod

• The time frame during which this authorization is effective.

preAuthRef

• Reference from the Insurer which is used in later communications which refers to this adjudication.

processNote

• A note that describes or explains adjudication results in a human readable form.

request

• Original request resource reference.

requestor

• The provider which is responsible for the claim, predetermination or preauthorization.

status

• The status of the resource instance.

subType

• A finer grained suite of claim type codes which may convey additional information such as Inpatient vs Outpatient and/or a specialty service.

text

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

total

• Categorized monetary totals for the adjudication.

use

• A code to indicate whether the nature of the request is: to request adjudication of products and services previously rendered; or requesting authorization and adjudication for provision in the future; or requesting the non-binding adjudication of the listed products and services which could be provided in the future.

Introduces the fields use, type, form, status, subType, patient, created, insurer, request, outcome, formCode, requestor, payeeType, identifier, preAuthRef, disposition, adjudication, fundsReserve, preAuthPeriod, communicationRequest, total, error, payment, processNote, insurance, item, addItem.

assessor

• The clinician performing the assessment.

code

• Categorizes the type of clinical assessment performed.

contained

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

date

• Indicates when the documentation of the assessment was complete.

description

• A summary of the context and/or cause of the assessment - why / where it was performed, and what patient events/status prompted it.

effective

• The point in time or period over which the subject was assessed.

encounter

• The Encounter during which this ClinicalImpression was created or to which the creation of this record is tightly associated.

extension

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

finding

• Specific findings or diagnoses that were considered likely or relevant to ongoing treatment.

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• Business identifiers assigned to this clinical impression by the performer or other systems which remain constant as the resource is updated and propagates from server to server.

implicitRules

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

investigation

• One or more sets of investigations (signs, symptoms, etc.). The actual grouping of investigations varies greatly depending on the type and context of the assessment. These investigations may include data generated during the assessment process, or data previously generated and recorded that is pertinent to the outcomes.

language

• The base language in which the resource is written.

meta

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

modifierExtension

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

note

• Commentary about the impression, typically recorded after the impression itself was made, though supplemental notes by the original author could also appear.

previous

• A reference to the last assessment that was conducted on this patient. Assessments are often/usually ongoing in nature; a care provider (practitioner or team) will make new assessments on an ongoing basis as new data arises or the patient's conditions changes.

problem

• A list of the relevant problems/conditions for a patient.

prognosisCodeableConcept

• Estimate of likely outcome.

prognosisReference

• RiskAssessment expressing likely outcome.

protocol

• Reference to a specific published clinical protocol that was followed during this assessment, and/or that provides evidence in support of the diagnosis.

status

• Identifies the workflow status of the assessment.

statusReason

• Captures the reason for the current state of the ClinicalImpression.

subject

• The patient or group of individuals assessed as part of this record.

summary

• A text summary of the investigations and the diagnosis.

supportingInfo

• Information supporting the clinical impression.

text

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

Introduces the fields code, date, note, status, subject, problem, summary, assessor, previous, protocol, encounter, identifier, description, statusReason, effective, supportingInfo, prognosisReference, prognosisCodeableConcept, finding, investigation.

caseSensitive

• If code comparison is case sensitive when codes within this system are compared to each other.

compositional

• The code system defines a compositional (post-coordination) grammar.

concept

• Concepts that are in the code system. The concept definitions are inherently hierarchical, but the definitions must be consulted to determine what the meanings of the hierarchical relationships are.

contact

• Contact details to assist a user in finding and communicating with the publisher.

contained

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

content

• The extent of the content of the code system (the concepts and codes it defines) are represented in this resource instance.

copyright

• A copyright statement relating to the code system and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the code system.

count

• The total number of concepts defined by the code system. Where the code system has a compositional grammar, the basis of this count is defined by the system steward.

date

• The date (and optionally time) when the code system was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the code system changes.

description

• A free text natural language description of the code system from a consumer's perspective.

experimental

• A Boolean value to indicate that this code system is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.

extension

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

filter

• A filter that can be used in a value set compose statement when selecting concepts using a filter.

hierarchyMeaning

• The meaning of the hierarchy of concepts as represented in this resource.

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• A formal identifier that is used to identify this code system when it is represented in other formats, or referenced in a specification, model, design or an instance.

implicitRules

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

jurisdiction

• A legal or geographic region in which the code system is intended to be used.

language

• The base language in which the resource is written.

meta

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

modifierExtension

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

name

• A natural language name identifying the code system. This name should be usable as an identifier for the module by machine processing applications such as code generation.

property

• A property defines an additional slot through which additional information can be provided about a concept.

publisher

• The name of the organization or individual that published the code system.

purpose

• Explanation of why this code system is needed and why it has been designed as it has.

status

• The date (and optionally time) when the code system resource was created or revised.

supplements

• The canonical URL of the code system that this code system supplement is adding designations and properties to.

text

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

title

• A short, descriptive, user-friendly title for the code system.

url

• An absolute URI that is used to identify this code system when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this code system is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the code system is stored on different servers. This is used in Coding.system.

useContext

• The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate code system instances.

valueSet

• Canonical reference to the value set that contains the entire code system.

version

• The identifier that is used to identify this version of the code system when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the code system author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. This is used in Coding.version.

versionNeeded

• This flag is used to signify that the code system does not commit to concept permanence across versions. If true, a version must be specified when referencing this code system.

Introduces the fields url, name, date, title, count, status, version, contact, purpose, content, valueSet, publisher, copyright, identifier, useContext, description, supplements, experimental, jurisdiction, caseSensitive, compositional, versionNeeded, hierarchyMeaning, filter, property, concept.

about

• Other resources that pertain to this communication and to which this communication should be associated.

basedOn

• An order, proposal or plan fulfilled in whole or in part by this Communication.

category

• The type of message conveyed such as alert, notification, reminder, instruction, etc.

contained

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

encounter

• The Encounter during which this Communication was created or to which the creation of this record is tightly associated.

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• Business identifiers assigned to this communication by the performer or other systems which remain constant as the resource is updated and propagates from server to server.

implicitRules

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

inResponseTo

• Prior communication that this communication is in response to.

instantiatesCanonical

• The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Communication.

instantiatesUri

• The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Communication.

language

• The base language in which the resource is written.

medium

• A channel that was used for this communication (e.g. email, fax).

meta

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

modifierExtension

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

note

• Additional notes or commentary about the communication by the sender, receiver or other interested parties.

partOf

• Part of this action.

payload

• Text, attachment(s), or resource(s) that was communicated to the recipient.

priority

• Characterizes how quickly the planned or in progress communication must be addressed. Includes concepts such as stat, urgent, routine.

reasonCode

• The reason or justification for the communication.

reasonReference

• Indicates another resource whose existence justifies this communication.

received

• The time when this communication arrived at the destination.

recipient

• The entity (e.g. person, organization, clinical information system, care team or device) which was the target of the communication. If receipts need to be tracked by an individual, a separate resource instance will need to be created for each recipient. Multiple recipient communications are intended where either receipts are not tracked (e.g. a mass mail-out) or a receipt is captured in aggregate (all emails confirmed received by a particular time).

sender

• The entity (e.g. person, organization, clinical information system, or device) which was the source of the communication.

sent

• The time when this communication was sent.

status

• The status of the transmission.

statusReason

• Captures the reason for the current state of the Communication.

subject

• The patient or group that was the focus of this communication.

text

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

topic

• Description of the purpose/content, similar to a subject line in an email.

Introduces the fields sent, note, topic, about, partOf, status, medium, sender, basedOn, subject, category, priority, received, encounter, recipient, identifier, reasonCode, inResponseTo, statusReason, instantiatesUri, reasonReference, instantiatesCanonical, payload.

about

• Other resources that pertain to this communication request and to which this communication request should be associated.

authoredOn

• For draft requests, indicates the date of initial creation. For requests with other statuses, indicates the date of activation.

basedOn

• A plan or proposal that is fulfilled in whole or in part by this request.

category

• The type of message to be sent such as alert, notification, reminder, instruction, etc.

contained

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

doNotPerform

• If true indicates that the CommunicationRequest is asking for the specified action to not occur.

encounter

• The Encounter during which this CommunicationRequest was created or to which the creation of this record is tightly associated.

extension

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

groupIdentifier

• A shared identifier common to all requests that were authorized more or less simultaneously by a single author, representing the identifier of the requisition, prescription or similar form.

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• Business identifiers assigned to this communication request by the performer or other systems which remain constant as the resource is updated and propagates from server to server.

implicitRules

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

language

• The base language in which the resource is written.

medium

• A channel that was used for this communication (e.g. email, fax).

meta

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

modifierExtension

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

note

• Comments made about the request by the requester, sender, recipient, subject or other participants.

occurrence

• The time when this communication is to occur.

payload

• Text, attachment(s), or resource(s) to be communicated to the recipient.

priority

• Characterizes how quickly the proposed act must be initiated. Includes concepts such as stat, urgent, routine.

reasonCode

• Describes why the request is being made in coded or textual form.

reasonReference

• Indicates another resource whose existence justifies this request.

recipient

• The entity (e.g. person, organization, clinical information system, device, group, or care team) which is the intended target of the communication.

replaces

• Completed or terminated request(s) whose function is taken by this new request.

requester

• The device, individual, or organization who initiated the request and has responsibility for its activation.

sender

• The entity (e.g. person, organization, clinical information system, or device) which is to be the source of the communication.

status

• The status of the proposal or order.

statusReason

• Captures the reason for the current state of the CommunicationRequest.

subject

• The patient or group that is the focus of this communication request.

text

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

Introduces the fields note, about, status, medium, sender, basedOn, subject, replaces, category, priority, encounter, requester, recipient, identifier, authoredOn, reasonCode, statusReason, doNotPerform, occurrence, groupIdentifier, reasonReference, payload.

code

• Which compartment this definition describes.

contact

• Contact details to assist a user in finding and communicating with the publisher.

contained

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

date

• The date (and optionally time) when the compartment definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the compartment definition changes.

description

• A free text natural language description of the compartment definition from a consumer's perspective.

experimental

• A Boolean value to indicate that this compartment definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

implicitRules

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

language

• The base language in which the resource is written.

meta

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

modifierExtension

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

name

• A natural language name identifying the compartment definition. This name should be usable as an identifier for the module by machine processing applications such as code generation.

publisher

• The name of the organization or individual that published the compartment definition.

purpose

• Explanation of why this compartment definition is needed and why it has been designed as it has.

resource

• Information about how a resource is related to the compartment.

search

• Whether the search syntax is supported,.

status

• The status of this compartment definition. Enables tracking the life-cycle of the content.

text

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

url

• An absolute URI that is used to identify this compartment definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this compartment definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the compartment definition is stored on different servers.

useContext

• The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate compartment definition instances.

version

• The identifier that is used to identify this version of the compartment definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the compartment definition author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence.

Introduces the fields url, name, date, code, status, search, version, contact, purpose, publisher, useContext, description, experimental, resource.

`type`

• Specifies the particular kind of composition (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the composition.

attester

• A participant who has attested to the accuracy of the composition/document.

author

• Identifies who is responsible for the information in the composition, not necessarily who typed it in.

category

• A categorization for the type of the composition - helps for indexing and searching. This may be implied by or derived from the code specified in the Composition Type.

confidentiality

• The code specifying the level of confidentiality of the Composition.

contained

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

custodian

• Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information.

date

• The composition editing time, when the composition was last logically changed by the author.

encounter

• Describes the clinical encounter or type of care this documentation is associated with.

event

• The clinical service, such as a colonoscopy or an appendectomy, being documented.

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• A version-independent identifier for the Composition. This identifier stays constant as the composition is changed over time.

implicitRules

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

language

• The base language in which the resource is written.

meta

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

modifierExtension

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

relatesTo

• Relationships that this composition has with other compositions or documents that already exist.

section

• The root of the sections that make up the composition.

status

• The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document.

subject

• Who or what the composition is about. The composition can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure).

text

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

title

• Official human-readable label for the composition.

Introduces the fields type, date, title, status, author, subject, category, encounter, custodian, identifier, confidentiality, event, section, attester, relatesTo.

contact

• Contact details to assist a user in finding and communicating with the publisher.

contained

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

copyright

• A copyright statement relating to the concept map and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the concept map.

date

• The date (and optionally time) when the concept map was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the concept map changes.

description

• A free text natural language description of the concept map from a consumer's perspective.

experimental

• A Boolean value to indicate that this concept map is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.

extension

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

group

• A group of mappings that all have the same source and target system.

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• A formal identifier that is used to identify this concept map when it is represented in other formats, or referenced in a specification, model, design or an instance.

implicitRules

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

jurisdiction

• A legal or geographic region in which the concept map is intended to be used.

language

• The base language in which the resource is written.

meta

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

modifierExtension

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

name

• A natural language name identifying the concept map. This name should be usable as an identifier for the module by machine processing applications such as code generation.

publisher

• The name of the organization or individual that published the concept map.

purpose

• Explanation of why this concept map is needed and why it has been designed as it has.

source

• Identifier for the source value set that contains the concepts that are being mapped and provides context for the mappings.

status

• The status of this concept map. Enables tracking the life-cycle of the content.

target

• The target value set provides context for the mappings. Note that the mapping is made between concepts, not between value sets, but the value set provides important context about how the concept mapping choices are made.

text

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

title

• A short, descriptive, user-friendly title for the concept map.

url

• An absolute URI that is used to identify this concept map when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this concept map is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the concept map is stored on different servers.

useContext

• The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate concept map instances.

version

• The identifier that is used to identify this version of the concept map when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the concept map author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence.

Introduces the fields url, name, date, title, status, version, contact, purpose, publisher, copyright, source, target, identifier, useContext, description, experimental, jurisdiction, group.

abatement

• The date or estimated date that the condition resolved or went into remission. This is called "abatement" because of the many overloaded connotations associated with "remission" or "resolution" - Conditions are never really resolved, but they can abate.

asserter

• Individual who is making the condition statement.

bodySite

• The anatomical location where this condition manifests itself.

category

• A category assigned to the condition.

clinicalStatus

• The clinical status of the condition.

code

• Identification of the condition, problem or diagnosis.

contained

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

encounter

• The Encounter during which this Condition was created or to which the creation of this record is tightly associated.

evidence

• Supporting evidence / manifestations that are the basis of the Condition's verification status, such as evidence that confirmed or refuted the condition.

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• Business identifiers assigned to this condition by the performer or other systems which remain constant as the resource is updated and propagates from server to server.

implicitRules

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

language

• The base language in which the resource is written.

meta

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

modifierExtension

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

note

• Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis.

onset

• Estimated or actual date or date-time the condition began, in the opinion of the clinician.

recordedDate

• The recordedDate represents when this particular Condition record was created in the system, which is often a system-generated date.

recorder

• Individual who recorded the record and takes responsibility for its content.

severity

• A subjective assessment of the severity of the condition as evaluated by the clinician.

stage

• Clinical stage or grade of a condition. May include formal severity assessments.

subject

• Indicates the patient or group who the condition record is associated with.

text

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

verificationStatus

• The verification status to support the clinical status of the condition.

Introduces the fields code, note, subject, category, severity, bodySite, onset, recorder, asserter, encounter, identifier, abatement, recordedDate, clinicalStatus, verificationStatus, stage, evidence.

category

• A classification of the type of consents found in the statement. This element supports indexing and retrieval of consent statements.

contained

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

dateTime

• When this Consent was issued / created / indexed.

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• Unique identifier for this copy of the Consent Statement.

implicitRules

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

language

• The base language in which the resource is written.

meta

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

modifierExtension

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

organization

• The organization that manages the consent, and the framework within which it is executed.

patient

• The patient/healthcare consumer to whom this consent applies.

performer

• Either the Grantor, which is the entity responsible for granting the rights listed in a Consent Directive or the Grantee, which is the entity responsible for complying with the Consent Directive, including any obligations or limitations on authorizations and enforcement of prohibitions.

policy

• The references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law.

policyRule

• A reference to the specific base computable regulation or policy.

provision

• An exception to the base policy of this consent. An exception can be an addition or removal of access permissions.

scope

• A selector of the type of consent being presented: ADR, Privacy, Treatment, Research. This list is now extensible.

source

• The source on which this consent statement is based. The source might be a scanned original paper form, or a reference to a consent that links back to such a source, a reference to a document repository (e.g. XDS) that stores the original consent document.

status

• Indicates the current state of this consent.

text

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

verification

• Whether a treatment instruction (e.g. artificial respiration yes or no) was verified with the patient, his/her family or another authorized person.

Introduces the fields scope, status, patient, category, dateTime, performer, source, identifier, policyRule, organization, policy, verification, provision.

`type`

• A high-level category for the legal instrument, whether constructed as a Contract definition, derivative, or instance in any legal state. Provides additional information about its content within the context of the Contract's scope to distinguish the kinds of systems that would be interested in the contract.

alias

• Alternative representation of the title for this Contract definition, derivative, or instance in any legal state., e.g., a domain specific contract number related to legislation.

applies

• Relevant time or time-period when this Contract is applicable.

author

• The individual or organization that authored the Contract definition, derivative, or instance in any legal state.

authority

• A formally or informally recognized grouping of people, principals, organizations, or jurisdictions formed for the purpose of achieving some form of collective action such as the promulgation, administration and enforcement of contracts and policies.

contained

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

contentDefinition

• Precusory content developed with a focus and intent of supporting the formation a Contract instance, which may be associated with and transformable into a Contract.

contentDerivative

• The minimal content derived from the basal information source at a specific stage in its lifecycle.

domain

• Recognized governance framework or system operating with a circumscribed scope in accordance with specified principles, policies, processes or procedures for managing rights, actions, or behaviors of parties or principals relative to resources.

expirationType

• Event resulting in discontinuation or termination of this Contract instance by one or more parties to the contract.

extension

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

friendly

• The "patient friendly language" versionof the Contract in whole or in parts. "Patient friendly language" means the representation of the Contract and Contract Provisions in a manner that is readily accessible and understandable by a layperson in accordance with best practices for communication styles that ensure that those agreeing to or signing the Contract understand the roles, actions, obligations, responsibilities, and implication of the agreement.

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• Unique identifier for this Contract or a derivative that references a Source Contract.

implicitRules

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

instantiatesCanonical

• The URL pointing to a FHIR-defined Contract Definition that is adhered to in whole or part by this Contract.

instantiatesUri

• The URL pointing to an externally maintained definition that is adhered to in whole or in part by this Contract.

issued

• When this Contract was issued.

language

• The base language in which the resource is written.

legal

• List of Legal expressions or representations of this Contract.

legalState

• Legal states of the formation of a legal instrument, which is a formally executed written document that can be formally attributed to its author, records and formally expresses a legally enforceable act, process, or contractual duty, obligation, or right, and therefore evidences that act, process, or agreement.

legallyBinding

• Legally binding Contract: This is the signed and legally recognized representation of the Contract, which is considered the "source of truth" and which would be the basis for legal action related to enforcement of this Contract.

meta

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

modifierExtension

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

name

• A natural language name identifying this Contract definition, derivative, or instance in any legal state. Provides additional information about its content. This name should be usable as an identifier for the module by machine processing applications such as code generation.

relevantHistory

• Links to Provenance records for past versions of this Contract definition, derivative, or instance, which identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the Contract. The Provence.entity indicates the target that was changed in the update. http://build.fhir.org/provenance-definitions.html#Provenance.entity.

rule

• List of Computable Policy Rule Language Representations of this Contract.

scope

• A selector of legal concerns for this Contract definition, derivative, or instance in any legal state.

signer

• Parties with legal standing in the Contract, including the principal parties, the grantor(s) and grantee(s), which are any person or organization bound by the contract, and any ancillary parties, which facilitate the execution of the contract such as a notary or witness.

site

• Sites in which the contract is complied with, exercised, or in force.

status

• The status of the resource instance.

subType

• Sub-category for the Contract that distinguishes the kinds of systems that would be interested in the Contract within the context of the Contract's scope.

subject

• The target entity impacted by or of interest to parties to the agreement.

subtitle

• An explanatory or alternate user-friendly title for this Contract definition, derivative, or instance in any legal state.t giving additional information about its content.

supportingInfo

• Information that may be needed by/relevant to the performer in their execution of this term action.

term

• One or more Contract Provisions, which may be related and conveyed as a group, and may contain nested groups.

text

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

title

• A short, descriptive, user-friendly title for this Contract definition, derivative, or instance in any legal state.t giving additional information about its content.

topic

• Narrows the range of legal concerns to focus on the achievement of specific contractual objectives.

url

• Canonical identifier for this contract, represented as a URI (globally unique).

version

• An edition identifier used for business purposes to label business significant variants.

Introduces the fields url, site, name, type, title, alias, scope, status, issued, domain, author, version, applies, subject, subType, subtitle, topic, authority, identifier, legalState, expirationType, supportingInfo, instantiatesUri, relevantHistory, contentDerivative, legallyBinding, instantiatesCanonical, rule, legal, signer, friendly, contentDefinition, term.

`class`

• A suite of underwriter specific classifiers.

`type`

• The type of coverage: social program, medical plan, accident coverage (workers compensation, auto), group health or payment by an individual or organization.

beneficiary

• The party who benefits from the insurance coverage; the patient when products and/or services are provided.

contained

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

contract

• The policy(s) which constitute this insurance coverage.

costToBeneficiary

• A suite of codes indicating the cost category and associated amount which have been detailed in the policy and may have been included on the health card.

dependent

• A unique identifier for a dependent under the coverage.

extension

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

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• A unique identifier assigned to this coverage.

implicitRules

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

language

• The base language in which the resource is written.

meta

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

modifierExtension

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

network

• The insurer-specific identifier for the insurer-defined network of providers to which the beneficiary may seek treatment which will be covered at the 'in-network' rate, otherwise 'out of network' terms and conditions apply.

order

• The order of applicability of this coverage relative to other coverages which are currently in force. Note, there may be gaps in the numbering and this does not imply primary, secondary etc. as the specific positioning of coverages depends upon the episode of care.

payor

• The program or plan underwriter or payor including both insurance and non-insurance agreements, such as patient-pay agreements.

period

• Time period during which the coverage is in force. A missing start date indicates the start date isn't known, a missing end date means the coverage is continuing to be in force.

policyHolder

• The party who 'owns' the insurance policy.

relationship

• The relationship of beneficiary (patient) to the subscriber.

status

• The status of the resource instance.

subrogation

• When 'subrogation=true' this insurance instance has been included not for adjudication but to provide insurers with the details to recover costs.

subscriber

• The party who has signed-up for or 'owns' the contractual relationship to the policy or to whom the benefit of the policy for services rendered to them or their family is due.

subscriberId

• The insurer assigned ID for the Subscriber.

text

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

Introduces the fields type, payor, order, status, period, network, contract, dependent, identifier, subscriber, beneficiary, subrogation, policyHolder, subscriberId, relationship, class, costToBeneficiary.

contained

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

created

• The date when this resource was created.

enterer

• Person who created the request.

extension

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

facility

• Facility where the services are intended to be provided.

id

• The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

identifier

• A unique identifier assigned to this coverage eligiblity request.

implicitRules

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

insurance

• Financial instruments for reimbursement for the health care products and services.

insurer

• The Insurer who issued the coverage in question and is the recipient of the request.

item

• Service categories or billable services for which benefit details and/or an authorization prior to service delivery may be required by the payor.

language

• The base language in which the resource is written.

meta

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

modifierExtension

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

patient

• The party who is the beneficiary of the supplied coverage and for whom eligibility is sought.

priority

• When the requestor expects the processor to complete processing.

provider

• The provider which is responsible for the request.

purpose

• Code to specify whether requesting: prior authorization requirements for some service categories or billing codes; benefits for coverages specified or discovered; discovery and return of coverages for the patient; and/or validation that the specified coverage is in-force at the date/period specified or 'now' if not specified.

serviced

• The date or dates when the enclosed suite of services were performed or completed.

status

• The status of the resource instance.

supportingInfo

• Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues.

text

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

Introduces the fields status, purpose, patient, created, enterer, insurer, priority, provider, facility, identifier, serviced, insurance, supportingInfo, item.