Navigate to the Canadian Institute for Health Information home page

Logical Data Model

Logical Data Model (LDM) / Entity / Party Role

Project:

Party Role
Appears In: Care Team LDM Subject Area, Diagnostic Imaging Reporting LDM Subject Area, Medication Request, Statement, Administration LDM Subject Area, Patient Health Concern LDM Subject Area, Person Information LDM Subject Area, Clinical Notes and Documentation LDM Subject Area, Health Care Service Event LDM Subject Area, Contact Mechanism LDM Subject Area, Provenance LDM Subject Area, Provider LDM Subject Area, Organization Information LDM Subject Area, Geography LDM Subject Area, CACDI LDM View, Observation LDM Subject Area, Address and Location LDM Subject Area, Health Care Service LDM Subject Area, Encounter LDM Subject Area, Procedure LDM Subject Area, Immunization LDM Subject Area, Provider Health Human Resource LDM Subject Area, Appointment LDM Subject Area, Laboratory Test Result Reporting LDM Subject Area, Allergy and Intolerance LDM Subject Area
A Party fulfilling a specific function related to the Canadian health care system.<br/>
  • Attributes
  • Associations To
  • Associations From
  • Constraints
  • Other Links
Attribute Type
Party Role Digital Identity Identifier
Notes: A piece of electronic information that uniquely identifies an individual or organization. Can be stored on digital devices such as smartphones and computers.<br/>Data Type for Party Role Digital Identity is in development.<br/><br/>
Party Role Effective Date Date
Notes: The first date when the information specified is valid.<br/>
Party Role Expiry Date Date
Notes: The last date when the information specified is valid.<br/>
Relationship Target Entity
is   Medical Imaging Performer
is   Appointment Participant
has   Party Role Type
is   Health Care Service Event Non-Patient Participant
is   Encounter Non-Patient Participant
sent to (org)   Service Request
plays   Party
to   Party Role Relationship
acts as   Agent
sent from (org)   Service Request
has
Optional on the Service Language side: not all parties have a service language (e.g. Animals)<br/>
 Party Role Service Language
from   Party Role Relationship
for   Health Care Provider Organization Affiliation
initiates   Service Request
is   Party Group Member
performer
Alias: Asserter<br/>Who was responsible for asserting the observed value as "true".<br/><br/>FHIR<br/>
 Observation
is   Medical Imaging Interpreter
receives   Service Request
Relationship Target Entity
recorded by
<br/><br/>
 Patient Health Concern
has   Party Role Location
asserted by
The source of the information about the allergy<br/>
 Patient Allergy or Intolerance
asserted by   Medication Statement
asserted by
Asserter: Individual who is making the condition statement. (FHIR)<br/>
 Patient Health Concern
observes   Laboratory Test Result
issued by   Procedure Order
receives   Medical Imaging Report
reported by
Modeling note:<br/>backend data as identified in Data Content Standard. Aligns with FHIR V5 <a href="http://hl7.org/fhir/immunization-definitions.html#Immunization.informationSource"><font color="#0000ff"><u>http://hl7.org/fhir/immunization-definitions.html#Immunization.informationSource</u></font></a> <br/><br/>
 Immunization Reaction
receives   Laboratory Test Result
interprets   Laboratory Test Result
is   Medication Administration Performer
has   Party Role Contact Mechanism
is   Note Author
is   Reported Procedure Performer
is   Note Recipient
recorded by
Who recorded the allergy or intolerance<br/>
 Patient Allergy or Intolerance
Constraint
Unique Key: Party, Party Role Type, Party Role Effective Date
Connection Direction Entity
Generalization From Health Care Provider
Generalization From Care Team Participant
Generalization From Service Animal
Generalization From Patient