"... In PAGE 7: ... We shall work with a syntax-directed formulation of the Damas-Milner polymorphic type assignment system inspired by the static semantics of Standard ML [25]. The rules given in Table1 de ne a formal system for deriving judgements of the form ; ` e : , expressing that the expression e may be assigned the monotype in context ;. The rules are parametric in a signature , whichweleave implicit.... In PAGE 7: ... The rules are parametric in a signature , whichweleave implicit. We often write ; ` e : ,orjuste : when ; is empty, to mean that this typing judgement is derivable in accordance with the rules of Table1 . An expression e is said to be well-typed in a context ; i there exists a suchthat ; ` e : .... In PAGE 7: ... An expression e is said to be well-typed in a context ; i there exists a suchthat ; ` e : . Some of the rules given in Table1 make use of auxiliary notions that merit further explanation. Rule var makes use of the polymorphic instance relation whichisde nedtoholdi is a polytype of the form 8t 1 : .... In PAGE 7: ...We sometimes abbreviate Close ; ( ) to just Close( ) when ; is the empty context. The formal system of Table1 is clearly a subsystem of the system given by Damas and Milner [4] in the sense that if ; ` e : is derivable in the system of Table 1, then it is derivable in Damas and Milner apos;s system. Conversely,if;` e : is derivable in Damas and Milner apos;s system, then ; ` e : is derivable in the system of Table 1 whenever .... In PAGE 7: ...We sometimes abbreviate Close ; ( ) to just Close( ) when ; is the empty context. The formal system of Table 1 is clearly a subsystem of the system given by Damas and Milner [4] in the sense that if ; ` e : is derivable in the system of Table1 , then it is derivable in Damas and Milner apos;s system. Conversely,if;` e : is derivable in Damas and Milner apos;s system, then ; ` e : is derivable in the system of Table 1 whenever .... In PAGE 7: ... The formal system of Table 1 is clearly a subsystem of the system given by Damas and Milner [4] in the sense that if ; ` e : is derivable in the system of Table 1, then it is derivable in Damas and Milner apos;s system. Conversely,if;` e : is derivable in Damas and Milner apos;s system, then ; ` e : is derivable in the system of Table1 whenever .Thus all and only the monotypes derivable for a given term in Damas and Milner apos;s system are derivable in the system considered here.... ..."

