Patient_MaritalStatuses
GetOptions
ValueSet
We did our best to remove as much complexity as we could from the data model while keeping everything that’s required to make it interoperable. However, we realise that building Healthcare applications is inherently complex, and therefore we included a Sample Application and accompanying Documentation to explain the fundamentals to help you get started building an interoperable Digital Health application using this data model.
We added 14 new interoperable health data structures in this release:
The following existing data structures now have new versions available and the previous versions have been deprecated:
NOTE: Each of the above data structures have corresponding Upgrade actions (e.g. Patient_Upgrade_v1_to_v2) that take in the v1 data structure and output the v2 data structure. These are private actions consumed by the new version’s Deserialize action, which will take the old version’s SimpleJSON and SimpleStructure (name) and it will automatically upgrade the data to return the data structure in the new version’s format. This streamlines the transition from an old data structure version to the new one.
The following new attributes have been added to some existing data structures:
Each main Health Data Structure now has corresponding Serialize and Deserialize actions (e.g. Patient_Serialize_v2 and Patient_Deserialize_v2). The Serialize action takes in the Data Structure and returns the SimpleJSON and SimpleStructure name. These can be stored as a pair of attributes (e.g. in the ResourceVersion entity, as demonstrated in the companion Sample Application) and then passed to the Deserialize action when needed to return the full Data Structure.
Reference to OutSystems UI was updated to version 2.18.2.
Many of the data attribute descriptions have been updated with more complete information.
Some data attributes had missing descriptions. These have been added.
Service Actions have been replaced with Server Actions for improved performance. The action names have the same name as the deprecated Service Actions, so all that is required to resolve this change in your consuming application is to Refresh References, remove the reference to the deprecated Service Action and select the new Server Action with the same name.
Structure descriptions have been updated to specify the particular Service Action that should be used to populate options, where applicable.
The following Service Actions for populating options have been added: