The API enables the creation, updating and consultation of agreement bodies as well as the establishment, updating and consultation of agreement specifications – as templates for agreement bodies. The API provides a standardized mechanism for managing agreements, especially with regard to partnerships between partners. We are in the process of implementing an eTMF system in our company and have had several discussions about the location of financial agreements. I would simply like to receive a guide and/or information on the paths followed by other companies instead of transferring the financial agreements to the eTMF? What is the standard expectation if a financial agreement is maintained outside the eTMF? We are of course aware that if they are kept elsewhere, their location should be highlighted in the TMF management plan, but it would be extremely useful to get some examples of this. Another issue was the global financial agreement for a provider, which covers multiple studies and where they will be stored when they are put online within the eTMF. Hello Ishita, Our corporate policy has always been not to submit financial documents to the eTMF. We use a separate database to record all contracts/budgets and, as you mentioned above, document this place in the specific TMF plans under consideration. If necessary, financially edited documents shall be made available to the auditors. This would also apply to cross-sectoral agreements that may span several studies. Hub is the repository of subscribers with their respective callback URLs. AbstractFacade is a complex implementation, but boilerplate, that should not be modified by developers. Other resource-specific facades should always extend AbstractFacade and are implemented by developers per resource.
The software stack for the TMForum OpenAPI reference implementation is a standard J2EE EJB3 implementation consisting of: persistence.xml, glassfish-web.xml and glassfish-resources.xml are standard but important configuration files that manage all application settings. You need to change these settings based on the type of database they selected (MySQL or Apache Derby), database connection information, application configuration path, and so on. With all path parameters, the resource path must be fully compliant with the Swagger documentation and API specification for each API, as well as the respective resources and verbs. Services use and produce JSON and call facades to validate, retrieve, and store data. General utilities support implementation by providing utility functions that can be called by the facade and resource levels. Home › Forums › General Discussion Forum › Financial Agreement in event tables eTMF contain event history for the associated resource. An event is logged in the event table, and then every subscriber registered in the hub is notified of the event. My comments apply to any document that is considered part of the TMF but kept outside the main eTMF/TMF. .
Another point – if you keep it in your ETMF, there probably needs to be a way to limit access to people with a need to know” – because financial information is often considered sensitive and access may be limited to a subset of eTMF users. The software architecture is multi-layered to address the separation of concerns. The application supports an event handling mechanism in which lists can subscribe to be notified of resource changes. . . .