visit the hl7 website
Ontario Provincial Consent Override Interface HL7® FHIR® Implementation Guide v1.0.0-draft1
fhir-logo
  • Index
  • Home
    • Home
    • Introduction
    • Relationship to Other Specifications
    • Scope
    • Glossary
  • Business Context
    • Business Context
    • Business Model
    • Business Data
    • Use Cases
    • Business Rules
  • Technical Context
    • Technical Context
    • Implementer Responsibility
    • Conformance Rules
    • Connectivity Summary
  • FHIR Artifacts
    • FHIR Artifacts
    • Interactions
    • Profiles
    • Extensions
    • Terminology
    • System URIs
    • Examples
    • Capability Statement
    • Response Handling
    • Downloads
  • Change Log
    • Change Log
    • Known Issues & Future Developments
    • Revision History
    1. Index
    2. Business Context
    3. Business Data

For a full list of available versions, see the Directory of published versions

2.2. Business Data

This model is linked to Ontario’s Electronic Health Record (EHR) Conceptual Information Model 2.0 (CIM 2.0). See: https://ehealthontario.on.ca/files/public/support/Architecture/Ontario_EHR_CIM_2.0.pdf

To support the use of structured data through the adoption of data content and health terminology standards in the solution, this CDM also includes high-level entity relationships and attributes discovered in versions of FHIR interoperability standard for patient summary specifications. The model does not repeat the structure of the messages laid out in FHIR. Links to FHIR specs are included for entity definitions and field code values. In any difference of meaning between cited FHIR elements and this model, FHIR is the authoritative voice. This model relies on the following specifications:

  • FHIR R4 - The current official version of FHIR as of the time this implementation guide was published.

2.2.1. Conceptual Data Model ERDs and Metadata

Entity Relationship Diagrams (ERDs) follow. These include:

  1. a conceptual high-level ERD for solution data structures for the Release 1 solution, including metadata for each entity,
  2. an ERD for the Client & Provider subject area (including metadata for each entity) which is not called out as a FHIR Profile but is included because all other entities in the model are dependent on it,

ERD Legend

2.2.2. Conceptual Data Model

Note: The concepts and definitions presented below are derived from the Ontario Electronic Health Record (EHR) Conceptual Information Model (CIM) and are included to provide a common business context for the PCOI specification. These concepts are not intended to represent PCOI-specific information entities. Where applicable, the concepts have been mapped to corresponding FHIR resources.


pcoi-datamodel

