API documentation for HeyDonto API users
curl -i -X GET \ 'https://docs.heydonto.com/_mock/apis/fhir/openapi/fhir/charge-item?_count=0&_page_token=string' \ -H 'Authorization: Bearer <YOUR_JWT_HERE>'
Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
Indicates the purpose of this bundle - how it is intended to be used.
An instant in time - known at least to the second
A series of links that provide context to this bundle.
An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).
A signature along with supporting context. The signature may be a digital signature that is cryptographic in nature, or some other signature acceptable to the domain. This other signature may be as simple as a graphical image representing a hand-written signature, or a signature ceremony Different signature approaches have different utilities.
{ "resourceType": "Bundle", "type": "searchset", "total": 100, "link": [ { … }, { … }, { … }, { … } ], "entry": [ { … } ] }
Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
A human-readable summary of the resource conveying the essential clinical and business information for the resource.
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.
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.
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).
Identifiers assigned to this event performer or other systems.
References the (external) source of pricing information, rules of application for the code this ChargeItem uses.
References the source of pricing information, rules of application for the code this ChargeItem uses.
The current state of the ChargeItem.
ChargeItems can be grouped to larger ChargeItems covering the whole set.
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
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.
A reference from one resource to another.
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.
Date/time(s) or duration when the charged service was applied.
Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.
Indicates who or what performed or participated in the charged service.
A measured amount (or an amount that can potentially be measured). Note that measured amounts include amounts that are not precisely quantified, including amounts involving arbitrary units and floating currencies.
The anatomical location where the related service has been applied.
A rational number with implicit precision
A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
Describes why the event occurred in coded or textual form.
Indicated the rendered service that caused this charge.
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
Account into which this ChargeItems belongs.
Comments made about the event by the performer, subject or other participants.
curl -i -X POST \ https://docs.heydonto.com/_mock/apis/fhir/openapi/fhir/charge-item \ -H 'Authorization: Bearer <YOUR_JWT_HERE>' \ -H 'Content-Type: application/json' \ -d '{ "resourceType": "ChargeItem", "id": "example", "text": { "status": "generated", "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">Example of ChargeItem Usage in Context of the German EBM Billing code system</div>" }, "identifier": [ { "system": "http://myHospital.org/ChargeItems", "value": "654321" } ], "definitionUri": [ "http://www.kbv.de/tools/ebm/html/01520_2904360860826220813632.html" ], "status": "billable", "code": { "coding": [ { "code": "01510", "display": "Zusatzpauschale für Beobachtung nach diagnostischer Koronarangiografie" } ] }, "subject": { "reference": "Patient/example" }, "context": { "reference": "Encounter/example" }, "occurrencePeriod": { "start": "2017-01-25T08:00:00+01:00", "end": "2017-01-25T12:35:00+01:00" }, "performer": [ { "function": { "coding": [ { "system": "http://snomed.info/sct", "code": "17561000", "display": "Cardiologist" } ] }, "actor": { "reference": "Practitioner/example" } }, { "function": { "coding": [ { "system": "http://snomed.info/sct", "code": "224542009", "display": "Coronary Care Nurse" } ] }, "actor": { "reference": "Practitioner/example" } } ], "performingOrganization": { "identifier": { "system": "http://myhospital/NamingSystem/departments", "value": "CARD_INTERMEDIATE_CARE" } }, "requestingOrganization": { "identifier": { "system": "http://myhospital/NamingSystem/departments", "value": "CARD_U1" } }, "quantity": { "value": 1 }, "factorOverride": 0.8, "priceOverride": { "value": 40, "currency": "EUR" }, "overrideReason": "Patient is Cardiologist'\''s golf buddy, so he gets a 20% discount!", "enterer": { "reference": "Practitioner/example" }, "enteredDate": "2017-01-25T23:55:04+01:00", "reason": [ { "coding": [ { "system": "http://hl7.org/fhir/sid/icd-10", "code": "123456", "display": "DIAG-1" } ] } ], "service": [ { "reference": "Procedure/example" } ], "account": [ { "reference": "Account/example" } ], "note": [ { "authorReference": { "reference": "Practitioner/example" }, "time": "2017-01-25T23:55:04+01:00", "text": "The code is only applicable for periods longer than 4h" } ] }'
Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
A human-readable summary of the resource conveying the essential clinical and business information for the resource.
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.
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.
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).
Identifiers assigned to this event performer or other systems.
References the (external) source of pricing information, rules of application for the code this ChargeItem uses.
References the source of pricing information, rules of application for the code this ChargeItem uses.
The current state of the ChargeItem.
ChargeItems can be grouped to larger ChargeItems covering the whole set.
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
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.
A reference from one resource to another.
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.
Date/time(s) or duration when the charged service was applied.
Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.
Indicates who or what performed or participated in the charged service.
A measured amount (or an amount that can potentially be measured). Note that measured amounts include amounts that are not precisely quantified, including amounts involving arbitrary units and floating currencies.
The anatomical location where the related service has been applied.
A rational number with implicit precision
A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
Describes why the event occurred in coded or textual form.
Indicated the rendered service that caused this charge.
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
Account into which this ChargeItems belongs.
Comments made about the event by the performer, subject or other participants.
{ "resourceType": "ChargeItem", "id": "example", "text": { "status": "generated", "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">Example of ChargeItem Usage in Context of the German EBM Billing code system</div>" }, "identifier": [ { … } ], "definitionUri": [ "http://www.kbv.de/tools/ebm/html/01520_2904360860826220813632.html" ], "status": "billable", "code": { "coding": [ … ] }, "subject": { "reference": "Patient/example" }, "context": { "reference": "Encounter/example" }, "occurrencePeriod": { "start": "2017-01-25T08:00:00+01:00", "end": "2017-01-25T12:35:00+01:00" }, "performer": [ { … }, { … } ], "performingOrganization": { "identifier": { … } }, "requestingOrganization": { "identifier": { … } }, "quantity": { "value": 1 }, "factorOverride": 0.8, "priceOverride": { "value": 40, "currency": "EUR" }, "overrideReason": "Patient is Cardiologist's golf buddy, so he gets a 20% discount!", "enterer": { "reference": "Practitioner/example" }, "enteredDate": "2017-01-25T23:55:04+01:00", "reason": [ { … } ], "service": [ { … } ], "account": [ { … } ], "note": [ { … } ] }
curl -i -X GET \ 'https://docs.heydonto.com/_mock/apis/fhir/openapi/fhir/charge-item/{id}' \ -H 'Authorization: Bearer <YOUR_JWT_HERE>'
Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
A human-readable summary of the resource conveying the essential clinical and business information for the resource.
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.
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.
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).
Identifiers assigned to this event performer or other systems.
References the (external) source of pricing information, rules of application for the code this ChargeItem uses.
References the source of pricing information, rules of application for the code this ChargeItem uses.
The current state of the ChargeItem.
ChargeItems can be grouped to larger ChargeItems covering the whole set.
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
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.
A reference from one resource to another.
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.
Date/time(s) or duration when the charged service was applied.
Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.
Indicates who or what performed or participated in the charged service.
A measured amount (or an amount that can potentially be measured). Note that measured amounts include amounts that are not precisely quantified, including amounts involving arbitrary units and floating currencies.
The anatomical location where the related service has been applied.
A rational number with implicit precision
A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
Describes why the event occurred in coded or textual form.
Indicated the rendered service that caused this charge.
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
Account into which this ChargeItems belongs.
Comments made about the event by the performer, subject or other participants.
{ "resourceType": "ChargeItem", "id": "example", "text": { "status": "generated", "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">Example of ChargeItem Usage in Context of the German EBM Billing code system</div>" }, "identifier": [ { … } ], "definitionUri": [ "http://www.kbv.de/tools/ebm/html/01520_2904360860826220813632.html" ], "status": "billable", "code": { "coding": [ … ] }, "subject": { "reference": "Patient/example" }, "context": { "reference": "Encounter/example" }, "occurrencePeriod": { "start": "2017-01-25T08:00:00+01:00", "end": "2017-01-25T12:35:00+01:00" }, "performer": [ { … }, { … } ], "performingOrganization": { "identifier": { … } }, "requestingOrganization": { "identifier": { … } }, "quantity": { "value": 1 }, "factorOverride": 0.8, "priceOverride": { "value": 40, "currency": "EUR" }, "overrideReason": "Patient is Cardiologist's golf buddy, so he gets a 20% discount!", "enterer": { "reference": "Practitioner/example" }, "enteredDate": "2017-01-25T23:55:04+01:00", "reason": [ { … } ], "service": [ { … } ], "account": [ { … } ], "note": [ { … } ] }
Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
A human-readable summary of the resource conveying the essential clinical and business information for the resource.
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.
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.
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).
Identifiers assigned to this event performer or other systems.
References the (external) source of pricing information, rules of application for the code this ChargeItem uses.
References the source of pricing information, rules of application for the code this ChargeItem uses.
The current state of the ChargeItem.
ChargeItems can be grouped to larger ChargeItems covering the whole set.
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
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.
A reference from one resource to another.
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.
Date/time(s) or duration when the charged service was applied.
Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.
Indicates who or what performed or participated in the charged service.
A measured amount (or an amount that can potentially be measured). Note that measured amounts include amounts that are not precisely quantified, including amounts involving arbitrary units and floating currencies.
The anatomical location where the related service has been applied.
A rational number with implicit precision
A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
Describes why the event occurred in coded or textual form.
Indicated the rendered service that caused this charge.
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
Account into which this ChargeItems belongs.
Comments made about the event by the performer, subject or other participants.
curl -i -X PUT \ 'https://docs.heydonto.com/_mock/apis/fhir/openapi/fhir/charge-item/{id}' \ -H 'Authorization: Bearer <YOUR_JWT_HERE>' \ -H 'Content-Type: application/json' \ -d '{ "resourceType": "ChargeItem", "id": "example", "text": { "status": "generated", "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">Example of ChargeItem Usage in Context of the German EBM Billing code system</div>" }, "identifier": [ { "system": "http://myHospital.org/ChargeItems", "value": "654321" } ], "definitionUri": [ "http://www.kbv.de/tools/ebm/html/01520_2904360860826220813632.html" ], "status": "billable", "code": { "coding": [ { "code": "01510", "display": "Zusatzpauschale für Beobachtung nach diagnostischer Koronarangiografie" } ] }, "subject": { "reference": "Patient/example" }, "context": { "reference": "Encounter/example" }, "occurrencePeriod": { "start": "2017-01-25T08:00:00+01:00", "end": "2017-01-25T12:35:00+01:00" }, "performer": [ { "function": { "coding": [ { "system": "http://snomed.info/sct", "code": "17561000", "display": "Cardiologist" } ] }, "actor": { "reference": "Practitioner/example" } }, { "function": { "coding": [ { "system": "http://snomed.info/sct", "code": "224542009", "display": "Coronary Care Nurse" } ] }, "actor": { "reference": "Practitioner/example" } } ], "performingOrganization": { "identifier": { "system": "http://myhospital/NamingSystem/departments", "value": "CARD_INTERMEDIATE_CARE" } }, "requestingOrganization": { "identifier": { "system": "http://myhospital/NamingSystem/departments", "value": "CARD_U1" } }, "quantity": { "value": 1 }, "factorOverride": 0.8, "priceOverride": { "value": 40, "currency": "EUR" }, "overrideReason": "Patient is Cardiologist'\''s golf buddy, so he gets a 20% discount!", "enterer": { "reference": "Practitioner/example" }, "enteredDate": "2017-01-25T23:55:04+01:00", "reason": [ { "coding": [ { "system": "http://hl7.org/fhir/sid/icd-10", "code": "123456", "display": "DIAG-1" } ] } ], "service": [ { "reference": "Procedure/example" } ], "account": [ { "reference": "Account/example" } ], "note": [ { "authorReference": { "reference": "Practitioner/example" }, "time": "2017-01-25T23:55:04+01:00", "text": "The code is only applicable for periods longer than 4h" } ] }'
Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
A human-readable summary of the resource conveying the essential clinical and business information for the resource.
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.
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.
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).
Identifiers assigned to this event performer or other systems.
References the (external) source of pricing information, rules of application for the code this ChargeItem uses.
References the source of pricing information, rules of application for the code this ChargeItem uses.
The current state of the ChargeItem.
ChargeItems can be grouped to larger ChargeItems covering the whole set.
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
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.
A reference from one resource to another.
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.
Date/time(s) or duration when the charged service was applied.
Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.
Indicates who or what performed or participated in the charged service.
A measured amount (or an amount that can potentially be measured). Note that measured amounts include amounts that are not precisely quantified, including amounts involving arbitrary units and floating currencies.
The anatomical location where the related service has been applied.
A rational number with implicit precision
A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
Describes why the event occurred in coded or textual form.
Indicated the rendered service that caused this charge.
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
Account into which this ChargeItems belongs.
Comments made about the event by the performer, subject or other participants.
{ "resourceType": "ChargeItem", "id": "example", "text": { "status": "generated", "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">Example of ChargeItem Usage in Context of the German EBM Billing code system</div>" }, "identifier": [ { … } ], "definitionUri": [ "http://www.kbv.de/tools/ebm/html/01520_2904360860826220813632.html" ], "status": "billable", "code": { "coding": [ … ] }, "subject": { "reference": "Patient/example" }, "context": { "reference": "Encounter/example" }, "occurrencePeriod": { "start": "2017-01-25T08:00:00+01:00", "end": "2017-01-25T12:35:00+01:00" }, "performer": [ { … }, { … } ], "performingOrganization": { "identifier": { … } }, "requestingOrganization": { "identifier": { … } }, "quantity": { "value": 1 }, "factorOverride": 0.8, "priceOverride": { "value": 40, "currency": "EUR" }, "overrideReason": "Patient is Cardiologist's golf buddy, so he gets a 20% discount!", "enterer": { "reference": "Practitioner/example" }, "enteredDate": "2017-01-25T23:55:04+01:00", "reason": [ { … } ], "service": [ { … } ], "account": [ { … } ], "note": [ { … } ] }
curl -i -X DELETE \ 'https://docs.heydonto.com/_mock/apis/fhir/openapi/fhir/charge-item/{id}' \ -H 'Authorization: Bearer <YOUR_JWT_HERE>'
{ "statusText": "OK", "status": 200 }
curl -i -X GET \ 'https://docs.heydonto.com/_mock/apis/fhir/openapi/fhir/charge-item/{id}/history' \ -H 'Authorization: Bearer <YOUR_JWT_HERE>'
A list of entries representing historical versions of the resource.
{ "resourceType": "Bundle", "type": "history", "entry": [ { … } ], "total": 2 }