The medical aid used to help the patient hear.

This is a specialization of the zib-MedicalDevice profile to represent HearingAid devices within the context of zib HearingFunction.

Please note that on a functional level, zib HearingFunction references zib MedicalDevice, but in FHIR this direction is reversed.

The anatomical location of the hearing aid, such as: ‘left ear’.

The medical aid used to help the patient hear.

A record of a device being used by a patient where the record is the result of a report from the patient or another clinician.

This is a specialization of the zib-MedicalDevice profile to represent HearingAid devices within the context of zib HearingFunction.

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.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

An Extension

An Extension

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

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

A code representing the patient or other source's judgment about the state of the device used that this statement is about. Generally this will be active or completed.

This element is implictly mapped to the zib concepts NL-CM:10.1.11 (StartDate) and NL-CM:10.1.14 (EndDate). Unless the status is explicitly recorded, the following guidance applies:

• When StartDate is in the future, .status will usually be set to intended.
• When StartDate is in the past and EndDate has a value and in the future or EndDate has no value, .status will usually be set to active.
• When EndDate has a value and is in the past, .status will usually be set to completed.

DeviceUseStatment is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for contains codes that assert the status of the use by the patient (for example, stopped or on hold) as well as codes that assert the status of the resource itself (for example, entered in error).

This element is labeled as a modifier because the status contains the codes that mark the statement as not currently valid.

A coded concept indicating the current status of the Device Usage.

The patient who used the device.

Allows linking the DeviceUseStatement to the underlying Request, or to other information that supports or is used to derive the DeviceUseStatement.

The most common use cases for deriving a DeviceUseStatement comes from creating it from a request or from an observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the DeviceUseStatement from.

• profile @ resolve()

The procedure which has the purpose of placing this product in or on the body.

Allows linking the DeviceUseStatement to the underlying Request, or to other information that supports or is used to derive the DeviceUseStatement.

• Note 1: on a functional level, zib Procedure references zib MedicalDevice, but in FHIR this direction is reversed.
• Note 2: zib Procedure can represent a requested or (to be) performed procedure. This slice represents requested procedures, while slice procedure-event represents performed procedures.

The most common use cases for deriving a DeviceUseStatement comes from creating it from a request or from an observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the DeviceUseStatement from.

The procedure which has the purpose of placing this product in or on the body.

Allows linking the DeviceUseStatement to the underlying Request, or to other information that supports or is used to derive the DeviceUseStatement.

• Note 1: on a functional level, zib Procedure references zib MedicalDevice, but in FHIR this direction is reversed.
• Note 2: zib Procedure can represent a requested or (to be) performed procedure. This slice represents performed procedures, while slice procedure-request represents requested procedures.

The most common use cases for deriving a DeviceUseStatement comes from creating it from a request or from an observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the DeviceUseStatement from.

How often the device was used.

• type @ $this

How often the device was used.

The details of the device used.

Indicates another resource whose existence justifies this DeviceUseStatement.

• profile @ resolve()

The medical reason for use of the medical device.

Indicates another resource whose existence justifies this DeviceUseStatement.

Indicates another resource whose existence justifies this DeviceUseStatement.

Please note that on a functional level, zib BowelFunction references zib MedicalDevice, but in FHIR this direction is reversed.

Indicates another resource whose existence justifies this DeviceUseStatement.

Please note that on a functional level, zib FunctionalOrMentalStatus references zib MedicalDevice, but in FHIR this direction is reversed.

Indicates another resource whose existence justifies this DeviceUseStatement.

Please note that on a functional level, zib Mobility references zib MedicalDevice, but in FHIR this direction is reversed.

Indicates another resource whose existence justifies this DeviceUseStatement.

Please note that on a functional level, zib Stoma references zib MedicalDevice, but in FHIR this direction is reversed.

Indicates another resource whose existence justifies this DeviceUseStatement.

Please note that on a functional level, zib HearingFunction references zib MedicalDevice, but in FHIR this direction is reversed.

The anatomical location of the hearing aid, such as: ‘left ear’.

Indicates the anotomic location on the subject's body where the device was used ( i.e. the target).

Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.

