Business Context > Business Rules

Business Rules

Data Contribution

Generic Rules

  • Data contributions must structurally conform to this specification with valid code values. The system/code value must be a value that matches with what’s in the PHSD FHIR specification, e.g. HealthcareService.specialty, etc.
  • For fields with extension.translation, if French translated value is available, include it in the submission data
  • For each bulk submission all associate resources to the changed resource must be submitted together. e.g. if a Healthcare service changes location, then the Healthcare Service, and associated Location and Organization data must be submitted together.
  • Specific business rules related to submitting data via the Bulk Import APIs are as follows.

HealthcareService

  1. HealthcareService.id - should be blank on submission
  2. HealthcareService.identifier - at a minimum the source system local identifier must be provided. to identify a source system local identifier:
    1. Local Identifier
      1. use: fixed value "secondary"
      2. system: Local URI identifying system or provincially assigned see Identifiers for valid system URIs
      3. value: Local System identifier value
    2. where possible, contributors should also include the relevant service provider’s licence # if available. To identify a practitioner licence with the healthcare service submission submit the practitioner identifier as follows:
      1. Identifier.use should be “temp”;
      2. Identifier.system should be the regulated college uri defined in Identifiers
      3. Identifier.value = provider’s licence number

Organization

  1. Organization.id must blank on submission
  2. Organization.identifier - at a minimum a local identifier must be present on a submission:
    1. use = “secondary”,
    2. system = vendor specific system URI
    3. value = local id
      1. All Resource References must reference a valid resource in the companion resource file

Location

  1. Location.id is blank for submission
  2. Location.identifier at a minimum must have a local identifier. Local Identifiers are identified via:
    1. use = “secondary” is assigned to local identifiers,
    2. system = vendor specific system URI
    3. value = local id
  3. All Resource References must reference a valid resource in the companion resource file

Practitioner

  1. Practitioner.identifier
    1. at a minimum must have a regulated body issued identifier. regulated bodies are identified via:
      1. use = “official” is assigned to regulatory body identifiers,
      2. system = Regulatory College specific system URI . See Identifiers
      3. All Resource References must reference a valid resource in the companion resource file

PractitionerRole

  1. All Resource References must reference a valid resource in the companion resource file

Endpoint

  1. Endpoint.id is blank for submission
  2. Endpoint.identifier at a minimum must have a local identifier. Local Identifiers are identified via:
    • use = “secondary” is assigned to local identifiers,
    • system = vendor specific system URI
    • value = local id
  3. All Resource References must reference a valid resource in the companion resource file