/
Upgrading SHR
Upgrading SHR
SHR can now be exposed under two urls:
Latest SHR
http:shr_host:shr_port/path/to/end-point --> default url
http:shr_host:shr_port/version/path/to/end-point --> versioned url
- If a new version is released, the older version need not serve the default url.
To achieve this clear out the IS_LATEST_SHR property of SHR Service
set SHR_VERSION=v1
Older SHR
http:shr_host:shr_port/v1/path/to/end-point
- By default clients, point to the latest shr. However if versioned shr services are maintained, clients can still point to an earlier version.
- Version configuration placeholders are present in the respective property files for each project, where version can be updated.
client property | name |
---|---|
bdshr client | shr.version |
datasense | SHR_VERSION |
patient journal | SHR_VERSION |
This way, only clients who are strict about sticking to an older version have to update their properties to point to the older version.Else auto point to the latest version
- Update the markers table to point to the older version for the sync to continue.
, multiple selections available,
Related content
SHR Development
SHR Development
More like this
SHR API Versions
SHR API Versions
More like this
General Validations in SHR
General Validations in SHR
More like this
Reference Client Application for SHR
Reference Client Application for SHR
More like this
Fhir Upgrade
Fhir Upgrade
More like this
Steps after new bahmni installation
Steps after new bahmni installation
More like this