"... In PAGE 55: ... and the functions of the required support system have been documented in detail t31; This study was done using many of the principles developed in [I] and [2]; The proposed automated medical record system has been called quot;The Family Systemtt. and it is this application which will be analyzed; Since the proposed system is moderately large, much use is made of tables during the exposition of the design process; FILES FOR THE FAMILY SYSTEN The Family System is envisaged to have 29 data files and several auxiliary index files [3]; The data files are summarized in Table3 -1: The summary provides An estimate of the size of the file: n; The number and total length of all fixed fields: af , Rf; The number and both average and maximum total length of ... In PAGE 57: ...fields; and the size: n(min, avg, max), an, Rn; The nests themselves are denoted using a hierarchical number in^ scheme: entity relation file. level I nest file, second and lowest level nest file: p, p;q, p;q;r The third file (Patient) has multiple record subtypes, containing optional and transient data; These files are denoted 3a and 3b; The length for various element types defined for the Family System is estimated as shown in Table3 -2; Groups of elements are taken in terms of multiple integer bytes; The table does not include any structural non-essential data elements; The estimates are based on data provided for the Family System [3], from the AANRS Study [2], and from statistics presented in [I]; The expected size of the files was verified by Dr; John Dervin of the Family Practice Center; and is shown in Table 3-3; Table 3-2 Lensth of Data Element Types Data-type V(min).,V(avg) ~(max) Reference Name Address Telephone Telephone Note Date Time Sex Flags Response Diglts (individual) 22 (business) 18 2 chars bits bit bits bytes bytes bgtes bytes bytes bytes [ : pit30 and ?:p;ll281 Hislll [2:p;99 and 2:vo1;2 CDB p;21] [3:p;81 I ~3:p;ai I ... In PAGE 57: ...fields; and the size: n(min, avg, max), an, Rn; The nests themselves are denoted using a hierarchical number in^ scheme: entity relation file. level I nest file, second and lowest level nest file: p, p;q, p;q;r The third file (Patient) has multiple record subtypes, containing optional and transient data; These files are denoted 3a and 3b; The length for various element types defined for the Family System is estimated as shown in Table 3-2; Groups of elements are taken in terms of multiple integer bytes; The table does not include any structural non-essential data elements; The estimates are based on data provided for the Family System [3], from the AANRS Study [2], and from statistics presented in [I]; The expected size of the files was verified by Dr; John Dervin of the Family Practice Center; and is shown in Table3 -3; Table 3-2 Lensth of Data Element Types Data-type V(min).,V(avg) ~(max) Reference Name Address Telephone Telephone Note Date Time Sex Flags Response Diglts (individual) 22 (business) 18 2 chars bits bit bits bytes bytes bgtes bytes bytes bytes [ : pit30 and ?:p;ll281 Hislll [2:p;99 and 2:vo1;2 CDB p;21] [3:p;81 I ~3:p;ai I ... In PAGE 59: ...The files presented by the Family System are organized to satisfy the perceived functional needs of the medical record applications; This means that all data attributes are assigned to specific files using conventional progra~ning design procedures; The files, however, exhibit semantic relationships among each other through the use of shared attribute domains; The files themselves are furthermore complex in the sense that they are not in first-normal-form; In order to present the data base model in a form which provides guidance to the design process, the files for the Family System will be normalized; In order tc derive the interrile rs~laLi.onships, the principal attributes of all files are listed alphabetically in Table3 -4; With each attribute the domain, the data type, and the file usage is indicated; Attributes which have a matching domain, but are named differently; are cornputstionally comparable, but ... In PAGE 63: ...A first-order normalization of the 32 Family System Files described in Table3 -1 extracts the nested structures and places them into distinct files; There are 25 nests and two auxiliary files so that the Family System in first-normal form comprises 57 files; In practice some of these nest files can be avoided by designating a fixed number of fields for the nest in the parent entity file as shown in Figure 2-2; The degree to which nests can be omitted depends on the efficiency of the file compression support; Prime candidates for denesting are the following files: 1;l Guarantors - small and low n(max) of repeating entries 4;1 Pap Smears - 11 11 11 II II II 11 4;2 Crug Allergies - quot; 11 11 II 11 11 II 10 ;0 Flowsheet - small flag and few entries 13;1 Day Sheet Patients - few records and high density 20;l Family member - small size of repeating field A sample calculation of the denesting tradeoff for the first of these files (1;1 ... In PAGE 68: ...The remaining files can now be reviewed for structural inter-relationships and redundancies; Linkage keys which have been identified in the 34 primary files are given as the ruling part for these files in Table3 -5; This table also indicates which of these files have a NULL dependent part (1;1, 5, 8, 9, lo), these files were apparently defined in [31 for their utility in providing a linkage, and are hence not an essential part of the data base model; There remain a number of files with identical ruling parts; These files represent different functional needs and were hence defined distinctly; In the model of the data base, however, these files are best combined; The original files are then represented ... In PAGE 69: ... medication code, date non.drugtEerapy, date floV sheet-type : gt; NUL date- date date date, problem-number date, problem-number, 3 code patient-number, aate; problem-number , test code patient-numbeF, date, problem-number , problem-note-number date, office date, office; patient-number - off ice office; patient-number * These files will be eliminated if denesting is carried out as lndlcated earller; In file 2; 1 (Family ember) the catenation of apos;family-number apos; and apos;family-member-number apos; forms the apos;~atient-number apos;, so that this file can also be represented as a segment dependent on the ruling part of apos;patient-number apos;; The new relations created in this manner are listed in Table3... In PAGE 74: ...role; Important linkage domains found in Table3 -4 are Patient name Patient number Provider name Office Family number Problem number Service code Therapy code Dollars Medication code Some redundancy is evident; In order to simplify updating, it may be desirable to define certain attributes as primary, and to update the redundant copies of these attributes asynchronously; Candidate attributes for such a division are the objective medical data as obtained during a patient visit; The primary relation for such data would be the Patient Visit file; The Problem List File; Flow-Sheets; Preventive Care records, etc; could be updated overnight; Redundancy for protection of data is maintained through the service files as the Transaction Log; Associations: An important primitive function for a data base is the ability to associate data from file with data from another file; Associations may be created dynamically through use of the Join operation, or may be bound permanently; A permanent association can contain unlimited dependent-part information; dynamic association only carries information derived from the joining ... In PAGE 78: ...transformed into a manipulatable model; This model was then inspected for function, redundancy; semantic relationships, and consistency; A number of transformations were performed to clarify and simplify the data base model; This model is now suitable for a performance-oriented design effort; Table 3-8 summarizes the transformations performed; The design of the Family System; as developed from an analysis of the service requirements, described 58 distinct files; The data base model now consists of 20 primary entity files (2 of these can be denested) 7 referenced entity files 4 lexicons 9 service files Rzlationships among the entity files are documented in Table3... In PAGE 80: ...hich is to support the Fa.m.i.1t.y System, several design techniques can be employed; These can be categorized as follows: File Organization Choices: pile, sequential, indexed-sequential, indexed, direct or ring; File Partitioning Choices: One record per tuple, or one record per segment; Use 01 apos; auxiliary access files; In practice all three choices will be employed; In order to establish a baseline; the nerf apos;ormance of a pile of unpartitioned records without auxiliary access files will be presented initially; Table 4-1 summarizes the basic relations and their parameters, as derived from the data presented in Table3 -1; Since all files are evaluated independently, the size of the ruling part has been added to the recordsize; The primary files summarized in Table 4-1 do not include the lexicons and referenced entity files; The space required for these is presented in Table 4-3 using the assumptions that they ... In PAGE 84: ...n aspect of information services to the Family System and as indicated in [ 1 :Ch;5; 1 I, the usage of the Family System for information purposes will depend on the quality of services to clinic, research and educational management; The load due to this latter type of usage can be expected to be considerably less and not coincide with times of high clinic activity; This aspect will hence not now be evaluated; The services that a.re to be provided are selected from [2:SeC;4C], and usage qualities are provided by [3:Ch;2] and Table3... In PAGE 104: ...T r log (n R/U) 1 (s+r+B/t) + 1/2 0/5 ~/t apos; F 2 Indexed-Sequential: An indexed-sequential file organization provides faster access through a tree search of key values [I:Ch;3;2;31; Its efficiency depends on a small number of updates per file; Some additional space, SI; is required; This space is a function of the fanout ratio, y, [I:Ch;3;3;1], blocking; and number of records; n, for a two-level (x=2) index; File 12;l only requires one level; The values for Rr depend on the size of the ruling part and are given in Table3 -7; T =s + (2 + Pov (1+1/2~ov)(r+B/t) ; Pov = o/(n+o) F T = ( R/B + 2 Pov (1-R/B) )(r+B/t) (two buffers are available) ... ..."