Knowing where the device is targeted is important for tracking if multiple sites are possible. If more information than just a code is required, use the extension http://hl7.org/fhir/StructureDefinition/bodySite.

Details about the device statement that were not represented at all or sufficiently in one of the attributes provided in a class. These may include for example a comment, an instruction, or a note associated with the statement.

Comment about use or information on the medical device used.

The text of the annotation in markdown format.

The medical aid used to help the patient hear.

This is a specialization of the zib-MedicalDevice profile to represent HearingAid devices within the context of zib HearingFunction.

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

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

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.

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.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

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.

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

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.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

An Extension

• value @ url

An Extension

An Extension

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.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

An external identifier for this statement such as an IRI.

A plan, proposal or order that is fulfilled in whole or in part by this DeviceUseStatement.

Allows tracing of authorization for the DeviceUseStatement and tracking whether proposals/recommendations were acted upon.

A code representing the patient or other source's judgment about the state of the device used that this statement is about. Generally this will be active or completed.

This element is implictly mapped to the zib concepts NL-CM:10.1.11 (StartDate) and NL-CM:10.1.14 (EndDate). Unless the status is explicitly recorded, the following guidance applies:

The patient who used the device.

Allows linking the DeviceUseStatement to the underlying Request, or to other information that supports or is used to derive the DeviceUseStatement.

The most common use cases for deriving a DeviceUseStatement comes from creating it from a request or from an observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the DeviceUseStatement from.

• profile @ resolve()

The procedure which has the purpose of placing this product in or on the body.

• Note 1: on a functional level, zib Procedure references zib MedicalDevice, but in FHIR this direction is reversed.
• Note 2: zib Procedure can represent a requested or (to be) performed procedure. This slice represents requested procedures, while slice procedure-event represents performed procedures.

The procedure which has the purpose of placing this product in or on the body.

• Note 1: on a functional level, zib Procedure references zib MedicalDevice, but in FHIR this direction is reversed.
• Note 2: zib Procedure can represent a requested or (to be) performed procedure. This slice represents performed procedures, while slice procedure-request represents requested procedures.

How often the device was used.

• type @ $this

How often the device was used.

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

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

• value @ url

The start date of the first use or implant of the medical device. A ‘vague’ date, such as only the year, is permitted.

If the low element is missing, the meaning is that the low boundary is not known.

The end date of the last use or explant of the medical device. A ‘vague’ date, such as only the year, is permitted.

The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.

The time at which the statement was made/recorded.

Who reported the device was being used by the patient.

The details of the device used.

Reason or justification for the use of the device.

Indicates another resource whose existence justifies this DeviceUseStatement.

• profile @ resolve()

The medical reason for use of the medical device.

Indicates another resource whose existence justifies this DeviceUseStatement.

Please note that on a functional level, zib BowelFunction references zib MedicalDevice, but in FHIR this direction is reversed.

Indicates another resource whose existence justifies this DeviceUseStatement.

Please note that on a functional level, zib FunctionalOrMentalStatus references zib MedicalDevice, but in FHIR this direction is reversed.

Indicates another resource whose existence justifies this DeviceUseStatement.

Please note that on a functional level, zib Mobility references zib MedicalDevice, but in FHIR this direction is reversed.

Indicates another resource whose existence justifies this DeviceUseStatement.

Please note that on a functional level, zib Stoma references zib MedicalDevice, but in FHIR this direction is reversed.

Indicates another resource whose existence justifies this DeviceUseStatement.

Please note that on a functional level, zib HearingFunction references zib MedicalDevice, but in FHIR this direction is reversed.

The anatomical location of the hearing aid, such as: ‘left ear’.

Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.

Knowing where the device is targeted is important for tracking if multiple sites are possible. If more information than just a code is required, use the extension http://hl7.org/fhir/StructureDefinition/bodySite.

Details about the device statement that were not represented at all or sufficiently in one of the attributes provided in a class. These may include for example a comment, an instruction, or a note associated with the statement.

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

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

• value @ url

The individual responsible for making the annotation.

Organization is used when there's no need for specific attribution as to who made the comment.

Indicates when this particular annotation was made.

Comment about use or information on the medical device used.