| API | Application Program Interface, code that allows two software programs to communicate with each other |
| Artifact | A particular type of document that can be uploaded to the eTMF. Any artifact can also have sub-artifacts when they are closely associated with that artifact's area of a study |
| Attributes | The options available when choosing from drop-down lists, menus, or making other selections |
| Claim | A piece of information about a user that has been packaged and signed into security tokens |
| eTMF | Electronic Trial Master File, a repository of documents used or generated in the course of a clinical trial |
| Events | Activity in the course of a trial, planned or unplanned, that indicate certain additional documents need to be submitted to the eTMF |
| Hashing | The transformation of a string of characters into a shorter value or key that is used to index and retrieve items in a database |
| JSON | Javascript Object Notation, a data interchange format used for representing simple data structures and objects in Web browser-based code |
| Metadata | Pieces of information giving related information about a document |
| Milestones | Key dates in the course of a trial that PhlexTMF uses to calculate completeness and associated document requirements |
| Placeholder | An entry in the eTMF indicating a particular document is expected for this artifact or sub-artifact |
| Protocol | A document that describes how a clinical trial will be conducted, and in the context of PhlexTMF a means of identifying individual studies |
| REST | Representational State Transfer, an architecture for developing Web services |
| Sub-artifact | A particular type of document that can be uploaded to the eTMF. A sub-artifact exist when there are several types that can be associated with a particular artifact in the study |