Data Type Profiles


This version of the PS-CA Implementation Guide has been superseded by a newer version. A full list of versions & releases of the PS-CA Implementation Guide may be found at Guides.


There are four data types that are profiled in PS-CA Version 1.

Data types are profiled in order to enforce constraints on what elements within the data type are required and/or are expected for systems to be able to demonstrate support.

CodeableConcept

This profile represents the constraint applied to the CodeableConcept data type by the PS-CA project to use the Coding-ca-ps data type profile in a way that is informed by the constraints of the CodeableConcept-UV-IPS profile but removes the overarching expectation that all patient summary creators must demonstrate they can support codings for conformance.

codingΣ0..*Data Type: Coding (PS-CA)
textS Σ0..1string

Note: This profile makes a significant change from the IPS-UV data type profile by removing the must support flag from the coding element.

  • While coding is not currently considered must support in Version 1.0.0, implementers that support codings should still send the codings for codeable concepts if they are available/appropriate and receivers should not produce failures or rejections if codings are included in the patient summary in the first release (a base tenet of FHIR).
  • Additionally vendors should expect that some jurisdictions may further constrain support of this element within the context of their own jurisdictional content
  • Implementors should also be aware that this constraint will be under consideration to be re-applied in PS-CA Version 2 .

Coding

This profile extends the capabilities of the coding data type to support multi-language designations (display). It relies on the Translation extension. This profile is informed by the constraints of the Coding-UV-IPS profile.

systemS Σ0..1uri
versionS Σ0..1string
codeS Σ0..1code
translationS I0..*Extension(Complex)
userSelectedΣ0..1boolean

Note: This profile makes no changes to the cardinality or placement of must support flags from IPS-UV, but has carried those constraints over into a unique PS-CA data type profile to ensure that implementers have clarity and consistency in the expectations this guide puts forth when must support is claimed.

Extensions

This profile uses the following extensions:

Quantity

This profile represents the constraint applied to the Quantity data type by the PS-CA project to use UCUM as the code system for units. Informed by the constraints of the Observation-Quantity-UV-IPS profile.

valueΣ0..1decimal
comparatorΣ ?!0..1codeBinding
unitΣ0..1string
systemS Σ I1..1uriFixed Value
codeS Σ1..1code

Note: This profile makes no changes to the cardinality or placement of must support flags from IPS-UV, but has carried those constraints over into a unique PS-CA data type profile to ensure that implementers have clarity and consistency in the expectations this guide puts forth when must support is claimed.

Ratio

This profile represents the constraint applied to the Ratio data type by the PS-CA project to use UCUM as the code system for units in a way that is informed by the constraints of the Ratio-UV-IPS profile.

numeratorS Σ I0..1Data Type: Quantity (PS-CA)
denominatorS Σ I0..1Data Type: Quantity (PS-CA)

Note: This profile makes no changes to the cardinality or placement of must support flags from IPS-UV, but has carried those constraints over into a unique PS-CA data type profile to ensure that implementers have clarity and consistency in the expectations this guide puts forth when must support is claimed.