"... In PAGE 15: ...8. Table6 shows the average values for F0.2 by topic and system type with strict judgments.... ..."

"... In PAGE 15: ...8. Table6 shows the average values for F0.2 by topic and system type with strict judgments.... ..."

"... In PAGE 8: ... For branching ratio and cross-section measurements, precisely measured e ciencies are crucial. The principal trigger requirements for each data set are listed in Table2 . In addition to the key physics events, a number of other events are recorded for uses such as luminosity determination, detector calibration, beam monitoring, and trigger performance studies.... In PAGE 11: ...Backgrounds and Trigger Rates The trigger architecture and selection algorithms designed to meet the requirements are based on simulation studies of the physics, backgrounds, and the BABAR detector. The total trigger output rate is the sum of the rates for the physics and diagnostic processes listed in Table2 and the rates for the background processes described in the TDR, Chapter 12. The main background processes that produce charged tracks traversing the drift chamber and calorimeter are: physics backgrounds from asymmetric Bhabhas with only one detected charged track and two-photon events below energies of interest; beam-induced backgrounds from hadronic interactions of lost beam particles, electromagnetic interactions of lost beam particles, and beam-gas collisions at the interaction point; and cosmic rays.... In PAGE 20: ... The following tables show both trigger e ciencies over the full space and trigger e ciencies within the geometric acceptance. I-H-2 Benchmark E ciencies and Background Rates for Level 1 An inclusive global trigger de nition that e ciently selects each of the processes in Table2 while rejecting some backgrounds requires a minimum of two charged tracks in the drift chamber, two M clusters, or one E cluster in the backward direction. The orthogonality of the two rst criteria makes it straightforward to measure the e ciency of the lter.... In PAGE 27: ... In this document, the rst two categories are investigated for the whole multi-level trigger system, in sections III-A and III-B, while the latter two are discussed rst for the Level 1 trigger, in sections III-C and III-D, and then again, in sections III-E and III-F, for the Level 3 trigger. III-A Physics Requirements for the Complete Trigger System As shown in Table2 , data sets to be selected are either directly related to the physics goals or to other essential requirements such as calibration and monitoring.... ..."

