visit the hl7 website
Ontario eForms HL7® FHIR® SDC Implementation Guide - v1.2.0 TU-snapshot1
fhir-logo
  • Index
  • Home
    • Home
    • Introduction
    • Relationship to Other Specifications
    • Scope
    • Glossary
  • Business Context
    • Business Context
    • Business Model
    • Business Data
    • Use Cases
  • Technical Context
    • Technical Context
    • Form Behavior and Rendering
    • Implementer Responsibility
    • Conformance Rules
    • Connectivity Summary
  • FHIR Artifacts
    • FHIR Artifacts
    • Profiles
    • Extensions
    • Terminology
    • Examples
    • Response Handling
    • Downloads
  • Change Log
    • Change Log
    • Known Issues & Future Developments
    • Revision History
    1. Index
    2. Home

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

1.0. Home

This Implementation Guide (IG) provides guidance, profiles, and supporting materials to enable consistent implementation of FHIR for this project. The guide is structured into the following sections:

Section Purpose
Home Introduces the IG and provides general background information about the project.
Business Context Provides an overview of the business model, relevant data (PHI), use cases, and business rules that this IG supports.
Technical Context Describes the profiling methodology, mapping strategies, implementation guidance, and security considerations. Start here if you're planning on building an Implementation Guide.
FHIR Artifacts Central location for all defined FHIR artifacts: profiles, extensions, value sets, data type profiles, operations, search parameters, and examples.
Change Log Tracks specification changes, lists known issues, and provides a place to collect feedback from implementers and reviewers.

1.0.1. Term use

This guide is written in alignment with policies established in conjunction with the Ontario Health privacy team to enable appropriate review and consideration of this specification by the Information and Privacy Commissioner of Ontario (IPC). This means aligning common industry terminology with that used in the Personal Health Information Protection Act (PHIPA). To ensure readability and specificity, the industry standard terms will be retained and the legislative term or abbreviation will be included in brackets. For example:

  • Practitioner (HIC), referring to Health Information Custodian
  • Health data (PHI), referring to Personal Health Information
  • Software application (DHA), referring to Digital Health Asset
  • Patient (Individual)

NOTE: When using underlying FHIR resources that use these business terms, it is not possible for tooling reasons to provide the legislative terms as well. However, the legislative terms still apply in those situations.


1.0.2. Section Contents

  • Introduction
  • Relationship to Other Specifications
  • Scope
  • Glossary

1.0.3. Intended Audience

The intended audiences of this document are the Health Information Custodians (HICs) and the vendors of the digital health assets as identified in the Scope section of this implementation guide.

The readers are expected to have an understanding of the fundamentals of HL7 FHIR Release 4 and the RESTful paradigm, as well as familiarity with the HL7 FHIR Structured Data Capture Implementation Guide.

Version: 1.2.0 FHIR Version: R4.0.1

Powered by SIMPLIFIER.NET

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