Overview

Documents the internal service APIs.

Details

There is a collection of internal APIs that provide the core functionality. Applications could be developed to use a “within JVM” connection to these services and through JPA lazy initialization entire graphs of objects can be read from the database (in either their current state or any desired past state). 

Data model access services generally take either internal ids or terminology-specific assigned identifiers (e.g. SCTID) and return individual objects without any eagerly initialized connected data. TBD.. discuss this for each "type" of domain model object

Services that create, modify, or remove data objects ...

Dual independent review of map records is achieved by creating completely separate objects associated with each user and then comparing when both have indicated work on mapping the underlying concept is complete.

In general, methods that find data return search result objects with identifiers (with display labels) that can be used to perform subsequent lookups to retrieve the underlying model objects. These methods typically also take a paging/sorting/filtering parameter to allow for controlled access to the desired amount of data.

Root Service

All services implement root service which provides the following functionality

Security Service

The internal security service API supports the following functionality:

Metadata Service

The internal metadata service API supports the following functionality:

Content Service

The internal content service API supports the following functionality:

Mapping Service

The internal mapping service API supports the following functionality:

 

Workflow Service

The internal workflow service API supports the following functionality:

 

Report Service

The internal report service API supports the following functionality:

References/Links