"... In PAGE 8: ... For branching ratio and cross-section measurements, precisely measured e ciencies are crucial. The principal trigger requirements for each data set are listed in Table2 . In addition to the key physics events, a number of other events are recorded for uses such as luminosity determination, detector calibration, beam monitoring, and trigger performance studies.... In PAGE 11: ...Backgrounds and Trigger Rates The trigger architecture and selection algorithms designed to meet the requirements are based on simulation studies of the physics, backgrounds, and the BABAR detector. The total trigger output rate is the sum of the rates for the physics and diagnostic processes listed in Table2 and the rates for the background processes described in the TDR, Chapter 12. The main background processes that produce charged tracks traversing the drift chamber and calorimeter are: physics backgrounds from asymmetric Bhabhas with only one detected charged track and two-photon events below energies of interest; beam-induced backgrounds from hadronic interactions of lost beam particles, electromagnetic interactions of lost beam particles, and beam-gas collisions at the interaction point; and cosmic rays.... In PAGE 20: ... The following tables show both trigger e ciencies over the full space and trigger e ciencies within the geometric acceptance. I-H-2 Benchmark E ciencies and Background Rates for Level 1 An inclusive global trigger de nition that e ciently selects each of the processes in Table2 while rejecting some backgrounds requires a minimum of two charged tracks in the drift chamber, two M clusters, or one E cluster in the backward direction. The orthogonality of the two rst criteria makes it straightforward to measure the e ciency of the lter.... In PAGE 27: ... In this document, the rst two categories are investigated for the whole multi-level trigger system, in sections III-A and III-B, while the latter two are discussed rst for the Level 1 trigger, in sections III-C and III-D, and then again, in sections III-E and III-F, for the Level 3 trigger. III-A Physics Requirements for the Complete Trigger System As shown in Table2 , data sets to be selected are either directly related to the physics goals or to other essential requirements such as calibration and monitoring.... ..."

"... In PAGE 11: ...Backgrounds and Trigger Rates The trigger architecture and selection algorithms designed to meet the requirements are based on simulation studies of the physics, backgrounds, and the BABAR detector. The total trigger output rate is the sum of the rates for the physics and diagnostic processes listed in Table2 and the rates for the background processes described in the TDR, Chapter 12. The main background processes that produce charged tracks traversing the drift chamber and calorimeter are: physics backgrounds from asymmetric Bhabhas with only one detected charged track and two-photon events below energies of interest; beam-induced backgrounds from hadronic interactions of lost beam particles, electromagnetic interactions of lost beam particles, and beam-gas collisions at the interaction point; and cosmic rays.... In PAGE 18: ... The following tables show both trigger e ciencies over the full space and trigger e ciencies within the geometric acceptance. I-H-2 Benchmark E ciencies and Background Rates for Level 1 An inclusive global trigger de nition that e ciently selects each of the processes in Table2 while rejecting some backgrounds requires a minimum of two charged tracks in the drift chamber, two M clusters, or one E cluster in the backward direction. The orthogonality of the two rst criteria makes it straightforward to measure the e ciency of the lter.... In PAGE 24: ... For the purpose of this document, the rst two categories are investigated for the whole multi- level trigger system while the latter two are limited mostly to the Level 1 trigger. III-A Physics Requirements for the Complete Trigger System As shown in Table2 , data sets to be selected are either directly related to the physics goals or to other essential requirements such as calibration and monitoring. III-A-1 Primary Physics Data Samples A summary of physics e ciency requirements are given in Table 9.... ..."

