Profiling Conventions & Approach
pCHDCF Translation Practices
This section will continue to expand in future iterations as content is further developed in the pCHDCF. This version focuses on 1) mapping the data element definitions from the pCHDCF Data Content Standard, 2) outlining a potential logic for translating initial expectations into FHIR profiles.
Mappings to the Data Content Standard data elements are defined in-line within the profiles and can be found on each profile's page.
Translating Obligations
In line with General Principles & Design these profiles make use of an emerging a new (and evolving) mechanism in FHIR that provides a consistent and machine processable way for profiles to define their expectations for system behaviors. This mechanism is the Obligation Extension which is defined in the cross-version extension registry but has been recently expanded to support application. The updated definition can be found in the CI Build FHIR Extension Registry definition.
The pCHDCF artifacts currently utilize the following definitions to convey the level of expectation for an element in a given context:
- M = Mandatory: where the data element is mandatory, and the process cannot be completed without the data element being present.
- RK = Required if Known: where the data element is required to be provided if available or known to support the process.
- O = Optional: where the data element is not required and may be provided to support the process.
These have been translated to the following obligation codes:
| pCHDCF Strength | Target for Expectation | Obligation Code |
|---|---|---|
| Mandatory | Resource Producer | use-reason |
| Mandatory | Resource Consumer | handle |
| Required If Known | Resource Producer | will-send |
| Required If Known | Resource Consumer | handle |
| Optional | Resource Producer | can-send |
| Optional | Resource Consumer | no-error |
Additional considerations:
- Some expectations are expected to be nested/conditional; others will require the backbone element carries the same strength
- Optional elements identified as stretch goals may not carry the can-send obligation (e.g., National Unique Health Identifier). These will be socialized with a comment until further is known about expectations for consumers/producers.
Note: Given the preliminary nature of the content in this release (see Scope of Guide), expectation details for the identified data elements were not in scope of this round of profiling. For this reason, the current profiles apply the minimum expectation strength (can-send/no-error) to all elements that have been identified at this stage, with a few exceptions for elements identified by CIHI as stretch goals. Application of obligation will continue to be updated as the pCHDCF content is developed and refined.