Pacemaker Timing Cycles

Поділитися
Вставка
  • Опубліковано 15 лис 2024

КОМЕНТАРІ • 72

  • @ynamanaloto
    @ynamanaloto Рік тому +4

    By far, the best and most helpful educational pacing video on the internet!

  • @mreddy7356
    @mreddy7356 Рік тому +3

    very good presentation was looking this type of presentation for long time

  • @omerhashmi3632
    @omerhashmi3632 3 роки тому +1

    This lecture is nothing short ov heaven for newbies ,,,,,,,,,,, i had only heard abt PMT , but now actually understanding it opens a while new world of prograaming ............ Thankyou , obliged

  • @brunocardoso6435
    @brunocardoso6435 2 місяці тому +1

    Explained with elegant simplicity like we're five years old. Excelent video!

  • @wernorse
    @wernorse 11 місяців тому +1

    Excellent tutorial .. best I’ve seen yet!

  • @efehi2249
    @efehi2249 3 роки тому +1

    This is a wonderful channel for EP-related info. Keep it up.

  • @johan9485
    @johan9485 4 роки тому +2

    Very clear and usefull lecture about one of the most difficult topics about pacing. Thanks!

  • @MrHugoTaz
    @MrHugoTaz 4 роки тому +2

    What a useful and precious informational video. I hope you receive the due return for this valuable contribution. Thank you.

  • @TheRamsis2009
    @TheRamsis2009 6 років тому +2

    This is an amazing piece of work explaining the most difficult of topics. Thanks

  • @ibags6848
    @ibags6848 7 років тому +2

    I’m a senior cardiology fellow nearing my graduation and after watching this i’m now really considering going into EPS. Thank you! I can’t understand it in braunwald no matter how i read it! This is great!

  • @vt2788
    @vt2788 3 роки тому +2

    Thanks a million times for this great video!!!

  • @TheUmmaHope
    @TheUmmaHope 7 років тому +13

    WOW I'm impressed by how good you are at explaining even the most complicated concepts.. Especially the "Upper Rate Behaviour" part ! I'm a big fan

  • @ankurkumarsonar8654
    @ankurkumarsonar8654 11 місяців тому +1

    Very useful vedio.. thankyou

  • @berkmehmet2399
    @berkmehmet2399 6 місяців тому

    Absolutely astonishing !! My sincere congratulations !! Do you have a written book with these explications ??

    • @berkmehmet2399
      @berkmehmet2399 6 місяців тому

      By the way, could it be possible to have your presentations ?

    • @understandingpacemakers7478
      @understandingpacemakers7478  6 місяців тому

      @@berkmehmet2399 Thank you for the compliment!! Sorry, I don't have a book and don't share the presentations

  • @milanam.4353
    @milanam.4353 2 роки тому

    never saw a better video! thnak you !!!!

  • @6474323
    @6474323 7 років тому +1

    Nice, we have test tomorrow in the ward .. U made me ready

  • @Antituarec
    @Antituarec 6 років тому +2

    Thank you for this outstanding lecture!

  • @ishfaqahmad9059
    @ishfaqahmad9059 2 роки тому +2

    You are genius thanks a billion for this all…..

  • @jmp1960
    @jmp1960 4 роки тому +2

    Amazing lecture!!!!!

  • @doctormsr4032
    @doctormsr4032 7 місяців тому +1

    What an amazing lecture ❤

  • @Assad966
    @Assad966 5 років тому +1

    Very useful, thx for sharing and posting

  • @MrNavaidification
    @MrNavaidification 7 років тому +1

    Excellent presentation

  • @emeschrist
    @emeschrist 4 роки тому +1

    Best explanation so far

  • @CARLOCOLAIACO
    @CARLOCOLAIACO 5 років тому +1

    Great presentation.

  • @somiapervaiz1754
    @somiapervaiz1754 Рік тому +1

    Best ❤️👏

  • @studiocorax8790
    @studiocorax8790 Рік тому

    The definition of pedagogical.

  • @Dailyupsdates
    @Dailyupsdates 3 роки тому +1

    Excellent

  • @jayasharma5407
    @jayasharma5407 6 років тому +1

    It was really helpful. Thanks ! Keep us updated. ;)

  • @mazscience9518
    @mazscience9518 5 років тому +1

    I'm confused by the part where you say we try to eliminate upper rate behavior by either decreasing the AV delay/PVARP (which makes sense), or increasing the MTR (which doesn't make sense to me). Wouldn't INCREASING the MTR actually increase the likelihood of Pacemaker Wenckebach? Unless by "increasing" you mean make faster or decrease the time. For example, if I increase the MTR to let's say 200bpm from 120 bpm, I'm almost guaranteeing pacemaker wenckebach, aren't I?

    • @understandingpacemakers7478
      @understandingpacemakers7478  5 років тому +3

      Hi Maz Science, excellent question!
      I probably should have included another example on this as it is one of the more difficult pacemaker topics to learn. Okay, let’s say you have a patient that is programmed with the following settings.
      LRL = 60 bpm
      AV delay = 100 ms
      PVARP = 300 ms
      MTR = 120 bpm.
      TARP = 400 ms
      If we calculate the 2:1 block point we would take the TARP of 400 ms and divide that into 60,000 and we would come up with a 2:1 block point of 150 bpm. This would mean that the patient will be 1:1 conduction up to 120 bpm, they would then go to a Wenkebach from 120 bpm up to 150 bpm. If the Atrial rate were to go up to, or above 150 bpm they would go to a 2:1 block. So by raising the MTR from 120 bpm up to something like 140 bpm we are minimizing some of the Wenckebach behavior. Instead of the patient having Wenckebach from 120 bpm up to 150 bpm they will now only have Wenckebach from 140 bpm up to 150 bpm. If you raise the MTR to 150 bpm the patient would be 1:1 all the way up to 150 bpm and then would go straight to 2:1 block. So in this scenario, if you raise the MTR to 200 bpm you would never actually have any Wenckebach block upper rate behavior.
      I prefer to have a little Wenckebach window in there. I wouldn't want a patient to be working out and everything is 1:1 and then suddenly they go to a 2:1 block. As you probably already know this will cut their cardiac output in half very suddenly and there is a potential that the patient could get dizzy or even pass out. I don't know if it is true or not but I was taught that by having a little Wenckebach window in there it might serve as a warning to the patient. They might be able to feel the dropped beats and then realize that they need to slow down.
      Hope this helps!

    • @mazscience9518
      @mazscience9518 5 років тому +1

      @@understandingpacemakers7478 Extremely helpful, thanks for taking time to clarify!

  • @666rayoflight
    @666rayoflight 4 роки тому +1

    THANKS A LOT . HELPED ME A LOT

  • @rosemaryjose6132
    @rosemaryjose6132 4 роки тому +1

    thank you so much , it was very helpful

  • @munirabdullatif2022
    @munirabdullatif2022 7 років тому +3

    İn one word, Great .. İ don't know how to thank you

  • @yidnekachewasrat
    @yidnekachewasrat 2 роки тому +1

    state of the art

  • @karimbenbrahim793
    @karimbenbrahim793 2 роки тому

    thank you for this amazing presentation ,can you give us some bibliographies please?

  • @MrAhmedfawzyzidan
    @MrAhmedfawzyzidan 5 років тому +1

    Sehr excellent and brilliant....thank you very much

  • @qusaijoha1753
    @qusaijoha1753 6 років тому

    thank you for the great infos, really helpfull. my question is with the 2:1 Block why didnt the pacemaker start a VA-Interval and LRL and reacted accordingly( why waited so long tell a P-wave schowed up)

    • @qusaijoha1753
      @qusaijoha1753 6 років тому

      do we have a fast heart rate with 2:1 block here?

    • @understandingpacemakers7478
      @understandingpacemakers7478  6 років тому

      Hi Joha, yes we have a fast heart rate in this situation. The upper rate behavior only occurs when the patient's intrinsic atrial rate is faster than the TARP or PVARP timer which is usually at a faster rate. In reality, the pacemaker is actually starting a VA-Interval and a LRL timer, it's just that those timers wouldn't have timed out which is why the pacemaker waits so long and won't atrial pace. Lets say that a patient is programmed with a Lower Rate Limit (LRL) of 60 bpm and has a 2:1 block point of 120 bpm but, there intrinsic atrial rate is 130 bpm. That would mean that the 2:1 block rate that the patient would be at is 65 bpm. Since 65 bpm is faster than 60 bpm the LRL won't time out, and depending on how the pacemaker is programmed the VA timer won't time out either. I hope that made sense.

    • @qusaijoha1753
      @qusaijoha1753 6 років тому

      made sense, thank you very much

  • @connect2nasir
    @connect2nasir 4 роки тому +1

    Outstanding!

  • @Azalro
    @Azalro 6 років тому

    Great presentation, thanks a lot.

  • @vasilischrisanthidis8214
    @vasilischrisanthidis8214 5 років тому +1

    Simple outstanding!

  • @oliverolle4157
    @oliverolle4157 2 роки тому

    My husband pacemaker battery has been dead for 2years now. Is there any danger in just having the device inside him and it's not active

    • @understandingpacemakers7478
      @understandingpacemakers7478  2 роки тому +1

      Pacemakers are designed to be in the body for many years so most likely there is no danger of leaving it in. But, it would be a good idea to check with the pacemaker clinic that he use to follow at.

  • @esraaalsadeq601
    @esraaalsadeq601 4 роки тому

    very useful !!!! Thank you.
    Can you share the slides please?

  • @sebamathew4556
    @sebamathew4556 Рік тому

    Thank you so much:)

  • @chauhanrajputvarna4528
    @chauhanrajputvarna4528 Рік тому +1

    good
    vedio

  • @ujjwaldasanything
    @ujjwaldasanything 3 роки тому +1

    Thank you sir

  • @PeterBlahutDr
    @PeterBlahutDr 7 років тому

    26:40, why intrinsic PP interval with dropped pace QRS is longer, than other PP interval. PP interval is from intrinsic activity of SA node, and SA node here is OK, or pacient has SSS syndrome?

    • @understandingpacemakers7478
      @understandingpacemakers7478  7 років тому +1

      Peter Blahút - Good catch! I must have missed that when I created the PowerPoint. Yes, the SA node is typically functioning properly in this situation and therefore the P to P interval should have been consistent all the way across and not longer after the dropped pace.

  • @khmercrypto9622
    @khmercrypto9622 7 років тому +1

    thank thank very good!