"... In PAGE 11: ...Backgrounds and Trigger Rates The trigger architecture and selection algorithms designed to meet the requirements are based on simulation studies of the physics, backgrounds, and the BABAR detector. The total trigger output rate is the sum of the rates for the physics and diagnostic processes listed in Table2 and the rates for the background processes described in the TDR, Chapter 12. The main background processes that produce charged tracks traversing the drift chamber and calorimeter are: physics backgrounds from asymmetric Bhabhas with only one detected charged track and two-photon events below energies of interest; beam-induced backgrounds from hadronic interactions of lost beam particles, electromagnetic interactions of lost beam particles, and beam-gas collisions at the interaction point; and cosmic rays.... In PAGE 19: ... The following tables show both trigger e ciencies over the full space and trigger e ciencies within the geometric acceptance. I-H-2 Benchmark E ciencies and Background Rates for Level 1 An inclusive global trigger de nition that e ciently selects each of the processes in Table2 while rejecting some backgrounds requires a minimum of two charged tracks in the drift chamber, two M clusters, or one E cluster in the backward direction. The orthogonality of the two rst criteria makes it straightforward to measure the e ciency of the lter.... In PAGE 24: ... For the purpose of this document, the rst two categories are investigated for the whole multi- level trigger system while the latter two are limited mostly to the Level 1 trigger. III-A Physics Requirements for the Complete Trigger System As shown in Table2 , data sets to be selected are either directly related to the physics goals or to other essential requirements such as calibration and monitoring. III-A-1 Primary Physics Data Samples A summary of physics e ciency requirements are given in Table 9.... ..."

"... In PAGE 11: ...Backgrounds and Trigger Rates The trigger architecture and selection algorithms designed to meet the requirements are based on simulation studies of the physics, backgrounds, and the BABAR detector. The total trigger output rate is the sum of the rates for the physics and diagnostic processes listed in Table2 and the rates for the background processes described in the TDR, Chapter 12. The main background processes that produce charged tracks traversing the drift chamber and calorimeter are: physics backgrounds from asymmetric Bhabhas with only one detected charged track and two-photon events below energies of interest; beam-induced backgrounds from hadronic interactions of lost beam particles, electromagnetic interactions of lost beam particles, and beam-gas collisions at the interaction point; and cosmic rays.... In PAGE 19: ... The following tables show both trigger e ciencies over the full space and trigger e ciencies within the geometric acceptance. I-H-2 Benchmark E ciencies and Background Rates for Level 1 An inclusive global trigger de nition that e ciently selects each of the processes in Table2 while rejecting some backgrounds requires a minimum of two charged tracks in the drift chamber, two M clusters, or one E cluster in the backward direction. The orthogonality of the two rst criteria makes it straightforward to measure the e ciency of the lter.... In PAGE 24: ... For the purpose of this document, the rst two categories are investigated for the whole multi- level trigger system while the latter two are limited mostly to the Level 1 trigger. III-A Physics Requirements for the Complete Trigger System As shown in Table2 , data sets to be selected are either directly related to the physics goals or to other essential requirements such as calibration and monitoring. III-A-1 Primary Physics Data Samples A summary of physics e ciency requirements are given in Table 9.... ..."

"... In PAGE 11: ...Backgrounds and Trigger Rates The trigger architecture and selection algorithms designed to meet the requirements are based on simulation studies of the physics, backgrounds, and the BABAR detector. The total trigger output rate is the sum of the rates for the physics and diagnostic processes listed in Table2 and the rates for the background processes described in the TDR, Chapter 12. The main background processes that produce charged tracks traversing the drift chamber and calorimeter are: physics backgrounds from asymmetric Bhabhas with only one detected charged track and two-photon events below energies of interest; beam-induced backgrounds from hadronic interactions of lost beam particles, electromagnetic interactions of lost beam particles, and beam-gas collisions at the interaction point; and cosmic rays.... In PAGE 18: ... The following tables show both trigger e ciencies over the full space and trigger e ciencies within the geometric acceptance. I-H-2 Benchmark E ciencies and Background Rates for Level 1 An inclusive global trigger de nition that e ciently selects each of the processes in Table2 while rejecting some backgrounds requires a minimum of two charged tracks in the drift chamber, two M clusters, or one E cluster in the backward direction. The orthogonality of the two rst criteria makes it straightforward to measure the e ciency of the lter.... In PAGE 24: ... For the purpose of this document, the rst two categories are investigated for the whole multi- level trigger system while the latter two are limited mostly to the Level 1 trigger. III-A Physics Requirements for the Complete Trigger System As shown in Table2 , data sets to be selected are either directly related to the physics goals or to other essential requirements such as calibration and monitoring. III-A-1 Primary Physics Data Samples A summary of physics e ciency requirements are given in Table 9.... ..."