Building point solutions using partial codesets (refsets) as each need arises may be efficient for each point solution. Point solutions create maintenance overhead that will accumulate as SNOMED is used more and more.
Ideally we would all connect to a central high availability environment however current recommendation is that a local runtime instance of SNOMED terminology server should be used for production applications (https://www.tewhatuora.govt.nz/our-health-system/digital-health/terminology-service/).
To closely couple applications would require local runtime instance rather than linking to central NZHTS. This requires a local copy of the terminology server for local applications. Maintain once use many times. {NB being very lose with the definition of ‘local’}
Has any Te Whatu Ora organisation already implemented a local copy? Or is there a relatively inexpensive commercial option available that is in use already?
There are descriptions of how a local terminology service can be done on both SNOMED international and Australian Digital Health Agency sites, and probably on other sites. Anyone with experience in downloading installing a runtime instance please post in this thread.
Would be helpful if we could collaborate on install, and maintenance. Likely we will need to have local terminology servers in multiple places.
Thoughts, suggestions, pointers to code (github etc). Other forums?
Regards Paul Docherty (TWO Waikato)