PharmaNet Re-Conformance Project

To All PharmaNet Software Support Organizations:

Action required: Please provide a direct point-of-contact (including the individual’s name, phone, and email) for the CIS team to establish communications and scheduling.


The updated British Columbia Professional and Software Conformance Standards for Electronic Health Information Exchange (which were released on Feb. 26, 2021) replace all previous compliance/conformance standards.

Note: The PharmaNet Legacy Compliance Standards are no longer available for new development.

The updated conformance standards package for PharmaNet includes:

  • BC Conformance Standards - Release Notes
  • Glossary
  • Volume 1: Overview & Conformance Processes
  • Volume 2: Information Privacy and Security
  • Volume 3A: Business Rules - General
  • Volume 3C: Business Rules - PharmaNet
  • Volume 4A: Application Enforced Rules - General
  • Volume 4C: Application Enforced Rules - PharmaNet
  • Volume 4C: Technical Message Specifications - PharmaNet
  • Volume 5B: Transport Protocol - HNSecure
  • Volume 5B: Technical Message Specifications - HNSecure


All applications must pass conformance testing against the ministry’s updated conformance standards in order to integrate with PharmaNet.

There have been significant updates which include (but are not limited to) the following:

  • Volume 1: Conformance processes and policy updates
  • Volume 2: Enhanced privacy and security rules that reflect current industry standards (e.g., safeguarding personal health information, allowing access only to authorized individuals)
  • Volume 4C: Updated PharmaNet conformance standards

    ​Highlights include (but are not limited to):
    • Transaction matrix updates including the following new transactions (for v70 access types):
      • TRX (X0/X5) – Retrieve Patient Prescription
      • TRX (X1/X6) – Record a Prescription
      • TRX (X2/X7) – Update Prescription Status
      • TRX (X3/X8) – Adapt a Prescription
      • TRX (X4/X9) – Retrieve Prescriber Prescription
    • Mandatory Global PharmaNet ID (GPID) and IP address in the message header (MSH) security field
    • New applications must integrate with the Client Registry

      Note: Integration with Client Registry is optional for existing applications.
    • Updates to:
      • Access logging and addition of telepharmacy site reporting
      • Data retention (local business & prescription records)
      • Electronic storage of pharmacy and prescription records
      • Mandatory display standards for transactions
      • Storage of PharmaNet clinical data

Mandatory Requirements

Each of the following requirements must be completed:

  • A new Vendor Participation Agreement (VPA) must be signed by all organizations integrated with PharmaNet.
  • All applicable conformance standards (e.g., business rules, application enforced rules, privacy and security rules, training requirements) will be taken in account in the conformance decision.
  • Going forward, all sites must deploy a software version that has passed conformance through the PharmaNet Re-Conformance Project in order to continue in the production environment.
    • All previous software versions will be decommissioned following a transition period.
    • Additional application changes that follow the PharmaNet Re-Conformance Project will be managed through the normal process as described in Volume 1: Overview & Conformance Processes (PDF, 625KB).


The following is a high-level summary of the Ministry’s conformance processes for PharmaNet integration:

PharmaNet Reconformance Project Diagram

  1. Each organization must sign the VPA.
    • Organizations without a signed VPA cannot integrate with PharmaNet.
    • The VPA will replace any existing agreements (e.g., SLA).
    • The term of the VPA will be for five years after the date of signing.
  2. Each organization must pass self-testing.
    • Once an organization is ready to proceed with self-testing, the Ministry will provide detailed information.
  3. Each organization must submit a Conformance Initiation Notice (CIN) to schedule re-conformance testing.
  4. The PharmaNet and P&S conformance processes will be completed in parallel.
  5. All applicable conformance standards (e.g., business rules, application enforced rules, privacy and security rules, training requirements) will be taken in account in the conformance assessment.
  6. An Interface Approval Notice (IAN) will be issued as follows:
    • IAN without conditions – if all conformance assessments are passed.
    • IAN with conditions – may be issued if there are minor deficiencies and/or gaps.
      Note: This letter may have a limited duration of 6-12 months, during which the organization must remedy all deficiencies.
    • The IAN will allow the application to be released in production for the term specified and with the respect to any identified conditions.

Conformance Test Cases

The required connections, test cases, and test data will be provided once an organization is ready to proceed with self testing and/or formal conformance testing.


Conformance testing will be scheduled by access type:

Phase 1 - Jun. 30, 2021
  • COMPAP - v03
  • EDAP - v03
  • HAP - v03
Phase 2 - Oct. 31, 2021
  • Pharmacy - v70
  • In-Patient (Pharmacy) - v03
Phase 3 - Oct. 31, 2022
  • HA-BPMH - v70
  • HA-Viewer - v70

Note: The ministry will attempt to accommodate requests to combine testing for multiple access types.


For more information, contact the Ministry’s Conformance and Integration Services at: