Overview
A glossary of phrases used in this documentation and what they mean.
Glossary
Term | Definition |
|---|---|
| API | A collection of conceptual services for performing tasks with domain model objects. |
| Domain Model | Conceptual objects (with implementations) that represent the information meta-model used by this service. In this case it is based on RF2 and includes things like Concepts, Descriptions, and Relationships. |
| Internal Service API | A collection of java-based services that must be accessed from within an actual Java application. |
| Map Admin | A map user who has access to administrator functions for a map project. |
| Map Advice | A project-specific piece of information associated with a map entry. |
| Map Entry | Represents the target code of a map and is contained within a map record and has zero or more map advices or map principles. |
| Map Lead | A map user who has access to lead functions for a map project. |
| Map Principle | An indicator from the map principles handbook used to collect statistics about when and how often certain important conditions apply. This is very project-specific information. |
| Map Project | A mapping effort between a version of a source terminology and a version of a target terminology. For example, mapping between SNOMED and ICD10. A variety of metadata and functional pieces contribute to the overall behavior of a map project within the tool |
| Map Record | A complete map of a concept within a map project. Depending upon the features of the map project, a record may have one or more entries which may themselves be grouped. |
| Map Specialist | A map user who has access to specialist functions for a map project. |
| Map User | An authenticated user of the application. There are a few special meta users, including "qa", "loader", and "guest". These users cannot "log in" and do not have accounts in the underlying security system. The mapping application tracks its own users and associates them with particular roles on various projects. A map user implicitly has guest privileges on projects that are not private. |
| REST Service APIs | A REST implementation of functionality based on the internal service APIs. In a sense, you can consider the REST services to be the primary application of the internal service APIs (with the admin tools being the other). |
References/Links
- n/a