HTB: Impact of SNOMED-CT RF2 Coding Scheme Loaded as 'Editable' and then Converted into 'Versionable'
Last updated on MAY 07, 2017
Applies to:Oracle Healthcare Transaction Base - Version 6.1 and later
Information in this document applies to any platform.
On Oracle Healthcare Transaction Base (HTB) 6.1 with SNOMED RF2 Compatibility Patch (Patch 17812866), SNOMED-CT RF2 was loaded as 'Editable' and then in the Database, HCT_ET_VERSIONS was updated from 'Editable' to a loaded version using createCodingSchemeVersion API. The final scope of this setup would be to use the old version as default.
Is this the correct approach and will that have any negative impact?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms