Site identifier
HeyDonto FHIR R4 API - Clinical (1.0)
This Clinical Module focuses on the FHIR Resources that represent core clinical information for a patient. The information contained in these Resources are those frequently documented, created or retrieved by healthcare providers during the course of clinical care. Resources generated during the course of diagnostic studies can be found in the Diagnostics Module, whereas the Resources related to medication ordering and administration process can be found in the Medications Module.
As an introduction to FHIR APIs and Resources, please see the Developer's Introduction or Clinical Introduction in the Overview section of the Foundation Module.
The Clinical Module covers the following resources:
- AllergyIntolerance - Risk of harmful or undesirable, physiological response which is unique to an individual and associated with exposure to a substance
- Condition (Problem) - A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern
- Procedure - An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy
- FamilyMemberHistory - Significant health conditions for a person related to the patient relevant in the context of care for the patient
- CarePlan - Describes the intention of how one or more practitioners intend to deliver care for a particular patient, group or community for a period of time, possibly limited to care for a specific condition or set of conditions
- Goal - Describes the intended objective(s) for a patient, group or organization care, for example, weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, etc.
- CareTeam - The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient
- ClinicalImpression - A record of a clinical assessment performed to determine what problem(s) may affect the patient and before planning the treatments or management strategies that are best to manage a patient's condition. Assessments are often 1:1 with a clinical consultation / encounter, but this varies greatly depending on the clinical workflow
- AdverseEvent - Actual or potential/avoided event causing unintended physical injury resulting from or contributed to by medical care, a research study or other healthcare setting factors that requires additional monitoring, treatment, or hospitalization, or that results in death
- DetectedIssue - Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, Ineffective treatment frequency, Procedure-condition conflict, etc.
- RiskAssessment - An assessment of the likely outcome(s) for a patient or other subject as well as the likelihood of each outcome
FHIR Resources have a low, moderate or high levels of complexity with respect to the number of primary and child elements as well as the number of referenced Resources, found in this module and others. To better understand the relationships between Resources, we recommend beginning with the lower complexity, core Resources such as Patient, Condition, and FamilyMemberHistory before addressing a high complexity Resource such as CarePlan.
The clinical resources often represent patient-related data, and as such are susceptible to data breaching. Necessary privacy and security provision must be in place for searching and fetching this information. For more general considerations, see the Security and Privacy module.
Documenting a patient's condition - The Condition Resource is used extensively throughout FHIR Resources to associate information and activities with specific conditions. The Condition Resource is broadly defined to include problems, diagnoses and health concerns.
Retrieving the patient's problems
Documenting and retrieving the patient's allergies - The AllergyIntolerance Resource is used to represent the patient's allergy or intolerance to a substance. There is vibrant debate within clinical community regarding what is appropriate to document as an allergy or intolerance. These terms are used both formally by the Allergy and Immunology community as well as informally by patients leading to confusion. Readers are referred to the Resource definition for the Scope and Usage of this resource. The AllergyIntolerance Resource also supports the documenting of the absence of an allergy.
Family History - The FamilyMemberHistory Resource can be used to document known conditions of family members and support the creation of pedigrees.
Care Plans - The CarePlan resource supports a problem based care plan with references to other Resources including CareTeam, Condition, Goal, and activities such as ServiceRequest.
Over the next 18 months, we will continue to advance the resources through the Maturity Levels through the process of development and testing of the Resources. We anticipate more widespread implementation of core Resources such as Condition. Complex Resources such as CarePlan are dependent on the maturation of its referred Resources and are expected to mature more gradually. The clinical community will need to develop use cases to test and further mature the ServiceRequest Resource at opportunities such as the Clinicians on FHIR sessions at the HL7 Working Group Meetings.
https://docs.heydonto.com/_mock/apis/fhir/clinical/
https://api-staging.heydonto.com/
https://api.heydonto.com/
Sort the results by a given field, e.g. _sort=family or _sort=-date.
Restrict returned fields, e.g. _elements=identifier,name.
Filter by resource telecom, e.g. date=[SYSTEM]|[VALUE].
Search for resources by identifier token, e.g. identifier=http://hospital.org|12345.
Include related patient resources, e.g. patient=Patient/[id]&.
Reverse chaining, e.g. _has:Observation:subject:code=http://loinc.org|1234-5.
Search by tag on the resource meta, e.g. _tag=http://example.org/tags|sample-tag.
Search by security label on resource meta, e.g. _security=RBAC|CONFIDENTIAL.
- Mock server
https://docs.heydonto.com/_mock/apis/fhir/clinical/site/{siteId}/fhir/composition
- Sandbox
https://api-staging.heydonto.com/site/{siteId}/fhir/composition
- Production
https://api.heydonto.com/site/{siteId}/fhir/composition
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://docs.heydonto.com/_mock/apis/fhir/clinical/site/{siteId}/fhir/composition?_count=10&_page_token=CgYK...&_sort=family&_elements=identifier%2Cname&telecom=telecom%3Dphone%2C555-555-5555&_id=abc123&identifier=http%3A%2F%2Fhospital.org%2C12345&_include=string&patient=patient%3DPatient%2F%5Bid%5D%26&_revinclude=string&_has=Observation%3Asubject%3Acode%3Dhttp%3A%2F%2Floinc.org%2C1234-5&_tag=http%3A%2F%2Fexample.org%2Ftags%2Csample-tag&_security=RBAC%2CCONFIDENTIAL&_profile=http%3A%2F%2Fexample.org%2Ffhir%2FStructureDefinition%2Fcustom-profile' \
-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.
String of characters used to identify a name or a 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
An integer with a value that is not negative (e.g. >= 0)
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.
String of characters used to identify a name or a 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).
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document.
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 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.
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.
Identifies who is responsible for the information in the composition, not necessarily who typed it in.
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 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 participant who has attested to the accuracy of the composition/document.
Relationships that this composition has with other compositions or documents that already exist.
The clinical service, such as a colonoscopy or an appendectomy, being documented.
The root of the sections that make up the composition.
- Mock server
https://docs.heydonto.com/_mock/apis/fhir/clinical/site/{siteId}/fhir/composition
- Sandbox
https://api-staging.heydonto.com/site/{siteId}/fhir/composition
- Production
https://api.heydonto.com/site/{siteId}/fhir/composition
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
'https://docs.heydonto.com/_mock/apis/fhir/clinical/site/{siteId}/fhir/composition' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"resourceType": "Composition",
"id": "example",
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n\t\t\t<p>Consultation note for Henry Levin the 7th</p>\n\t\t\t<p>Managed by Good Health Clinic</p>\n\t\t</div>"
},
"identifier": {
"system": "http://healthintersections.com.au/test",
"value": "1"
},
"status": "final",
"type": {
"coding": [
{
"system": "http://loinc.org",
"code": "11488-4",
"display": "Consult note"
}
]
},
"category": [
{
"coding": [
{
"system": "http://loinc.org",
"code": "LP173421-1",
"display": "Report"
}
]
}
],
"subject": {
"reference": "Patient/xcda",
"display": "Henry Levin the 7th"
},
"encounter": {
"reference": "Encounter/xcda"
},
"date": "2012-01-04T09:10:14Z",
"author": [
{
"reference": "Practitioner/xcda-author",
"display": "Harold Hippocrates, MD"
}
],
"title": "Consultation Note",
"confidentiality": "N",
"attester": [
{
"mode": "legal",
"time": "2012-01-04T09:10:14Z",
"party": {
"reference": "Practitioner/xcda-author",
"display": "Harold Hippocrates, MD"
}
}
],
"custodian": {
"reference": "Organization/2.16.840.1.113883.19.5",
"display": "Good Health Clinic"
},
"relatesTo": [
{
"code": "replaces",
"targetReference": {
"reference": "Composition/old-example"
}
},
{
"code": "appends",
"targetIdentifier": {
"system": "http://example.org/fhir/NamingSystem/document-ids",
"value": "ABC123"
}
}
],
"event": [
{
"code": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
"code": "HEALTHREC",
"display": "health record"
}
]
}
],
"period": {
"start": "2010-07-18",
"end": "2012-11-12"
},
"detail": [
{
"reference": "Observation/example"
}
]
}
],
"section": [
{
"title": "History of present illness",
"code": {
"coding": [
{
"system": "http://loinc.org",
"code": "11348-0",
"display": "History of past illness Narrative"
}
]
},
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n\t\t\t\t<table>\n\t\t\t\t\t<tr>\n\t\t\t\t\t\t<td>\n\t\t\t\t\t\t\t<b>Code</b>\n\t\t\t\t\t\t</td>\n\t\t\t\t\t\t<td>\n\t\t\t\t\t\t\t<b>Date</b>\n\t\t\t\t\t\t</td>\n\t\t\t\t\t\t<td>\n\t\t\t\t\t\t\t<b>Type</b>\n\t\t\t\t\t\t</td>\n\t\t\t\t\t\t<td>\n\t\t\t\t\t\t\t<b>BodySite</b>\n\t\t\t\t\t\t</td>\n\t\t\t\t\t\t<td>\n\t\t\t\t\t\t\t<b>Severity</b>\n\t\t\t\t\t\t</td>\n\t\t\t\t\t</tr>\n\t\t\t\t\t<tr>\n\t\t\t\t\t\t<td>Stroke</td>\n\t\t\t\t\t\t<td>2010-07-18</td>\n\t\t\t\t\t\t<td>Diagnosis</td>\n\t\t\t\t\t\t<td/>\n\t\t\t\t\t\t<td/>\n\t\t\t\t\t</tr>\n\t\t\t\t\t<tr>\n\t\t\t\t\t\t<td>Burnt Ear</td>\n\t\t\t\t\t\t<td>2012-05-24</td>\n\t\t\t\t\t\t<td>Diagnosis</td>\n\t\t\t\t\t\t<td>Left Ear</td>\n\t\t\t\t\t\t<td/>\n\t\t\t\t\t</tr>\n\t\t\t\t\t<tr>\n\t\t\t\t\t\t<td>Asthma</td>\n\t\t\t\t\t\t<td>2012-11-12</td>\n\t\t\t\t\t\t<td>Finding</td>\n\t\t\t\t\t\t<td/>\n\t\t\t\t\t\t<td>Mild</td>\n\t\t\t\t\t</tr>\n\t\t\t\t</table>\n\t\t\t</div>"
},
"mode": "snapshot",
"orderedBy": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/list-order",
"code": "event-date",
"display": "Sorted by Event Date"
}
]
},
"entry": [
{
"reference": "Condition/stroke"
},
{
"reference": "Condition/example"
},
{
"reference": "Condition/example2"
}
]
},
{
"title": "History of family member diseases",
"code": {
"coding": [
{
"system": "http://loinc.org",
"code": "10157-6",
"display": "History of family member diseases Narrative"
}
]
},
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n\t\t\t\t<p>History of family member diseases - not available</p>\n\t\t\t</div>"
},
"mode": "snapshot",
"emptyReason": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/list-empty-reason",
"code": "withheld",
"display": "Information Withheld"
}
]
}
}
]
}'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.
String of characters used to identify a name or a 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).
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document.
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 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.
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.
Identifies who is responsible for the information in the composition, not necessarily who typed it in.
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 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 participant who has attested to the accuracy of the composition/document.
Relationships that this composition has with other compositions or documents that already exist.
The clinical service, such as a colonoscopy or an appendectomy, being documented.
The root of the sections that make up the composition.
{ "resourceType": "Composition", "id": "example", "text": { "status": "generated", "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n\t\t\t<p>Consultation note for Henry Levin the 7th</p>\n\t\t\t<p>Managed by Good Health Clinic</p>\n\t\t</div>" }, "identifier": { "system": "http://healthintersections.com.au/test", "value": "1" }, "status": "final", "type": { "coding": [ … ] }, "category": [ { … } ], "subject": { "reference": "Patient/xcda", "display": "Henry Levin the 7th" }, "encounter": { "reference": "Encounter/xcda" }, "date": "2012-01-04T09:10:14Z", "author": [ { … } ], "title": "Consultation Note", "confidentiality": "N", "attester": [ { … } ], "custodian": { "reference": "Organization/2.16.840.1.113883.19.5", "display": "Good Health Clinic" }, "relatesTo": [ { … }, { … } ], "event": [ { … } ], "section": [ { … }, { … } ] }
- Mock server
https://docs.heydonto.com/_mock/apis/fhir/clinical/site/{siteId}/fhir/composition/{id}
- Sandbox
https://api-staging.heydonto.com/site/{siteId}/fhir/composition/{id}
- Production
https://api.heydonto.com/site/{siteId}/fhir/composition/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://docs.heydonto.com/_mock/apis/fhir/clinical/site/{siteId}/fhir/composition/{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.
String of characters used to identify a name or a 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).
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document.
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 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.
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.
Identifies who is responsible for the information in the composition, not necessarily who typed it in.
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 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 participant who has attested to the accuracy of the composition/document.
Relationships that this composition has with other compositions or documents that already exist.
The clinical service, such as a colonoscopy or an appendectomy, being documented.
The root of the sections that make up the composition.
{ "resourceType": "Composition", "id": "example", "text": { "status": "generated", "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n\t\t\t<p>Consultation note for Henry Levin the 7th</p>\n\t\t\t<p>Managed by Good Health Clinic</p>\n\t\t</div>" }, "identifier": { "system": "http://healthintersections.com.au/test", "value": "1" }, "status": "final", "type": { "coding": [ … ] }, "category": [ { … } ], "subject": { "reference": "Patient/xcda", "display": "Henry Levin the 7th" }, "encounter": { "reference": "Encounter/xcda" }, "date": "2012-01-04T09:10:14Z", "author": [ { … } ], "title": "Consultation Note", "confidentiality": "N", "attester": [ { … } ], "custodian": { "reference": "Organization/2.16.840.1.113883.19.5", "display": "Good Health Clinic" }, "relatesTo": [ { … }, { … } ], "event": [ { … } ], "section": [ { … }, { … } ] }
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.
String of characters used to identify a name or a 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).
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document.
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 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.
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.
Identifies who is responsible for the information in the composition, not necessarily who typed it in.
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 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 participant who has attested to the accuracy of the composition/document.
Relationships that this composition has with other compositions or documents that already exist.
The clinical service, such as a colonoscopy or an appendectomy, being documented.
The root of the sections that make up the composition.
- Mock server
https://docs.heydonto.com/_mock/apis/fhir/clinical/site/{siteId}/fhir/composition/{id}
- Sandbox
https://api-staging.heydonto.com/site/{siteId}/fhir/composition/{id}
- Production
https://api.heydonto.com/site/{siteId}/fhir/composition/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X PUT \
'https://docs.heydonto.com/_mock/apis/fhir/clinical/site/{siteId}/fhir/composition/{id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"resourceType": "Composition",
"id": "example",
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n\t\t\t<p>Consultation note for Henry Levin the 7th</p>\n\t\t\t<p>Managed by Good Health Clinic</p>\n\t\t</div>"
},
"identifier": {
"system": "http://healthintersections.com.au/test",
"value": "1"
},
"status": "final",
"type": {
"coding": [
{
"system": "http://loinc.org",
"code": "11488-4",
"display": "Consult note"
}
]
},
"category": [
{
"coding": [
{
"system": "http://loinc.org",
"code": "LP173421-1",
"display": "Report"
}
]
}
],
"subject": {
"reference": "Patient/xcda",
"display": "Henry Levin the 7th"
},
"encounter": {
"reference": "Encounter/xcda"
},
"date": "2012-01-04T09:10:14Z",
"author": [
{
"reference": "Practitioner/xcda-author",
"display": "Harold Hippocrates, MD"
}
],
"title": "Consultation Note",
"confidentiality": "N",
"attester": [
{
"mode": "legal",
"time": "2012-01-04T09:10:14Z",
"party": {
"reference": "Practitioner/xcda-author",
"display": "Harold Hippocrates, MD"
}
}
],
"custodian": {
"reference": "Organization/2.16.840.1.113883.19.5",
"display": "Good Health Clinic"
},
"relatesTo": [
{
"code": "replaces",
"targetReference": {
"reference": "Composition/old-example"
}
},
{
"code": "appends",
"targetIdentifier": {
"system": "http://example.org/fhir/NamingSystem/document-ids",
"value": "ABC123"
}
}
],
"event": [
{
"code": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
"code": "HEALTHREC",
"display": "health record"
}
]
}
],
"period": {
"start": "2010-07-18",
"end": "2012-11-12"
},
"detail": [
{
"reference": "Observation/example"
}
]
}
],
"section": [
{
"title": "History of present illness",
"code": {
"coding": [
{
"system": "http://loinc.org",
"code": "11348-0",
"display": "History of past illness Narrative"
}
]
},
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n\t\t\t\t<table>\n\t\t\t\t\t<tr>\n\t\t\t\t\t\t<td>\n\t\t\t\t\t\t\t<b>Code</b>\n\t\t\t\t\t\t</td>\n\t\t\t\t\t\t<td>\n\t\t\t\t\t\t\t<b>Date</b>\n\t\t\t\t\t\t</td>\n\t\t\t\t\t\t<td>\n\t\t\t\t\t\t\t<b>Type</b>\n\t\t\t\t\t\t</td>\n\t\t\t\t\t\t<td>\n\t\t\t\t\t\t\t<b>BodySite</b>\n\t\t\t\t\t\t</td>\n\t\t\t\t\t\t<td>\n\t\t\t\t\t\t\t<b>Severity</b>\n\t\t\t\t\t\t</td>\n\t\t\t\t\t</tr>\n\t\t\t\t\t<tr>\n\t\t\t\t\t\t<td>Stroke</td>\n\t\t\t\t\t\t<td>2010-07-18</td>\n\t\t\t\t\t\t<td>Diagnosis</td>\n\t\t\t\t\t\t<td/>\n\t\t\t\t\t\t<td/>\n\t\t\t\t\t</tr>\n\t\t\t\t\t<tr>\n\t\t\t\t\t\t<td>Burnt Ear</td>\n\t\t\t\t\t\t<td>2012-05-24</td>\n\t\t\t\t\t\t<td>Diagnosis</td>\n\t\t\t\t\t\t<td>Left Ear</td>\n\t\t\t\t\t\t<td/>\n\t\t\t\t\t</tr>\n\t\t\t\t\t<tr>\n\t\t\t\t\t\t<td>Asthma</td>\n\t\t\t\t\t\t<td>2012-11-12</td>\n\t\t\t\t\t\t<td>Finding</td>\n\t\t\t\t\t\t<td/>\n\t\t\t\t\t\t<td>Mild</td>\n\t\t\t\t\t</tr>\n\t\t\t\t</table>\n\t\t\t</div>"
},
"mode": "snapshot",
"orderedBy": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/list-order",
"code": "event-date",
"display": "Sorted by Event Date"
}
]
},
"entry": [
{
"reference": "Condition/stroke"
},
{
"reference": "Condition/example"
},
{
"reference": "Condition/example2"
}
]
},
{
"title": "History of family member diseases",
"code": {
"coding": [
{
"system": "http://loinc.org",
"code": "10157-6",
"display": "History of family member diseases Narrative"
}
]
},
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n\t\t\t\t<p>History of family member diseases - not available</p>\n\t\t\t</div>"
},
"mode": "snapshot",
"emptyReason": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/list-empty-reason",
"code": "withheld",
"display": "Information Withheld"
}
]
}
}
]
}'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.
String of characters used to identify a name or a 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).
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document.
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 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.
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.
Identifies who is responsible for the information in the composition, not necessarily who typed it in.
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 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 participant who has attested to the accuracy of the composition/document.
Relationships that this composition has with other compositions or documents that already exist.
The clinical service, such as a colonoscopy or an appendectomy, being documented.
The root of the sections that make up the composition.
{ "resourceType": "Composition", "id": "example", "text": { "status": "generated", "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n\t\t\t<p>Consultation note for Henry Levin the 7th</p>\n\t\t\t<p>Managed by Good Health Clinic</p>\n\t\t</div>" }, "identifier": { "system": "http://healthintersections.com.au/test", "value": "1" }, "status": "final", "type": { "coding": [ … ] }, "category": [ { … } ], "subject": { "reference": "Patient/xcda", "display": "Henry Levin the 7th" }, "encounter": { "reference": "Encounter/xcda" }, "date": "2012-01-04T09:10:14Z", "author": [ { … } ], "title": "Consultation Note", "confidentiality": "N", "attester": [ { … } ], "custodian": { "reference": "Organization/2.16.840.1.113883.19.5", "display": "Good Health Clinic" }, "relatesTo": [ { … }, { … } ], "event": [ { … } ], "section": [ { … }, { … } ] }
- Mock server
https://docs.heydonto.com/_mock/apis/fhir/clinical/site/{siteId}/fhir/composition/{id}
- Sandbox
https://api-staging.heydonto.com/site/{siteId}/fhir/composition/{id}
- Production
https://api.heydonto.com/site/{siteId}/fhir/composition/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X DELETE \
'https://docs.heydonto.com/_mock/apis/fhir/clinical/site/{siteId}/fhir/composition/{id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'{ "statusText": "OK", "status": 200 }
- Mock server
https://docs.heydonto.com/_mock/apis/fhir/clinical/site/{siteId}/fhir/composition/{id}/history
- Sandbox
https://api-staging.heydonto.com/site/{siteId}/fhir/composition/{id}/history
- Production
https://api.heydonto.com/site/{siteId}/fhir/composition/{id}/history
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://docs.heydonto.com/_mock/apis/fhir/clinical/site/{siteId}/fhir/composition/{id}/history' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'{ "resourceType": "Bundle", "type": "history", "entry": [ { … } ], "total": 2 }