The apply operation applies a definition in a specific context

This operation is used to return all the information related to an encounter described in the resource on which this operation is invoked. The response is a bundle of type "searchset". At a minimum, the encounter resource itself is returned, along with any other resources that the server has available for the given encounter for the user. The server also returns whatever resources are needed to support the records - e.g. linked practitioners, locations, organizations etc. The principle intended use for this operation is to provide a patient with access to their record, or to allow a client to retrieve everything for an encounter for efficient display). The server SHOULD return all resources it has that: * are included in the encounter compartment for the identified encounter (have a reference to the encounter) * are referenced by the standard extenstion for associating an encounter (where no reference element exists) http://hl7.org/fhir/StructureDefinition/encounter-associatedEncounter * the server believes are relevant to the context of the encounter for any other reason (internally defined/decided) * any resource referenced by the above, including binaries and attachments (to make a more complete package) Implementation guides may make additional rules about how much information that is returned. Note that for many resources, the exact nature of the link to encounter can be ambiguous (e.g. for a DiagnosticReport, is it the encounter when it was initiated, or when it was reported?)

This operation is used to return all the information related to an episodeofcare described in the resource on which this operation is invoked. The response is a bundle of type "searchset". At a minimum, the episodeofcare resource itself is returned, along with any other resources that the server has available for the given episodeofcare for the user. The server also returns whatever resources are needed to support the records - e.g. linked practitioners, locations, organizations etc. The principle intended use for this operation is to provide a patient with access to their record, or to allow a client to retrieve everything for an episodeofcare for efficient display). The server SHOULD return all resources it has that: * are included in the episodeofcare compartment for the identified episodeofcare (have a reference to the episodeofcare) * are referenced by the standard extension for associating an episodeofcare (where no reference element exists) http://hl7.org/fhir/StructureDefinition/workflow-episodeOfCare * the server believes are relevant to the context of the episodeofcare for any other reason (internally defined/decided) * any resource referenced by the above, including binaries and attachments (to make a more complete package)

This operation is used to return all the information related to one or more patients described in the resource or context on which this operation is invoked. The response is a bundle of type "searchset". At a minimum, the patient resource(s) itself is returned, along with any other resources that the server has that are related to the patient(s), and that are available for the given user. The server also returns whatever resources are needed to support the records - e.g. linked practitioners, medications, locations, organizations etc. The intended use for this operation is to provide a patient with access to their entire record (e.g. "Blue Button"), or for provider or other user to perform a bulk data download. The server SHOULD return at least all resources that it has that are in the patient compartment for the identified patient(s), and any resource referenced from those, including binaries and attachments. The server SHOULD resolve version-specific references by returning the explicitly named version. Implementation guides may make additional rules about how much information that is returned.

The merge operation is used to request two patient resources be merged. One of the two patients is identified as the source and one as the target. The data from the source patient will be merged with the data of the target patient. The source Patient resource will be updated to add a new Patient.link reference to the target Patient resource with a link-type of replaced-by. The source Patient will also be updated to have a status of inactive, unless the source Patient resource was deleted. The target Patient resource will be updated to add a new Patient.link reference to the source Patient resource with a link-type of replaces unless the source Patient resource is deleted. The target Patient resource must be included in the result-patient parameter if used.

Account to place this charge

A code that identifies the charge, like a billing code

Candidate account for charge items

A quantity- or range-valued use context assigned to the charge item definition

A use context type and quantity- or range-based value assigned to the charge item definition

A use context type and value assigned to the charge item definition

A type of use context assigned to the charge item definition

A use context assigned to the charge item definition

The charge item definition publication date

The description of the charge item definition

The time during which the charge item definition is intended to be in use

Whether the ChargeItemDefinition is experimental

External identifier for the charge item definition

Jurisdiction of the authority that maintains the the charge item definition

Name of the publisher of the charge item definition

The current status of the charge item definition

The human-friendly name of the charge item definition

The uri that identifies the charge item definition

The business version of the charge item definition

Encounter associated with event

