The Basic API provides foundational functionalities for healthcare developers, offering essential tools and protocols to establish seamless communication and integration between diverse components of clinical applications. By leveraging the Basic API, developers can build robust, interoperable solutions, fostering improved data exchange, system connectivity, and overall efficiency within the healthcare ecosystem.
Object Definition
{
"resourceType": "Basic",
"id": "referral",
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <p><b>Patient:</b>Roel</p>\n <p><b>Requestor:</b>Dokter Bronsig</p>\n <p><b>Type:</b>Consultation</p>\n <p><b>Target Date:</b>April 1 - April 31</p>\n <p>COMPLETED</p>\n <b>The patient had fever peaks over the last couple of days. He is worried about these peaks.</b>\n </div>"
},
"extension": [
{
"url": "http://example.org/do-not-use/fhir-extensions/referral#requestingPractitioner",
"valueReference": {
"reference": "Practitioner/f201",
"display": "Dokter Bronsig"
}
},
{
"url": "http://example.org/do-not-use/fhir-extensions/referral#notes",
"valueString": "The patient had fever peaks over the last couple of days. He is worried about these peaks."
},
{
"url": "http://example.org/do-not-use/fhir-extensions/referral#fulfillingEncounter",
"valueReference": {
"reference": "Encounter/f201"
}
}
],
"modifierExtension": [
{
"url": "http://example.org/do-not-use/fhir-extensions/referral#referredForService",
"valueCodeableConcept": {
"coding": [
{
"system": "http://snomed.info/sct",
"code": "11429006",
"display": "Consultation"
}
]
}
},
{
"url": "http://example.org/do-not-use/fhir-extensions/referral#targetDate",
"valuePeriod": {
"start": "2013-04-01",
"end": "2013-04-15"
}
},
{
"url": "http://example.org/do-not-use/fhir-extensions/referral#status",
"valueCode": "complete"
}
],
"identifier": [
{
"system": "http://goodhealth.org/basic/identifiers",
"value": "19283746"
}
],
"code": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/basic-resource-type",
"code": "referral"
}
]
},
"subject": {
"reference": "Patient/f201",
"display": "Roel"
},
"created": "2013-05-14",
"author": {
"reference": "Practitioner/example"
},
"meta": {
"tag": [
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActReason",
"code": "HTEST",
"display": "test health data"
}
]
}
}Data Fields
| Data Field | Type | Description |
|---|
| resourceType | Basic | This is a Basic resource |
| id | id | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
| meta | Meta | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. |
| implicitRules | uri | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. |
| language | code | The base language in which the resource is written. |
| text | Narrative | 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 | BackboneElement | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. |
| extension | Extension | May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
| modifierExtension | 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). |
| identifier | Identifier | Identifier assigned to the resource for business purposes, outside the context of FHIR. |
| code | CodeableConcept | Identifies the 'type' of resource - equivalent to the resource name for other resources. |
| subject | Reference | Identifies the patient, practitioner, device or any other resource that is the "focus" of this resource. |
| created | date | Identifies when the resource was first created. |
| author | Reference | Indicates who was responsible for creating the resource instance. |
Extensions