Operations

PS-AB API Specification

Refer to Alberta Patient Summary (PS-AB) API Specification.

Submission Quick Reference Table

This section provides a quick-reference table for the PS-AB submission process

Initial Submission

Initial submission SHALL be used when a patient summary has never been previously submitted.

Attribute	Notes
Bundle.id	SHALL be assigned by CII upon successful validation of submitted PS-AB instance. SHALL be a new UUID per each instance of a PS-AB. Note: CII SHALL make location (using Bundle.id) resolvable.
Bundle.identifier	SHALL be assigned by Source EMR. SHALL be the same for every updated instance and SHALL be globally unique. SHALL match Composition.identifier (value + naming system).
Composition.id	SHALL be assigned by Source EMR. SHOULD be a UUID.
Composition.identifier	SHALL be assigned by Source EMR. SHALL remain static for same author and PS-AB instance. MAY be a UUID, if not a UUID, then value + Alberta Health assigned naming system SHALL be globally unique
Composition.status	“final”
REST API	POST
Rules/Validations	PS-AB content is valid per PS-AB FHIR Profile definitions. Client demographics are valid per pCR validation. Composition.identifier is indeed globally unique. If Composition.identifier exists, CII checks that author (Practitioner.identifier’) matches.

Update Submission

Update submission SHALL be used when a patient summary was previously submitted and changes on patient information in medical chart have taken place.

Note: Update submission SHALL also be used when data about a patient was incorrectly reported on another patient in EMR and a subsequent patient summary was submitted. To correct the data in patient summary in Alberta Netcare, an update submission to both patients SHALL be performed to replace the incorrect patient summaries.

Attribute	Notes
Bundle.id	SHALL be assigned by CII upon successful validation of submitted PS-AB instance. SHALL be a new UUID per each instance of a PS-AB. Note: CII SHALL make location (using Bundle.id) resolvable.
Bundle.identifier	SHALL be assigned by Source EMR. SHALL be the same for every updated instance and SHALL be globally unique. SHALL match Composition.identifier (value + naming system).
Composition.id	SHALL be assigned by Source EMR. SHOULD be a UUID.
Composition.identifier	SHALL be assigned by Source EMR. SHALL remain static for same author and PS-AB instance. MAY be a UUID, if not a UUID, then value + Alberta Health assigned naming system SHALL be globally unique
Composition.status	“amended”
REST API	POST
Rules/Validations	PS-AB content is valid per PS-AB FHIR Profile definitions. Client demographics are valid per pCR validation. Composition.identifier is indeed globally unique. If Composition.identifier exists, CII checks that author (Practitioner.identifier’) matches.

Cancel Submission

Cancel submission SHALL only be used when a patient should never have had a patient summary (i.e., a patient summary for another patient was sent in error for this patient).

Attribute	Notes
Bundle.id	SHALL be assigned by CII upon successful validation of submitted PS-AB instance. SHALL be a new UUID per each instance of a PS-AB. Note: CII SHALL make location (using Bundle.id) resolvable.
Bundle.identifier	SHALL be assigned by Source EMR. SHALL be the same for every updated instance and SHALL be globally unique. SHALL match Composition.identifier (value + naming system).
Composition.id	SHALL be assigned by Source EMR. SHOULD be a UUID.
Composition.identifier	SHALL be assigned by Source EMR. SHALL remain static for same author and PS-AB instance. MAY be a UUID, if not a UUID, then value + Alberta Health assigned naming system SHALL be globally unique
Composition.status	“entered-in-error”
REST API	POST
Rules/Validations	PS-AB content is valid per PS-AB FHIR Profile definitions. Client demographics are valid per pCR validation. Composition.identifier is indeed globally unique. If Composition.identifier exists, CII checks that author (Practitioner.identifier’) matches.