Releases of the PS-CA Implementation Guide may be found on a table on the Home Page of this Project.


Bundle (PS-CA)

Additional information on this profile (including the JSON & XML structure and detailed element descriptions) can be found at package/structuredefinition-profile-bundle-ca-ps.json

Profile

idΣ0..1string
metaΣ0..1Meta
implicitRulesΣ ?!0..1uri
language0..1codeBinding
identifierS Σ1..1Identifier
typeS Σ1..1codeBindingFixed Value
timestampS Σ1..1instant
totalΣ I0..1unsignedInt
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
fullUrlS Σ1..1uri
resourceΣ0..1Resource
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
fullUrlΣ0..1uri
resourceS Σ I1..1CompositionPSCA
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
modeΣ0..1codeBinding
scoreΣ0..1decimal
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
methodΣ1..1codeBinding
urlΣ1..1uri
ifNoneMatchΣ0..1string
ifModifiedSinceΣ0..1instant
ifMatchΣ0..1string
ifNoneExistΣ0..1string
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
statusΣ1..1string
locationΣ0..1uri
etagΣ0..1string
lastModifiedΣ0..1instant
outcomeΣ0..1Resource
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
fullUrlΣ0..1uri
resourceS Σ I1..1PatientPSCA
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
modeΣ0..1codeBinding
scoreΣ0..1decimal
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
methodΣ1..1codeBinding
urlΣ1..1uri
ifNoneMatchΣ0..1string
ifModifiedSinceΣ0..1instant
ifMatchΣ0..1string
ifNoneExistΣ0..1string
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
statusΣ1..1string
locationΣ0..1uri
etagΣ0..1string
lastModifiedΣ0..1instant
outcomeΣ0..1Resource
signatureΣ0..1Signature

Key Differences between the IPS-UV and PS-CA

IPS-UV is currently piloting a slight variation in the modeling of bundle, that involves creating an entry slice for every potential resource that could be included in an IPS section. IPS-UV has introduced this modeling as a potential method to reduce the amount of informational messages that are provided back during validation.

Since this modeling change has no impact on the constraints or expectations of what is included in the Bundle resource, both PS-CA and PS-ON have decided to maintain the current modeling until further trialing in IPS has occurred.

Further differences identified:

  • Bundle.type element is not Must Support (MS) in IPS-UV and MS in PS-CA.
  • Bundle.entry:composition and Bundle.entry:composition.resource elements are not MS in IPS-UV, but they are MS in PS-CA.
  • Bundle.entry:patient and Bundle.entry:patient.resource elements are not MS in IPS-UV and MS in PS-CA.