Frequently Asked Questions
Our PTSF staff have compiled frequently asked questions for you to reference. Do you have a question about basic trauma assessment? Maybe you're looking to better understand basic trauma training?
Trauma Registry related FAQs will be updated here weekly by PTSF staff. Please take the date of the post into consideration. As you know, changes occur frequently in the PTOS dataset.
There are no guidelines in the PTOS Manual that tell you not to use PACU as a post ed location, it just isn’t in the current menu as an option. I recommend recording 15, other, for Post ED Destination and specifying PACU in the Specify field that opens.
For Procedure Location, you can record 13, PACU.
You are not to use data from the referring facility here. You must record the first height and weight documented within 24 hours of ED or hospital arrival at your facility.
You are correct that these are optional elements that are NOT required to be completed. PTSF will work with ESO to modify or remove this check.
You cannot record both a controlled and an uncontrolled rate in PTOS. The idea is that you are capturing the initial vitals. For respiratory rate, you are capturing the initial respiratory rate, which will be either controlled or uncontrolled.
This scenario falls under W01.0 (tripping over animal). W01.0 does fall within the accepted code range for our solitary hip fracture exclusion. Therefore, based on the information provided, this patient would meet the exclusion and would NOT be captured as PTOS.
Can you please clarify the pre-existing history of head trauma? The term TBI doesn’t need to be specifically documented, correct? If we have documentation of SAH, SDH, concussion, etc. is that sufficient? What about closed head injury?
You don’t need the term “TBI” if you have a specific diagnosis of brain, skull or scalp injury (can be open or closed) , as long as it caused anything from drowsiness to an intracranial bleed. So just diagnosis of SAH is fine; if you get into milder skull/scalp injury I would want to see that at least drowsiness or concussion symptoms were noted.
Based on the information provided, I believe this patient would meet the isolated hip fracture exclusion and NOT be captured as PTOS. In Appendix 15 of the PTOS Manual there are examples provided. This scenario seems similar to Fall from standing (knocked over/pushed) with an isolated hip fracture, which is non-PTOS. However, if a horse hit the patient causing an injury, that is when you would use W55.1 (contact with horse). If it was the fall that caused the injury, you will want to use the fall code, which does meet the exclusion.
No, I wouldn’t pick up substance abuse. While he does have the abstinence syndrome, it wasn’t his direct use/abuse of substance.
You are correct the abuse coding guidelines within the PTOS Manual instruct you to leave the secondary and tertiary fields blank in situations of suspected abuse. PTSF is working with ESO to remove the incorrect check. For the time being, please enter “/” for n/a in the secondary and tertiary fields and validate the check. PTSF will also correct the guidance within the PTOS Manual.
We recommend to always record the mechanism that caused the most severe injuries first. In this situation, we recommend the mechanism code for the strike by train as the primary and the mechanism for the electrocution as secondary based on the information provided.
In order to capture this as a pre-existing, the patient’s advanced directive to limit life-sustaining treatment must have been present on their person on arrival or already on file at your center.
If it is a closed fracture, blunt injury, you can code hematoma in addition to the fracture. If it is an open fracture or a penetrating injury, you wouldn’t code those associated.
From what you wrote, it sounds like it could be sequela, as they say there is no injury to muscle, but I might ask your doc. Blood loss associated with certain injuries does increase the severity. Did they note any vessel injuries?
Hemorrhagic shock itself isn’t codable.
Interpeduncular cistern does code to brain stem. In the AIS clarification document from October 2019 they have
“Interpeduncular fossa (cistern) basal cisterns code as injury involving hemorrhage in the brainstem;”
The ICD-10 code has hemorrhage of brain stem also.
I would note any specifics related to LOC if you have documentation, as it will assume the LOC nfs otherwise.
If you have an AIS code recorded that falls within the defined coding criteria for these fields, you will need to answer the antibiotic elements as if there is an open fracture present for both PTOS and the NTDB. This criteria is provided by the NTDB/TQIP, and we understand sometimes it is not perfect as some non-open fractures do get included simply based on how they are coded in AIS. PTSF can provide the current list of AIS codes that fall within the criteria.
This could be used to code cerebrum brain swelling. Partial effacement would go to moderate; compressed – 140664.4, while complete effacement would go to severe; absent/obliterated/closed – 140666.5. I wouldn’t use edema unless the provider notes as edema.
Correct. You are to code brain injuries based on what is documented closest to or at 24 hours, or at initial confirmed diagnosis if later than 24 hours. If a head bleed is noted after the first 24 hours, that would be considered the initial confirmed diagnosis and you would capture the injury.
That is correct. As long as the patient is placed on comfort care prior to leaving the ED or meeting another portion of the criteria (LOS, ICU, transfer, etc.) that patient will not be captured as PTOS due to our hospice patient exclusion. The patient in your scenario appears to meet this exclusion.
As an example of a patient that would be captured, if a patient were to be admitted to the ICU and it is later decided to place the patient on comfort care, this patient would be captured as PTOS.
This patient would not qualify as PTOS as the fracture is pathological. There is a separate pathologic and traumatic fracture category in ICD-10. Only traumatic fractures fall within the PTOS ICD-10 inclusion code range.
Being lifted certainly could be a traumatic mechanism; however, in this situation, there was no injury.
In both of your scenarios, since the patient has a diagnosis that falls within our inclusion code range, they should be considered for PTOS. Note, they will need to meet the LOS criteria or another portion of the inclusion criteria before you confirm them as PTOS.
In the documentation provided, it appears to me that the mechanism of injury is cat bite. PTOS inclusion does not consider the mechanism of injury, diagnoses only. There is no specific icd-10 diagnosis code related to the bite itself, such as a laceration code. Since there is no documented diagnosis that falls within the ICD-10 code range for PTOS, the patient should be made nonPTOS.
Yes, if the injury occurs after the patient is in your hospital being treated, then that is not a qualifying injury.
The idea is that those patients are being reviewed through another quality review in your hospital, so are not picked up for PTOS or NTDS.
That’s correct. The patient was discharged home from the ED. She went home and did not meet LOS and so does not qualify as PTOS.
In order for Stepdown or ICU to be qualifying criteria, the patient actually has to go to the unit.
If the patient is in an acute care hospital, and falls, that record won’t meet inclusion criteria. In other locations such as a SNF, residential care, or a psychiatric center that is not an acute care hospital, those do qualify for inclusion.
No, if the injuries are due to the disease then you won’t pick it up. Another example would be osteophytes on a vertebra. You can pick up a fractured vertebra, but not a fractured osteophyte.
It all comes down to the ICD-10-CM diagnosis code. Lacerations do typically fall within our ICD-10-CM inclusion code range. It is the superficial abrasions and contusions that are excluded.
If the patient has an ICD-10-CM diagnosis code that falls within the PTOS inclusion code range AND the patient meets another portion of the criteria (i.e. LOS, transfer, etc.), the patient should be captured as PTOS.
Treatment vs no treatment or medical admissions no longer play a role in determining inclusion.
Note we are discussing this further at registry committee. However, the current guidance should be followed.
Appendix 15 are examples for our solitary hip fracture exclusion. In order for a patient to meet this exclusion the patient must sustain a solitary hip fracture from a fall on the same level. It does not sound like from the information you provided that the patient fell. Therefore, the patient would not meet the exclusion.
Based on the information you provided, the patient should be considered for PTOS. The patient must have an injury diagnosis that falls within the ICD-10 inclusion code range AND meet another portion of the criteria (i.e. LOS, ICU admission, transfer, etc.).
If this second encounter is based on the same injury due to the fall as the first encounter, you will not capture as PTOS. If there is documentation that there was a new injury mechanism (i.e. another fall), the patient would be considered for PTOS as long as there was also a diagnosis that falls within our inclusion code range.
Yes, the code W18.2 is not in the exclusion list and so would meet PTOS criteria.
The patient had a new mechanism of injury (fall), and since he expired rapidly and no workup was completed, he can be captured as PTOS.
If your facility has recorded a positive test on the patient, then record positive. With patients now being tested multiple times during their stay, if they test positive at any point, you will record a positive result.
With physician documentation of a false positive, and negative test results following, you will enter negative.
With patients now being tested multiple times during their stay, if they test positive at any point, we are directing to record a positive result. If you did not have the physician documentation and negative result confirmation, then you would have reported positive.
You are correct that TRISS will not calculate for every patient. TRISS EOE, which is a Pennsylvania specific estimated TRISS used in these situations, is planned to be included in the next software platform.
You can absolutely use the yellow memo field after the diagnosis tab in Collector! It is the only memo field that transfers information to PTSF. We often suggest using it to describe unusual scenarios (additional prehospital info, for example), not just for diagnoses. However, please do NOT include any patient or provider identifiers in this free-text field. Use of this memo field does result in errors only if copy and/or paste is used. You cannot use copy/paste functionality in Collector. It may look fine, but when processed at the state, or when the interface is run to v5, errors are the result. Simply avoid copy/paste, and all will be well!
The best resource to use for this is the PTOS Element History. In the Comments column it will note if the element is an optional element. Note on the Element History that elements titled in blue are current; elements with no highlight are retired.
Your best practice is to delete the second record entirely, and not reuse the number. If it was already copied over into v5 with the interface, then you want to delete it there as well. If you haven’t submitted to us yet, we will not need to delete here. But before you delete, ensure that you do change it to NPTOS, just in case it would still be in the system when the transfer process is run.
It depends. Some fields have checks that won’t allow blanks, while others you can pass through.
Registrars may use the discharge destination specify field in specific situations listed in the manual (one example is to enter Home when discharge to SNF which is patient’s residence). Otherwise, can be left blank. This field used to be used for reason and mode of transfer out, but we have specific elements for those now.
Yes, the payor specify fields can be left blank (example: Medicare, with no MCO or other name). Some use these fields to track specific payor info that requires transfer, for example.
With no secondary payor, you can now enter “9 None”. This is a new option to report for 2021 admissions instead of n/a or leaving blank.
In order to capture any hospital event, including osteomyelitis, the condition must have occurred during the patient’s initial stay at your hospital. If the patient arrived to your hospital with osteomyelitis, it should not be captured as a hospital event.
For patient intubated for airway protection per MD documentation, you would not pick up unplanned intubation.
If this was a missed injury, meaning the injury presented itself but was not identified by the medical team, you would capture the Hospital Event. In the definition, patients with an unplanned operative procedure are captured. Also, even if this bleed didn’t present itself and could not be diagnosed until later in the stay, you will still capture this Hospital Event. The PI process can further explore and explain.
Yes, if it does not meet CAUTI and does meet UTI, pick up UTI.
The NTDB/TQIP added a new check on their ED Discharge Date/Time element for 2021 admissions. The field cannot be n/a. When I’s are entered in PTOS, it does map to n/a in the ITDX module, which is problematic. For the time being, you must manually change the value for Discharge Order within the ITDX module under NTDB/ED/Hospital Arrival. PTSF is working with ESO in hopes of providing a better solution.
If they meet the definition of the occurrence, you will pick it up and report for PTOS. There are no exclusions related to COVID, it can be addressed in review.
Based on the information provided, AKI should not be reported. The patient did not have an abrupt decrease in kidney function that required the CRRT nor were they diagnosed with an AKI.
You are correct. Unless there is documentation that the provider provided appropriate therapy for a urinary tract infection, you will not capture this as a hospital event.
There must be documentation of inhalation of gastric contents or other materials and then also documentation of clinical and new radiological findings of pneumonitis which requires treatment within 48 hours.
Unless you have documentation that suggests the DVT was present on admission, you will capture DVT as a hospital event as long as the definition is met. Note, the patient must also be treated with anticoagulation therapy and/or placement of a vena cava filter or clipping of the vena cava in order to capture the DVT hospital event.
For PTOS you should report 17 (Hospice) for discharge destination. We want to capture the level/type of care. You can note “home” in the specify field. Note, the NTDB follows different guidelines in these situations.
This would meet ambulance/helicopter rendezvous, as both provided part of the transport from the referring facility to you.
I recommend recording 3 – Ambulance/Helicopter Rendezvous as the Scene Provider and 1 – Ambulance as the Transport Provider. This may look a little strange so I also recommend that you utilize the Memo to include a note regarding this scenario (be sure to exclude any provider or patient identifiers from this free-text section). Life Flight is still your transport provider even though they rode in the ALS ambulance since they are now caring for the patient. The information from the Life Flight’s trip sheet will still be used in the Transport section for vitals and other information.
For PTOS, the scene is the scene of injury. Therefore, it would be the patient’s home.
You may enter 1, yes. It sounds like you have documentation from the non-acute care hospital. If this is the case, you will enter 2, no, for is this a transfer patient element. But you will then enter 1, yes, for documentation available from outside facility on the Referring Facility tab.
If the x-ray is for the hip specifically, I recommend using the BQ0 code. If it is a diagnostic x-ray that is of the entire pelvis that happened to identify a hip injury, that is when I would use the BW01ZZZ code.
If you would like to send over the documentation you have, we can take a look and offer a better recommendation.
We recommend 0QS2XZZ (Reposition Right Pelvic Bone, External Approach) and 0QS3XZZ (Reposition Left Pelvic Bone, External Approach). Way back during ICD-10 implementation we submitted this same question to coding clinic, but we never heard back. However, we feel this is consistent with what others are using.