I agree that this site is using cookies. You can find further informations
here
.
X
Login
Merkliste (
0
)
Home
About us
Home About us
Our history
Profile
Press & public relations
Friends
The library in figures
Exhibitions
Projects
Training, internships, careers
Films
Services & Information
Home Services & Information
Lending and interlibrary loans
Returns and renewals
Training and library tours
My Account
Library cards
New to the library?
Download Information
Opening hours
Learning spaces
PC, WLAN, copy, scan and print
Catalogs and collections
Home Catalogs and Collections
Rare books and manuscripts
Digital collections
Subject Areas
Our sites
Home Our sites
Central Library
Law Library (Juridicum)
BB Business and Economics (BB11)
BB Physics and Electrical Engineering
TB Engineering and Social Sciences
TB Economics and Nautical Sciences
TB Music
TB Art & Design
TB Bremerhaven
Contact the library
Home Contact the library
Staff Directory
Open access & publishing
Home Open access & publishing
Reference management: Citavi & RefWorks
Publishing documents
Open Access in Bremen
zur Desktop-Version
Toggle navigation
Merkliste
1 Ergebnisse
1
Why say "statistically significant" rather than just "signi..:
Fingerhut, Abe
;
Wexner, Steve
;
Behrns, Kevin
...
Surgery. 172 (2022) 4 - p. 1039-1040 , 2022
Link:
https://doi.org/10.1016/j.surg.2022.08.019
RT Journal T1
Why say "statistically significant" rather than just "significant"? a plea to rid the medical literature of linguistic ambiguity
UL https://suche.suub.uni-bremen.de/peid=cr-10.1016_j.surg.2022.08.019&Exemplar=1&LAN=DE A1 Fingerhut, Abe A1 Wexner, Steve A1 Behrns, Kevin A1 Arrezo, Alberto A1 Buhler, Leo A1 Francis, Nader A1 Keller, Deborah S. A1 Knoefel, Wolfram A1 Salminen, Paulina A1 Swanstrom, Lee A1 Winter, Des PB Elsevier BV YR 2022 SN 0039-6060 JF Surgery VO 172 IS 4 SP 1039 OP 1040 LK http://dx.doi.org/https://doi.org/10.1016/j.surg.2022.08.019 DO https://doi.org/10.1016/j.surg.2022.08.019 SF ELIB - SuUB Bremen
Export
RefWorks (nur Desktop-Version!)
Flow
(Zuerst in
Flow
einloggen, dann importieren)