On 12/09/2016 07:01, [email protected] wrote:
I strongly recommend looking at the way terminology services are handled in FHIR. A ValueSet Resource (ie the subsets you're talking about) has a URI, so that it can be replicated in a local TS and referenced by it's well-known identifier rather than just a URL. It has a definition (which may be an explicit list of codes, or based on filters (ie rules) - for SNOMED CT you can use the Expression Constraint Language), and it also has an expansion - the enumeration of the codes that satisfy the definition with respect to a particular version of the underlying code system.
does the expansion preserve IS-A relationships (at least optionally)? That's crucial for making any value set of more than about 20 terms usable in a real system.
- thomas _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
