Form F-1/A Link: https://t.co/RQcYLFMXQO
Okay hope everyone having a lovely weekend. Lots of love today. Feeling very blessed 🥰 Going through NNOX tweets from last week. Time to compile threads and bring you highlights. No need to go digging old tweets if I do for you 🤗 FDA, Secondary, and 3P510k. Let’s review..
Form F-1/A Link: https://t.co/RQcYLFMXQO
Reference to Eagle eyes: https://t.co/gT779MFX82
We discover in F-1 that 3P510K recommended clearance of Nanox Source. This triggers a 30 day timeline to approval by FDA. However ...
Eagle-eyes \U0001f985 https://t.co/w1wF3Ysmt1
— Harvey \U0001f1fa\U0001f1f8 (@realharveymark) February 12, 2021
The short thesis destroyed by the recommend clearance. Go back see where NNOX trade before short report. You will recognize the number. Okay you see the number approx the analyst price targets and secondary pricing.
NNOX here\u2019s a link about FDA Third Party Review Program. https://t.co/hlrrlXi6Us
— Harvey \U0001f1fa\U0001f1f8 (@realharveymark) February 11, 2021
"The FDA's review timeframe for a MDUFA decision is within 30 days after receiving the recommendation of a 3P510k Review Organization."
I typo 99 mean pg 97 but this covered in F-1. Nanox has mapped this out fully and tell you exactly what to expect.
These are two important NNOX points. 3P510K 30 day, FDA classification decision covered for you
The \u201cde novo\u201d process is a risk-based classification determination means low to moderate risk novel medical devices can have route to market. Okay this is contingency talk. This is a short seller dream scenario. FUD gonna get all over everything but not you. You go to F-1/A pg 99
— Harvey \U0001f1fa\U0001f1f8 (@realharveymark) February 11, 2021
Tomorrow FDA will publish all approvals that occur last week. It very possible NNOX is there. Maybe 60% chance
30 days \U0001f60e https://t.co/Qj80xn00pI
— Harvey \U0001f1fa\U0001f1f8 (@realharveymark) February 12, 2021
More from Life
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.