The formal definitions for the elements in the patient resource. Also available as an XML file.
| Patient |
| Definition | A patient is a person or animal that is receiving care |
| Control | 1..1 |
| Requirements | Tracking patient is the center of the healthcare process |
| RIM Mapping | Patient |
| Patient.link |
| Definition | A linked patient record is a record that concerns the same patient. Records are linked after it is realized that at least one was created in error. |
| Control | 0..* |
| Type | Resource(Patient) |
| Must Understand | true |
| Requirements | Due to the clerical errors associated with the difficulties of identifying humans consistently, duplicate patient records are frequently created in error |
| Comments | More then two patient records may be linked. Note that there is a special transaction for linking patient records in the RESTful context, as record linking consistency must be maintained |
| Patient.active |
| Definition | Whether the patient record is in use, or has been removed from active use |
| Control | 1..1 |
| Type | boolean |
| Must Understand | true |
| Requirements | Need to be able to mark a patient record as not to be used because it was created in error |
| Comments | If a record is inactive, and linked to an active record, then future patient/person/record updates should occur on the other patient |
| Patient.subject |
| Definition | The person or animal that this patient record is about |
| Control | 1..1 |
| Type | Resource(Person|Animal) |
| Must Understand | true |
| Requirements | Need to link this patient record to a known and identifiable person or animal |
| Patient.provider |
| Definition | The provider for whom this is a patient record |
| Control | 1..1 |
| Type | Resource(Organization) |
| Must Understand | true |
| Requirements | Need to know who recognises this patient record |
| To Do | But is thie same as institution above? |
| Patient.identifier |
| Definition | An identifier that applies to this person as a patient |
| Control | 0..* |
| Type | HumanId |
| Must Understand | true |
| Requirements | Patients are almos always assigned specific numerical identifiers |
| Patient.diet |
| Definition | Dietary restrictions for the patient |
| Control | 0..1 |
| Type | CodeableConcept from PatientDiet |
| Requirements | Track patients reported dietary restrictions to help with catering requirements |
| Comments | not for specifying medical diets, but for casual dietary restrictions such as vegetarian, diary-free, nut-free, etc |
| Patient.confidentiality |
| Definition | Confidentiality of the patient records |
| Control | 0..1 |
| Type | CodeableConcept from PatientConfidentiality |
| Requirements | Need to be able to track which patient records are particularly sensitive |
| Comments | Confidentiality tracking also occurs at more detailed points in the medical record |
| Patient.recordLocation |
| Definition | The location of the paper record for the patient, if there is one |
| Control | 0..1 |
| Type | CodeableConcept from PaperRecordLocation |
| Requirements | Track old paper records where these are still in use |
| Patient.extension |
| Definition | See Extensions |
| Control | 0..* |
| Type | Extension |
| Patient.text |
| Definition | Text summary of resource (for human interpretation) |
| Control | 1..1 |
| Type | Narrative |
. Page versions: R5 R4B R4 R3 R2
This is an old version of FHIR retained for archive purposes. Do not use for anything else