Terminology
The AB:eReC conforms to FHIR rules with regards to use of code systems and value sets for coded attributes.
When the the binding strength is set as “required”, AB:eReC uses the concepts from the bound code system or value set in CA:eReC.
When the binding strength is “extensible”, AB:eReC uses the concepts from the bound code system or value set in CA:eReC, otherwise, AB:eReC extends the value set with concepts that it needs that are not currently supported in a value set bound as extensible.
Lastly, when the binding strength is “preferred” or “example”, AB:eReC uses either a pan-Canadian or Alberta standard code system or value set (e.g. AB:eReC uses concepts from SCPTYPE for ProviderRole.code).
The following are code systems specific to AB:eReC:
- AdministrativeGender_AB: package/CodeSystem-administrative-gender-ab.json
- PreferenceTypeCode: PreferenceTypeCode
- PreferenceValueTypeCode:PreferenceValueTypeCode
- ProviderRoleType: package/CodeSystem-provider-role-type.json
- SpecialityCode: SpecialtyCode
- SubmissionMetadata: package/CodeSystem-submission-metadata.json
- TaskBusinessStatus_AB TaskBusinessStatus_AB
- TimestampTypeCode TimestampTypeCode
The following are value sets specific to AB:eReC:
- AdministrativeGender_AB: package/ValueSet-administrative-gender-ab.json
- PreferenceTypeCode: PreferenceTypeCode
- PreferenceValueTypeCode:PreferenceValueTypeCode
- ProviderRoleType: package/ValueSet-provider-role-type.json
- RecordedSexOrGenderType_AB: package/ValueSet-recorded-sex-or-gender-type-AB.json
- ReferralReasonCode: ReferralReasonCode
- NOTE the codes provided in the value set do not constitute the full list, only a few examples
- SecurityLabel: package/ValueSet-security-label.json
- SpecialityCode: SpecialtyCode
- SubmissionMetadata: package/ValueSet-submission-metadata.json
- TaskBusinessStatus_AB TaskBusinessStatus_AB
- TimestampTypeCode TimestampTypeCode