Search PubMed⌕ Search

Biomedical subjects

B LaRue

Publications and source records attributed to B LaRue.

4 recordsLinked to original sources

Health care delivery reorganization innovative outcome: universal computerized patient identification.

Twenty-three large employers in the Minneapolis/St. Paul area formed the business health care action coalition group (BHCAC) to obtain medical care for their employees and families. Requirements of BHCAC included: 1) detailed reporting of outcomes of both preventive and standard health care, 2) development and successful implementation of practice guidelines, and 3) development of a functioning automated medical record. The coalition was contracted to meet these requirements. A nonprofit foundation--the Institute for Clinical Systems Integration (ICSI)--was formed and the data standards committee created. To ensure registration information transmitted by network would be attached to the correct patient's computer file; a standardized registration data set was agreed upon to be recorded in a uniform manner. This innovative change has allowed, encouraged, and required that clinical data be transferable electronically among organizations. The following are the ICSI data standard requirements for ICSI member organizations: the Health Level 7 (HL7) is to be used for data transmission [1]. Fields to be used include: 1) Social Security Number (SSN): The SSN was chosen as the patient identifier for the reasons listed in [2]. Record the official SSN assigned by the Social Security Administration; record a pseudo-SSN if a social security number is not available following the Veterans Administration (VA) Hospital algorithm. 2) Name: Use the American National Standards Institute (ANSI) Healthcare Informatics Standards Planning Panel (HISPP) and Message Standards Developers Subcommittee (MSDS) Standard for representation of a person's name [3]; completely record all of the person's legal name (including any punctuation, hyphenated and double last names); nicknames and appellations are to be recorded separately; salutations and suffixes are optional, but must be placed in separate computer fields from other name parts. 3) Gender: Allowable values include FEMALE, MALE, OTHER, UNKNOWN. 4) Date of Birth: Include the day, month, year (including century); permitted is approximate or estimated birth dates provided they are indicated as such. Use the ANSI HISPP MSDS standard for date representation [4]. 5) Address: Record at least one address; multiple addresses desirable identified by type or usage (i.E., home, business, office). Allow two or more lines for street, city, U.S. state or Canadian Province; identify by standard two-letter postal abbreviation--zip code (at least 5-digits, preferably 9) or postal code and country. 6) Home ID or Medical Record Number (MRN): Record if different than Social Security Number.

Female↗

The evolution of multi-isoacceptor tRNA families. Sequence of tRNA Leu CAA and tRNA Leu CAG from Anacystis nidulans.

Two leucine tRNAs from the cyanophyte Anacystis nidulans have been isolated, and their complete nucleotide sequences have been determined by combining data from oligonucleotide fingerprints and sequencing gels. The two sequences are 87 nucleotides long, have the anticodons CAA and CAG, and differ from each other at a total of 28 positions. They have been compared to other known tRNA Leu sequences and incorporated into a phylogenetic tree comprising prokaryotic and chloroplastic tRNA Leu sequences. Mutations inferred from the tree show that some parts of the tRNA molecule are highly variable (the extra arm and the acceptor stem) while others are much more conserved (the D and T arms). The topology of the tree supports the idea that blue-green algae and chloroplasts share a common prokaryotic ancestor and show a basic divergence between XAA and XAG anticodon-containing tRNAs, suggesting that these two subfamilies result from an ancient gene duplication. Finally, comparison of this phylogenetic tree with those of other multi-isoacceptor tRNA families shows no common scheme, which may be due to independent refinement of codon-reading patterns in different tRNA families.

Base Sequence↗

The evolving tRNA molecule.

The study of tRNA molecular evolution is crucial to understanding the origin and establishment of the genetic code as well as the differentiation and refinement of the machinery of protein synthesis in prokaryotes, eukaryotes, organelles, and phage systems. The small size of the molecule and its critical involvement in a multiplicity of roles distinguish its study from classical protein molecular evolution with respect to goals and methods. Here, the authors assess available and missing data, existing and needed methodology, and the impact of tRNA studies on current theories both of genetic code evolution and of the evolution of species. They analyze mutational "hot spots", the role of base modification, synthetase recognition, codon-anticodon interactions and the status of organelle tRNA.

Animals↗

Convergence and minimal mutation criteria for evaluating early events in tRNA evolution.

The convergence of ancestral sequences independently constructed from different branches of a phylogenetic tree can be used as a test of homology of data sequences. This criterion has shown that all phenylalanine tRNAs are related to a common ancestor, whereas eukaryotic and prokaryotic tyrosine tRNAs may have independent origins. All glycine tRNAs share a common ancestor. The glycine tRNA family splits according to the purine or pyrimidine nature of the first anticodon base prior to the divergence of eukaryotes and prokaryotes. The structural similarity between some prokaryotic glycine and and valine tRNAs is the result of their derivation from a common ancestor that existed previous to the divergence of the different glycine tRNAs. These results support models of genetic code evolution involving the incremental elaboration of earlier, simpler codes.

Animals↗