Date the charge item was entered

Individual who was entering

Factor overriding the associated rules

Business Identifier for item

When the charged service was applied

Individual service was done for/to

Individual who was performing

What type of performance was done

Organization providing the charged service

Price overriding the associated rules

Quantity of which the charge item has been serviced

Organization requesting the charged service

Which rendered service is being charged?

Is this charge item active

Individual service was done for/to

The Encounter associated with this set of history values

Identifier(s) by which this encounter is known

The patient present at the encounter

Status of the Encounter history entry

The patient or group present at the encounter

Location(s) insurance product is intended for/available to

External identifiers for this item

The product this plan is available to

The product this plan is available to

A code for the type of insurance plan

Product administrator

A city specified in an address

A country specified in an address

A postal code specified in an address

A state specified in an address

A use code specified in an address

A server defined search that may match any of the string fields in the Address, including line, city, district, state, country, postalCode, and/or text

Technical endpoint

Any identifier for the product (not the accreditation issuer's identifier)

A portion of the insurance product's name or alias

The issuer of the insurance product

A portion of the product's name using some kind of phonetic matching algorithm

Is the Product record active

A code for the type of insurance product

The patient this related person is related to

The personal relationship between the patient and the PersonalRelationship

The source of the relationship

The target of the relationship

Select validation information for data that was attested to using the specified method

Select validation information for data that was attested to on behalf of the specified source

Select validation information for data that was attested to by the specified source

Select validation information for data that was validated against a primary source on the specified date

Select validation information for data that was validated against the specified type of primary source organization

Select validation information for data that was validated against the specified primary source

Select validation information with a validation status that occurred at the specified date/time

Select validation information with the specified status

A resource that was validated

Select validation information for data that was validated by the specified organization

The resource ChargeItem describes the provision of healthcare provider products for a certain patient, therefore referring not only to the product, but containing in addition details of the provision, like date, time, amounts and participating organizations and persons. Main Usage of the ChargeItem is to enable the billing process and internal cost allocation.

The ChargeItemDefinition resource provides the properties that apply to the (billing) codes necessary to calculate costs and prices. The properties may differ largely depending on type and realm, therefore this resource gives only a rough structure and requires profiling for each type of billing code system.

A record of significant events/milestones key data throughout the history of an Encounter

Details of a Health Insurance plan provided by an organization under an InsuranceProduct.

Details of a Health Insurance product provided by an organization.

Details about the relationship between 2 individuals.

Describes validation requirements, source(s), status and dates for one or more elements.

Whether the cost applies to in-network or out-of-network providers.

Whether the cost applies to in-network or out-of-network providers.

Example set of codes that can be used for billing purposes.

Codes identifying the lifecycle stage of a ChargeItem.

This example value set defines a set of codes that can be used to indicate a type of insurance plan.

This example value set defines a set of codes that can be used to indicate a type of insurance plan.

Codes indicating the kind of the price component.

A set of codes that can be used to indicate the relationship between a PersonalRelationship's focus and target.

The validation status of the target

Attested information may be validated by process that are manual or automated. For automated processes it may accomplished by the system of record reaching out through another system's API or information may be sent to the system of record. This value set defines a set of codes to describing the process, the how, a resource or data element is validated.

Ability of the primary source to push updates/alerts

The result if validation fails

The frequency with which the target must be validated

Type of the validation primary source

Type of alerts/updates the primary source can send

The primary process by which the target is validated

Status of the validation of the target against the primary source

What the target is validated against

Codes identifying the lifecycle stage of a ChargeItem.

Codes indicating the kind of the price component.

The validation status of the target

Financial details for custom made device

Allergologisch-diagnostischer Komplex zur Diagnostik und/oder zum Ausschluss einer (Kontakt-)Allergie vom Spättyp (Typ IV), einschl. Kosten

Allergologisch-diagnostischer Komplex zur Diagnostik und/oder zum Ausschluss einer (Kontakt-)Allergie vom Spättyp (Typ IV), einschl. Kosten