Correlation Between the Revised Trauma Score and Injury Severity Score: Implications for Prehospital Trauma Triage
Correlation Between the Revised Trauma Score and Injury Severity Score: Implications for Prehospital Trauma Triage is a paper indexed in ScholarIQ from OpenAlex.
How many citations does Correlation Between the Revised Trauma Score and Injury Severity Score: Implications for Prehospital Trauma Triage have?
Correlation Between the Revised Trauma Score and Injury Severity Score: Implications for Prehospital Trauma Triage has 105 citations in the OpenAlex counts ScholarIQ stores.
When was Correlation Between the Revised Trauma Score and Injury Severity Score: Implications for Prehospital Trauma Triage published?
Correlation Between the Revised Trauma Score and Injury Severity Score: Implications for Prehospital Trauma Triage has 2018 year in the ScholarIQ index.
What is the open-access status of Correlation Between the Revised Trauma Score and Injury Severity Score: Implications for Prehospital Trauma Triage?
Correlation Between the Revised Trauma Score and Injury Severity Score: Implications for Prehospital Trauma Triage has closed oa status in the ScholarIQ index.
What is the DOI of Correlation Between the Revised Trauma Score and Injury Severity Score: Implications for Prehospital Trauma Triage?
The DOI for Correlation Between the Revised Trauma Score and Injury Severity Score: Implications for Prehospital Trauma Triage is on the source record.
What is the PMID of Correlation Between the Revised Trauma Score and Injury Severity Score: Implications for Prehospital Trauma Triage?
The PMID for Correlation Between the Revised Trauma Score and Injury Severity Score: Implications for Prehospital Trauma Triage is on the source record.
What is the OpenAlex record for Correlation Between the Revised Trauma Score and Injury Severity Score: Implications for Prehospital Trauma Triage?
The OpenAlex for Correlation Between the Revised Trauma Score and Injury Severity Score: Implications for Prehospital Trauma Triage is on the source record.