Unique identifier

Abstract: Automatic actions can be obtained through a network using an area of marking medium with machine-readable markings that encode an action/medium identifier. The action/medium identifier identifies an action that can be produced through the network, and also identifies the area of marking medium. For example, it may include a globally unique or network-wide page identifier as well as an action identifier that can be used to produce an action described by data associated with a counterpart digital page. Or it can include both a page identifier and a location identifier, with the location identifier also identifying an action that relates to the page's digital counterpart. Or it can include a document identifier and an action identifier. Or it can be a globally unique or network-wide sticker identifier that can be used to identify a document, a peripheral device, or another object to which the sticker is attached, and that also produces an action through the network.

Abstract: Background Typically, randomization software should allow users to exert control over the different aspects of randomization including block design, provision of unique identifiers and control over the format and type of program output. While some of these characteristics have been addressed by available software, none of them have all of these capabilities integrated into one package. The main objective of the Random Allocation Software project was to enhance the user's control over different aspects of randomization in parallel group trials, including output type and format, structure and ordering of generated unique identifiers and enabling users to specify group names for more than two groups.

Abstract: Vast amounts of data are collected about patients and service users in the course of health and social care service delivery. Electronic data systems for patient records have the potential to revolutionise service delivery and research. But in order to achieve this, it is essential that the ability to link the data at the individual record level be retained whilst adhering to the principles of information governance. The SAIL (Secure Anonymised Information Linkage) databank has been established using disparate datasets, and over 500 million records from multiple health and social care service providers have been loaded to date, with further growth in progress. Having established the infrastructure of the databank, the aim of this work was to develop and implement an accurate matching process to enable the assignment of a unique Anonymous Linking Field (ALF) to person-based records to make the databank ready for record-linkage research studies. An SQL-based matching algorithm (MACRAL, Matching Algorithm for Consistent Results in Anonymised Linkage) was developed for this purpose. Firstly the suitability of using a valid NHS number as the basis of a unique identifier was assessed using MACRAL. Secondly, MACRAL was applied in turn to match primary care, secondary care and social services datasets to the NHS Administrative Register (NHSAR), to assess the efficacy of this process, and the optimum matching technique. The validation of using the NHS number yielded specificity values > 99.8% and sensitivity values > 94.6% using probabilistic record linkage (PRL) at the 50% threshold, and error rates were < 0.2%. A range of techniques for matching datasets to the NHSAR were applied and the optimum technique resulted in sensitivity values of: 99.9% for a GP dataset from primary care, 99.3% for a PEDW dataset from secondary care and 95.2% for the PARIS database from social care. With the infrastructure that has been put in place, the reliable matching process that has been developed enables an ALF to be consistently allocated to records in the databank. The SAIL databank represents a research-ready platform for record-linkage studies.

Abstract: A system and method for implementing an association of business objects without retrieving said objects from a database on which they are stored. A business object in the business cache is provided and an instance of an associated object is stored on a database. An association of the business object with the instance of the associated object is determined. An object identifier is generated containing information including the determination association which is necessary to retrieve the instance of the associated object from the database, wherein the object identifier includes a unique row identifier, an identifier generated by a utility, and a unique string generated from one or more attributes. The object identifier is loaded when the business object starts. A location of the instance of the associated object on the database is determined from the object identifier and the instance of the associated object is retrieved from the database.