Person
"Demographics and administrative information about a person independent of a specific health-related context."
Highlights:
- "The Person resource serves as a linkage resource that may provide a reference set of common demographics for an individual (human or animal) across multiple roles (Patient, Practitioner,...)."
- Patient may have several identifiers
- Person structure is compatible with tblInsuree content: none of the Patient attribute is mandatory and Patient is "expandable" (with whatever we may want)
- ... but "RelatedPerson" (here under) doesn't point (directly) to Person!
Patient
"Demographics and other administrative information about an individual or animal receiving care or other health-related services."
Highlights:
- "A Patient record is generally created and maintained by each organization providing care for a patient. A patient or animal receiving care at multiple organizations may therefore have its information present in multiple Patient Resources."
- Patient may have several identifiers
- Patients are "Linked" to each other, according a LinkType... but this is NOT the equivalent of tblFamilies: it is used to depict patient entity merge (replaced-by, replaces,...), that master entity for information is another one (refer),...
- One can link Patients (in the tblFamilies meaning) via contact.relationship (supposed to be "partner", "friend",...) but contact detail is a very "weak" reference (keep a name, telecom,... but it is not a formal other Patient entity)
- Patient structure is compatible with tblInsuree content: none of the Patient attribute is mandatory and Patient is "expandable" (with whatever we may want)
"Information about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process."
Highlights:
- RelatedPerson refer to "Patient" (and not Person as its name seem to indicated it)