Entity Name Description Corresponding FHIR Resource
Client Supporter A person who provides care to a health care client who needs supervision or assistance. He or she may provide the care in the home, in a hospital, or in an institution.
Although caregivers include trained medical, nursing, and other health personnel, the concept also refers to parents, spouses, or other family members, friends, members of the clergy, teachers, social workers, fellow health care clients.
This could be an informal care giver: unpaid, unlicensed, often untrained, often a friend or family member of the health care client.
It includes information about contact method (e.g. geographic or virtual address, telephone number and other demographics).
Patient.contact (Contact element within Patient Resource)
Health Care Provider A person or an organization that provides health care or other health-related services or products. It includes information about contact method:
• geographic address
• virtual address
• telephone number
• other demographics
Practitioner, Organization
Health Care Provider Role A part played by a health care provider (regulated or unregulated) that provides a type of care to a particular health care client.
Examples:
  • Acupuncturist
  • Advanced Care Paramedic
  • Audiologist
  • Certified Graduate Nurse
  • Chiropractic
  • Clinical Counsellor
  • Combined Lab and X-Ray Technologist
  • Communicable Disease Case Investigator
  • Counsellor
  • Critical Care Paramedic
  • Dental Assistant
  • Dental Hygienist
  • Dental Technician
  • Dentist
  • Denturist
  • Emergency Medical Responder
  • Homeopath
  • Home Support Worker
  • Kinesiologist
  • Lab Technician
  • Licensed Practical Nurse
  • Marriage and Family Therapist
  • Medical Doctor
  • Medical Laboratory Technologist
  • Medical Officer of Health
  • Midwife
  • Nuclear Medicine Technologist
  • Occupational Therapist
  • Optician
  • Optometrist
  • Paramedic Practitioner
  • Pharmacist
  • Pharmacy Technician
  • Physiotherapist
  • Personal Support Worker
  • Podiatrist
  • Primary Care Paramedic
  • Psychiatrist
  • Psychologist
  • Psychotherapist
  • Radiation Technologist in Magnetic Resonance
  • Radiation Technologist in Radiation
  • Radiation Technologist in Therapy
  • Recreation Therapist
  • Registered Acupuncturist
  • Registered Clinical Social Worker
  • Registered Dietitian
  • Registered Massage Therapist
  • Registered Midwife
  • Registered Nurse
  • Registered Nurse Practitioner
  • Registered Psychiatric Nurse
  • Respiratory Therapist
  • Social Services Worker
  • Social Worker
  • Speech Language Pathologist
  • Speech Therapist
  • Veterinarian
  • N/A
    Healthcare Client An individual participating in the health care system for the purpose of receiving therapeutic, diagnostic, or preventive procedures. (U.S. National Library of Medicine - Medical Subject Headings)
    A natural person (i.e. a human being) who:
  • is eligible to receive health care services in Ontario, or
  • has received or is receiving health care services in the province of Ontario (i.e. a health care client).

  • This entity covers personal identifying information but not health information. It includes information about:
  • identity within the health system e.g. a Health Number; each care setting may have a separate unique ID. E.g. a research study may uniquely identify a health care client as a test subject.
  • administrative gender, e.g. Male, Female, undisclosed
  • adoption: whether or not the health care client was adopted
  • birth and death dates
  • official versus preferred name
  • whether or not the health care client would prefer to receive correspondence
    The health care client's identity may be unknown e.g. for a protected person or if the identity of the health care client is unknown. A health care client may be a VIP whose identity must be omitted from reporting. A health care client may be identified by an alias. Health care client-identifying information could include a photograph. May be elated genetically or by physical co-location (e.g. residential, occupational, travel, etc.) to another person not necessarily a health care client.
    Depending on care setting, a health care client may be referred to as:
  • Patient (currently receiving care)
  • Participant (in a clinical study)
  • Resident (of a long term care facility)
  • Subject (in a public health case)
  • Client (in home care/community care cases/ settings)
  • Patient
    Provider Organization An organization that provides health care or other health-related services or products.
    Includes e.g. insurers and transcription services.
    May have information on service classification e.g. Regional Cancer Centre.
    (For Single Sign on application, a Provider Organization may be a Sponsoring Organization, a Health Care organization that has users that require access to at least one Federated Service. 2015-6-15)
    Organization
    Provider Person Describes a health care provider involved in the delivery of healthcare services. Encompasses both professional and non-professional members.
    Has professions, areas of practice for which the provider is qualified. May have information on clinician credentialing and privileging as defined by the applicable professional and governing organizations. This includes remote participation (e.g., via tele-health activities such as tele-consultation, home health monitoring.) Includes any information about licensing status and license suspension. May be an author, authenticator or scribe/transcriber of clinical documentation.
    Has a Unique Provider Identifier, a key assigned by eHealth to uniquely identify each Provider. May have a health system universal ID. May have a license number or national provider identifier (U.S.). May have multiple unique identifiers.
    Practitioner
    Information Consent Directive A directive received from a health care client or health client for the purpose of restricting access to Personal Health Information (PHI) by Health Information Custodians (i.e. implied consent directive).
    If a consent directive is in place, it is only to prevent access to PHI in the EHR for health care purposes. Consent directives will apply only in respect of sharing of PHI for provision of health care (since EHR is to be accessed only for this purpose). Consent directives do not have a time limit.
    May be overridden by Consent Override in a 'break the glass' scenario. Consent overrides may be permitted only for the following purposes as authorized by law:
  • if health care client or Substitute Decision Maker (SDM) provides express consent for the override to facilitate provision of health care to the health care client, or
  • to prevent, eliminate or reduce risk of serious bodily harm to a person (if it is not reasonable to obtain consent in timely manner) or to a group, where the HIC believes on reasonable grounds that the collection is necessary for this purpose.

  • Additional purposes are not permitted.
    Consent
    Permission Override In Temporary Override with Client’s Consent a Client allows a Provider temporary access to the Client’s restricted Personal Health Information (PHI). In Temporary Override without Client’s Consent a Provider temporarily accesses a Client’s restricted Personal Health Information without the Client’s consent. This scenario may play out in an Emergency setting where the Providers do not have the ability to obtain consent from the Client (or the Client’s SDM) but must access their PHI for the purpose of providing care.
    For example, normally the 'Dietician' role can only view (not update) the Health Care Client's diary. A Health Care Client may grant special permission to his/her dietician to enable him/her to update the nutritional intake portion of the diary. In another example an ER physician may gain temporarily access to PHI to treat a non-communicative emergency patient.
    Override permission is only allowed under 3 circumstances:
  • With express consent
  • For health care purposes
  • For reducing risk of harm to others
  • Consent (Action + Purpose)

    2.2.3. Client and Provider Subject Area

    client-erd

    For details on:

    • Health Care Client: Healthcare Client
    • Client Supporter: Healthcare Client - Contact
    • Client Supporter: RelatedPerson
    • Provider Person: Provider Person
    • Provider Organization: Organization
    • Health Care Provider Role: N/A
    • Information Consent Directive: Consent (Scope)
    • Permission Override: Consent (Action + Purpose)

    2.2.4. Consent Subject Area

    consent-erd-2

    For Details on:

    • Information Consent Directive: Consent (Identifier + Scope)
    • Permission Override: Consent (Action + Purpose)
    • Health Care Client: Healthcare Client
    • Provider Person: Provider Person
    Version: 1.0.0 FHIR Version: R4.0.1

    Powered by SIMPLIFIER.NET

    HL7® and FHIR® are the registered trademarks of Health Level Seven International