Thanks very much for the comments. Our initial requirement is simply code
validation, but a more extensive list can be found in our documents section
at Log In - OpenHIE Wiki.
ok - here's analysis:
Code validation: Given a source context (including version/date), return whether the source concept id is valid. Single/multiple input codes.
yes
Code normalization: Given a source and target context (including version/date), return the target concept id corresponding to a source concept id. Single/multiple input codes.
yes
Code look-up/translation: Given a source and target context (including version/date), return the concept name, optionally in a specified language, corresponding to a source concept id. Single/multiple input codes.
umm, possible, but not quite clear what single/multiple means
Search by partial phrase, begins with, partial word, including stop words
yes
Handle synonyms (return exact term user is looking for regardless of which concept it is linked to).
not sure what this means
Return all the descendants of a concept in a Code System (subsumption/decision support).
yes
Return whether a concept in a Code System is a descendant of another concept (subsumption/decision support).
yes
Return the (possibly specified) attributes associated with a concept in a Code System (permits hierarchical browsing, etc.)
not sure. this would need to be explored
> Load a file consisting of local code/target (standard) code associations.
Load a standard or local Code System/Value Set/Subset.
yes
Return all the names/codes within a Code System or named Value Set/Subset. Specify format: xml, csv, etc.
yes, though format would be a client/wrapper issue, not an API one
Return all the names/codes within a Code System or named Value Set/Subset that have changed since a specified version/date.
not currently specified, but I guess it would be possible
Return the names/codes in a named Value Set/Subset.
yes
Grahame