Change Log

CA Core+ v0.1 DFT - Ballot Reconciliation

• Created Mapping Logic page to convey logic for how pCHDCF and obligation mapping was applied, ensuring that mapping is consistent and that reviewers have the rationale for primary and secondary mappings
• Created Relationship to Other Specifications to convey relationship between this guide and other pan-Canadian specifications
• Created Change Log,Known Issues & Future Development, and Specification Feedback pages
• Shifted to using the updated obligation codes from the recent 5.1.0-snapshot publication of the extension registry guide
• Removed identifier slices from Patient (CA-Core) and Practitioner (CA-Core)
• Removed mapping & obligations on elements that mapped to concepts that have since been removed in the pCHDCF Data Content Standard: Patient Notes
• Modified the way that the following concepts are profiled in Patient (CA-Core) to align to updates in pCHDCF Data Content Standard to allow for better concept separation
  • name, telecom, address, contact relationship & role
• Updated name invariant on Patient (CA-Core) to be better aligned to IPA modelling
• Socialized individual-recordedSexOrGender extension on the Patient (CA-Core) profile
• Temporarily removed obligations (and mappings) on provider concepts that could be mapped to Practitioner & PractitionerRole FHIR Resources until pCHDCF data modelling is further along for Care Team Member concepts
• Applied technical corrections (typos, corrected mapping tables in guide to match mapping element in profiles, added hyperlinks to external content, adjusted diagrams, removed unintentional conformance language from actor definitions, etc.)
• Applied update to CA Baseline package version (1.1.5->1.1.7) in the dependencies file to accommodate bug fixes between versions