Coding Reference System Data

The interim code number field is intended to prevent re-copying data and thereby reduces transcription errors. It also reduces delay of data entry because a user of the system can assign interim numbers to his data set ranging from 097000 to 097999 while RSC sheets are edited and analyzed for assignment of permanent code numbers into the general RKC system. The RKC system uses the 100000 to 199999 series of numbers (see Fig. 1, and Sections 101-106). 

The following fields of information must be recorded 1) reference strain number or designation 2) suffix 3) interim code number 4) reference strain taxon 5) producer or manufacturer of test materials 6) determinant 7) technique or method 8) literature reference or comments on technique and 9) RSC number. 

The reference strain designation is recorded on all RSC sheets. We have previously defined a reference strain as the organism from which a product was obtained and used as 

The reference strain taxon field is used to record the generic name and specific epithet of the reference strain. This is essential, if the names are known, to avoid confusion. If the names are not known, distinctive operational names or symbols must be assigned to all reference strains. For example, an antiserum prepared against a Salmonella strain might be included in a number of tests developed for the genus Escherichia. Although components of earlier coded data might exist in both the Escherichia and the Salmonella sections of the RSC, the reference strain taxon would be Salmonella, not Escherichia. Computer searches of the reference strain number and the reference strain taxon fields would determine if the RSC contains any information about specifically numbered or named reference strains. 

The producer or manufacturer field records the name of the laboratory which produced the tested product. The producer could be a commercial source, a government agency, or a private or academic laboratory. 

---

Specific directions for coding reference system data are given in the "Directions for Coding Data. ... 

Reference Systems may be unique to a particular laboratory because antisera, extracts, etc. are prepared in t at laboratory by its own methods and from its own laboratory strains which that laboratory often uses as reference strains. An example of this are DNA or RNA extraction and testing procedures for homology studies. We present here a standardized format that facilitates design of coding data sets to record reference strain information. 

What we present here are examples of what can be done with reference system coding and is not meant to be exhaustive. Particularly, we have omitted areas in states of rapid flux, such as monoclonal antibodies and identification by nucleic acid hybridizations, probes and sequences. These are examples of areas of relative newness and ferment in which coding problems are being seriously investigated internationally in such endeavors as the CODATA/IUIS Hybridoma Data Bank (Bussard et al, 1985) and various gene sequence data banks. 

The protective systems and their corresponding corrosion data are available in the relevant overseas codes for reference. These data are not applicable in Indian specific context as atmospheric corrosion is location specific. Atmospheric corrosion is the frontier research area where limited work has been carried out as it comprises with three phases (solid/atmospheric/liquid environment). Therefore it is significant to study the rust on MS and WS as well as coated steels in a given atmospheric environments. This is important for the selection of more suitable materials as well as for the safety of structures, including the realisation of essential economic effect. 

The relevance of photonics technology is best measured by its omnipresence. Semiconductor lasers, for example, are found in compact disk players, CD-ROM drives, and bar code scaimers, as well as in data communication systems such as telephone systems. Compound semiconductor-based LEDs utilized in multicolor displays, automobile indicators, and most recendy in traffic lights represent an even bigger market, with approximately 1 biUion in aimual sales. The trend to faster and smaller systems with lower power requirements and lower loss has led toward the development of optical communication and computing systems and thus rapid technological advancement in photonics systems is expected for the future. In this section, compound semiconductor photonics technology is reviewed with a focus on three primary photonic devices LEDs, laser diodes, and detectors. Overviews of other important compound semiconductor-based photonic devices can be found in References 75—78. 

Computer applications allow for defining and managing several important nonclinical data types that are managed by the system itself. Such data are referred to as metadata or control data. These are information such as domain-specific descriptions, application conditions, parameters, and methods in a repository. Control data fields can be part of the data collection forms or in system-defined tables. Some of these control fields include electronic signatures, form status, transmission date, transmission number, field completed, and memo fields (large text format). The database contains tables for reference ranges, visit schedule, form schedule, labels, and drug codes. 

To create our terminology containing both internal terms and external terms we semiautomatically extract terms from available external resources (e.g., MeSH, EMTREE, UniProt). Then we fit the extracted terms to our data structure and preserve the reference to the source system because sometimes terms are very specific to certain databases. We refer to the terms specific to a database as local terms. These local terms are stored in a dedicated data structure, the Metastore. It must be noted that we refer to accession codes and identifiers used in databases such as UniProt, RefSeq, and GO as local terms (see Tables 31.1 and 31.2). 

Conditions (2.76) and (2.77) define independence of the design from rotation of coordinates. When selecting the null/centerpoints points (points in experimental center) take into consideration a check of lack of fit of the model, an estimate of experimental error and conditions of uniformity [37]. Centerpoints are created by setting all factors at their midpoints. In coded form, centerpoints fall at the all-zero level. The centerpoints act as a barometer of the variability in the system. All the necessary data for constructing the rotatable design matrix for k<7 are in Table 2.137. This kind of designing is called central, because all experimental points are symmetrical with reference to the experimental center. This is shown graphically for k=2 and k=3 in Fig. 2.40. 

There are no detailed specihcation documents for any of the computerized process control systems that contain sufficient information on how these systems/software were represented and developed. The only specification documents made available and referred to as the design document were the system specifications however, these documents only provide a high-level explanation of what the systems do. They lack sufficient detailed description of specihc and complete data structure, data control flow, design bases, procedural design, development standards, and so on to serve as the model for writing code and to support future changes to the code. [FDA 483, 2000]... 

The management and use of the system, and related reference data (e.g., laboratory reference ranges and coding dictionaries), should be controlled by Standard Operating Procedures. Such procedures should include taking data extracts, possibly as predefined reports. Extracts should be validated to demonstrate they correctly identify, combine/merge, and report data requested. At the system level the functionality of a reporting system should ensure that ... 

---