Abstract: A kit for determining ctDNA concentration and a method for determining ctDNA concentration is disclosed, wherein the method comprising dissolving extracted ctDNA in Tris-HCl buffer with pH>7.0 and adding into the buffer 2,7-bis(1-methyl-4-vinylpyridine)-9-ethylcarbazole iodised salt as a molecular probe, calculating the concentration of ctDNA in the solution by measuring the Fluorescence intensity of the solution. It has extremely high sensitivity in the determination of 0 ?g/ml˜50 ?g/ml ctDNA solution.

Abstract: A kit for determining ctDNA concentration and a method for determining ctDNA concentration is disclosed, wherein the method comprising dissolving extracted ctDNA in Tris-HCl buffer with pH>7.0 and adding into the buffer 2,7-bis(1-methyl-4-vinylpyridine)-9-ethylcarbazole iodised salt as a molecular probe, calculating the concentration of ctDNA in the solution by measuring the Fluorescence intensity of the solution. It has extremely high sensitivity in the determination of 0 ?g/ml˜50 ?g/ml ctDNA solution.

Abstract: A service framework wherein a markup language based software development kit that maps an object model of a service SDK to a set of markup language schemas. On the basis of the markup language schemas the service may convert any service data object into a markup language string, and vice versa. All data exchange requests and responses are in the format of markup language strings such that web services perform data exchange with the service through standard internet technologies, for example JavaScript and SOAP. The UI of the service is abstracted to a markup language structure. The definition of interaction points of web services are also standardized, such that other services may customize the service user interface through a simple markup language string, passed via custom code. In this way, deployment and enlightening of web based services in the service may be controlled from the server or web service side.

Abstract: A data transaction system allows performing a transaction related to a data unit, where the data unit can be independently saved and retrieved, from an upper layer to a storage layer without causing a database deadlock related to the data unit in the storage layer. The data transaction system uses a first stage for transferring the data unit from the upper layer to the storage layer, and a second stage to save the transferred data unit independent of the upper layer. The data transaction system guarantees data consistency in applications using multiple layer architecture and at the same time avoiding cost and inefficiencies related to a database deadlock scenario.

Abstract: A general provider of a core registration service provides registration services to a special service provider. In one implementation, a first party presents a user registration form to a second party on behalf of a third party The first party receives registration provisioning data from the third party, which is used by the first party to generate a custom registration form. Responsive to receiving a request from a second party to register for a specialized service provided by a third party, the first party communicates the custom registration form to second party.

Abstract: A data transaction system allows performing a transaction related to a data unit, where the data unit can be independently saved and retrieved, from an upper layer to a storage layer without causing a database deadlock related to the data unit in the storage layer. The data transaction system uses a first stage for transferring the data unit from the upper layer to the storage layer, and a second stage to save the transferred data unit independent of the upper layer. The data transaction system guarantees data consistency in applications using multiple layer architecture and at the same time avoiding cost and inefficiencies related to a database deadlock scenario.

Abstract: A general provider of a core registration service provides registration services to a special service provider. In one implementation, a first party presents a user registration form to a second party on behalf of a third party The first party receives registration provisioning data from the third party, which is used by the first party to generate a custom registration form. Responsive to receiving a request from a second party to register for a specialized service provided by a third party, the first party communicates the custom registration form to second party.