OpenRegulatory
OpenRegulatory
  • 73
  • 32 210
Medical Device Technical Documentation In 5 Minutes: Formwork Product Templates
When we learn to code, we learn by looking at example code on GitHub. Why don't we have examples for medical device technical documentation? Probably because people don't share them.
But today we do. Check out Formwork, our eQMS which now comes bundled with example technical documentation - we call them product templates.
Try out Formwork here:
openregulatory.com/formwork/
Переглядів: 90

Відео

QMS Automation With The Formwork QMS Overview
Переглядів 134Місяць тому
A quick walkthrough on how our eQMS software Formwork helps you automate your QMS documentation with a feature called the "QMS Overview". If you'd like to try out Formwork, check it out here: openregulatory.com/formwork
B2B Sales And Generating Revenue: Tatyana Eliseeva, Healthcare Startup Meetup #3
Переглядів 323 місяці тому
00:00 Introduction 02:30 Tatyana's Talk 20:30 Q&A Our Healthcare Startup Meetup is back! This time, we'll be focusing about one of your most-requested topics: B2B sales and generating revenue. If you want to join next time, check it out here: www.meetup.com/healthcare-startup-meetup/ Tatyana from HealthCaters will be our guest, and she'll be sharing her insights on those topics with you in our ...
Agile Development For Medical Device Software: Is It Possible?
Переглядів 2215 місяців тому
This is the million-dollar question, or the Holy Grail of medical device compliance: Can you do agile development which magically generates all the necessary compliance documentation for your audits? I'll walk you through what's needed for passing audits, and based on a typical agile development process (ours!), we can take a look at whether it's possible. Link to Formwork: openregulatory.com/f...
Launching Free Regulatory Updates: Stay Updated With The ISO 13485 And Other Standards
Переглядів 765 місяців тому
In the past, staying up to date with medical device standards like the ISO 13485, IEC 62304 and others has either been very clunky or rather expensive. Today, we're launching Regulatory Updates in our eQMS software, Formwork, and the best thing is that we're making it available to everyone, for free! There's literally no reason not to use it - it'll save you lots of time, help you pass your aud...
Jira QMS: Can You Set Up a QMS And Requirements Management In Jira For Medical Device Compliance?
Переглядів 2916 місяців тому
As a medical device manufacturer, can you set up your Quality Management System (QMS) in Jira? And can you manage your requirements (e.g. Design Inputs) there, too? The goal would be compliance with the ISO 13485, IEC 62304 and other standards required for medical device manufacturers. Watch my video to see how a setup in Jira could look like, and where you might run into problems if you get au...
Get The ISO 13485 Almost For Free: How to Buy Standards on the Estonian Website
Переглядів 1226 місяців тому
If you're a medical device manufacturer, you have to comply with certain standards, like the ISO 13485. The shady thing, however, is that you have to buy those standards - yes, you literally have to purchase a PDF. The German websites offer standards for ridiculous prices - anywhere between 100€ and 600€, crazy! The good news is that other developed countries like Estonia are much more friendly...
Bringing Transparency To MDR Compliance
Переглядів 396 місяців тому
A quick mention of our templates and why we published them for free. Check out more here: openregulatory.com/templates/
Free MDR Templates
Переглядів 776 місяців тому
A (very) short video about us offering free EU MDR templates and why the hell I came up with the idea :) Link: openregulatory.com/templates/
ChatGPT For Medical Device Documentation (MDR / FDA)?
Переглядів 3747 місяців тому
Can you use ChatGPT to create your medical device documentation for EU MDR or FDA submissions? We'll find out in today's video :) 00:00 Introduction & free templates! 01:23 First attempt with ChatGPT 03:56 Second attempt with Formwork 06:35 Conclusion openregulatory.com/formwork
Software Detailed Design Documentation in Formwork
Переглядів 1267 місяців тому
If you're IEC 62304 class C (there are classes A, B and C), you need to document something called "software detailed design" for your medical device. Let's check out how you can document that in Formwork, our QMS software. Check out Formwork here: openregulatory.com/formwork
Medical Device QMS Software Comparison: Shady Business Practices!
Переглядів 2987 місяців тому
00:00 Introduction 00:48 Greenlight Guru 03:01 Qualio 06:05 Matrix Requirements 08:00 OpenRegulatory Formwork First off, sorry for the Amazon box in the background. I'm currently tidying up! I also forgot to mention the most important points about our Formwork (chuckle): There's a free tier, and you get unlimited users in all tiers, which is super awesome! Anyway, here's the actual description ...
Matthew Fenech: DiGA For Glucose Control at Una Health (Healthcare Startup Meetup #2)
Переглядів 1137 місяців тому
00:00 Introduction 03:02 Matt's talk 18:00 Q&A Episode 2 of our Healthcare Startup Meetup! If you want to join next time, check it out here: www.meetup.com/healthcare-startup-meetup/ In this meetup, our guest will be Matthew Fenech from Una Health. I can hardly believe that he managed to carve some time out of his schedule to join us, because many exciting things are happening at his company Un...
MDR Clinical Evaluation: Understanding the Process
Переглядів 1308 місяців тому
This is the first video in our series of 7 videos on MDR Clinical Evaluations! Sebastian walks you through the process and basic concepts of an MDR Clinical Evaluation. He'll also walk you through the template of the Clinical Evaluation Process. This first video is free and all the other videos are purchasable through our Wizard video course which helps you bring your medical device to market a...
QMS Overview: Automate Your ISO 13485 Documents and Records
Переглядів 3288 місяців тому
Check out how Formwork automatically creates a document list of all your QMS documents, including SOPs and templates. This saves you a gigantic amount of time! To our knowledge, no other QMS software has anything which comes close. Formwork is the best software for medical device startups to bring their product to market. It comes with unlimited users and documents and even has a free tier! Che...
Leander Märkisch: Building AI For Radiology at Floy (Healthcare Startup Meetup #1)
Переглядів 1529 місяців тому
Leander Märkisch: Building AI For Radiology at Floy (Healthcare Startup Meetup #1)
Use ChatGPT to Generate Your QMS In Minutes
Переглядів 1 тис.11 місяців тому
Use ChatGPT to Generate Your QMS In Minutes
Medical Device Starter Course, Part 6: ChatGPT For Medical Devices And Automating QMS Trainings
Переглядів 157Рік тому
Medical Device Starter Course, Part 6: ChatGPT For Medical Devices And Automating QMS Trainings
Medical Device Starter Course, Part 5: Auto-Generate Audit Spreadsheets For Requirements Management
Переглядів 76Рік тому
Medical Device Starter Course, Part 5: Auto-Generate Audit Spreadsheets For Requirements Management
Medical Device Starter Course, Part 4: Saving Time By Copying OpenRegulatory Templates
Переглядів 109Рік тому
Medical Device Starter Course, Part 4: Saving Time By Copying OpenRegulatory Templates
Custom File Documents / Records
Переглядів 72Рік тому
Custom File Documents / Records
QMS Trainings: Automatically Train Your Employees in Formwork
Переглядів 56Рік тому
QMS Trainings: Automatically Train Your Employees in Formwork
Formwork Batch Export: The Only eQMS Software Without Lock-In
Переглядів 41Рік тому
Formwork Batch Export: The Only eQMS Software Without Lock-In
Manage your Technical Documentation in Formwork (eQMS software)
Переглядів 103Рік тому
Manage your Technical Documentation in Formwork (eQMS software)
Medical Device Starter Course, Part 3: What next? How to save money and automate things?
Переглядів 113Рік тому
Medical Device Starter Course, Part 3: What next? How to save money and automate things?
Medical Device Starter Course, Part 2: What do you need to do? Looking at IEC 62304 and other docs
Переглядів 215Рік тому
Medical Device Starter Course, Part 2: What do you need to do? Looking at IEC 62304 and other docs
Medical Device Starter Course, Part 1: How much does it cost? How long does it take?
Переглядів 593Рік тому
Medical Device Starter Course, Part 1: How much does it cost? How long does it take?
Creating a UDI For a Medical Device at IFA
Переглядів 300Рік тому
Creating a UDI For a Medical Device at IFA
Registering at GS1 To Purchase a UDI For A Medical Device
Переглядів 539Рік тому
Registering at GS1 To Purchase a UDI For A Medical Device
Introduction To Understanding Unique Device Identifiers (UDIs) For Medical Devices
Переглядів 871Рік тому
Introduction To Understanding Unique Device Identifiers (UDIs) For Medical Devices

КОМЕНТАРІ

  • @brunomarques309
    @brunomarques309 11 днів тому

    Thanks for your videos! I'm new to this kind of regulatory documentation, but your content helps me out a lot :) I'm just curious about the conclusion here: Obviously, your video points out that shipping your Jira/trello/whatever tickets / Github issues & PR discussions etc. as documentation for your medical software is not an option. But both can still be done in parallel right? an Agile board / issue tracker for developers, and the documentation for regulation. I mean taking your example here, a milestone could be added to the basecamp ticket, and the output of that ticket would not only be to perform the change in the software, but also to update the documentation accordingly..? In a previous project, each issue had a checklist that needed to be fulfilled for that particular issue to be closed: 1. Provide possible solutions + chosen solution for the fix 2. Implement the fix 3. Provide 100% test coverage 4. Update project requirements Then the next release in which the fix is implemented matches the project documentation. Would this workflow work?

    • @openregulatory
      @openregulatory 11 днів тому

      Hey, yeah sure, that's possible! I've seen this "two-project-setup" done a few times. The question then, however, becomes: If you're using a second "project" for your regulatory documentation, why do it in the same tool (e.g. Jira) which is a super-generic tool and objectively sucks for this sort of task? You'd be better off using some sort of specialized software for this instead; so, for your documents, you'd look for an eQMS, and for your requirements and tests, you'd look for a requirements management software. I'm obviously super biased here as we developed a product which achieves exactly this (Formwork, openregulatory.com/formwork) - but, still trying to be somewhat objective here, these are your options: 1) Use Jira / Confluence / any other generic tool: It's possible, but you'll spend quite some time setting it up. You'll probably have to re-read the standards a few times to see what sort of "data models" you have to set up and how to link them with one another. Versioning becomes a huge concern because you essentially need to be able to pull out your documentation for "historic version X" of your software; this is non-trivial in most tools as humanity hasn't invented a versioned SQL database yet (chuckle). So you'll probably have to create a "messy bunched-up zip-file" which contains your data export for each medical device version you release. This is how companies do it with Jira / Confluence at least. 2) You use a specialized tool and all the above pain goes away. There are drawbacks though, too: You're dealing with another tool which your team might not be accustomed to, and obviously it's an additional expense. Hope it helps!

  • @cimilar
    @cimilar Місяць тому

    Sehr gut, danke.

  • @counterzees
    @counterzees Місяць тому

    In some cases, you may find a "pure" ISO standard that does NOT have a corresponding EN ISO standard. In this case, the EVS pricing for the "pure" ISO standard is similar to the higher ISO standard prices you will find from other standards bodies and standards resellers.

  • @counterzees
    @counterzees Місяць тому

    A quick comment (correction) that even further supports acquiring standards from EVS. The lower-priced standards sold by EVS are not the "pure" ISO versions - instead, they are "EN ISO" standards that include the ISO standard inside and also include bonus material applicable to European regulations. The bonus information are called "Z" Annexes that correlate the clauses of the standard to the corresponding General Safety and Performance Requirements (Annex I) of the Europe MDR and IVDDR.

  • @counterzees
    @counterzees Місяць тому

    Hello Oliver, you mentioned that it is ok (desirable) to overwrite old records with new records. That has not been my experience in my many years of designing, running and auditing medical device quality systems. From my perspective, all records should be dated and saved "forever". It is normal to have new records but I would not want to overwrite an older record with a newer record. Perhaps you can clarify your meaning?

    • @openregulatory
      @openregulatory Місяць тому

      Not our experience, and we also passed many audits. Where do your requirements come from?

  • @counterzees
    @counterzees Місяць тому

    I agree that EVS (Estonia national standard body) is the most affordable source in the world for "EN ISO" versions [or "EN" versions associated with IEC standards - not called EN IEC typically - weird]. But please note that their prices for the "ISO" only versions of standards is similar to other standards bodies and resellers. So buy EN ISO or EN (IEC) standards from EVS and you get the ISO/IEC version inside the document and also get informative European Z Annexes that map the clauses of the standard to the corresponding European medical device regulations, formerly the European Directives.

  • @MariaSchüller
    @MariaSchüller 4 місяці тому

    Very wholesome tutorial. I love this feature! Thank you.

  • @ethanstillman513
    @ethanstillman513 4 місяці тому

    Great content; thanks!

  • @anagha77
    @anagha77 4 місяці тому

    can this SW create test cases with already available requirement document? so can we upload our own req. document and it can generate module test cases or system level test cases?

    • @openregulatory
      @openregulatory 4 місяці тому

      Yes. You can sign up for a free trial and see whether it works for your use case :)

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

    Great to see promotion of EVS - simple and relatively easy to use, they don't over-sell themselves and spam you with emails. Software restrictions like 'FileOpen' are overburdening, particularly for smaller companies and start-ups. EVS also offer free tracking/notification for new standards - you just need an account and don't have to buy the standard beforehand. I think other companies charge for similar services.

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

    Oliver you are a legend. what do you think of a similar idea using a Modern Requirements plugin in DevOps for example?

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

      Hey, thanks for your kind words! :) I mean, DevOps + Modern Requirements will work for all the reasons a Confluence / Jira + plugins setup will work, and it will suck for all the same reasons the Confluence / Jira setup sucks, too. So.. it's kinda up to you. Some quick notes: - The Jira plugins seem to be more affordable, e.g. SoftComply has mostly-transparent pricing, while Modern Requirements has "request a quote" secret pricing (which I find very shady). - It'll still probably need some "glue" and a person in your team who maintains this. I guess it'll boil down to how much you really want to use DevOps for your requirements management. My gut feeling would be that small teams shouldn't go for this sort of custom approach, because you can't sacrifice 1+ engineer working full time on this sort of stuff. Larger teams which might be more coupled to DevOps might be able to do this, though. Stil.. maximum productivity would be to keep project management and regulatory documentation tools separate.

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

      @@openregulatory thanks a lot, this was very useful (though I was mostly looking for confirmation that it's generally a bad idea as you detailed with Jira.)

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

      @@drmanhattan71 Haha oh alright, I was trying to be diplomatic. Yes, DevOps for regulatory documentation probably sucks just as much as Jira 😄

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

    Easing the burden of bureaucracy is cool!

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

    Great Business and Work! Thanks for your Mission! Looking forward to dig those files and maybe also receive consultancy from you. Keep it up!

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

      Awesome, thanks for your kind words! :)

  • @everythingisfake7555
    @everythingisfake7555 8 місяців тому

    Does it have ISO 9001 templates?

  • @kinusha303
    @kinusha303 8 місяців тому

    helpful video! i would like check if we have one device with 5 variants (difference in size) , do we need to buy 5 UDI-Di?

  • @CarmenBellebna
    @CarmenBellebna 8 місяців тому

    cool! Thank you

  • @drtunset
    @drtunset 9 місяців тому

    Such a cool feature. Looking forward to begin with the risk management process in Formwork.

    • @openregulatory
      @openregulatory 9 місяців тому

      Awesome. Thanks for choosing Formwork, and let me know if you need any help! :)

  • @JoergKowollik
    @JoergKowollik 9 місяців тому

    spät gesehen, aber finde ich jetzt auch noch Klasse !

    • @openregulatory
      @openregulatory 9 місяців тому

      Haha, danke! Und vielen Dank für's Anschauen! :)

  • @DavidAudrain-d2v
    @DavidAudrain-d2v 9 місяців тому

    github was started in 2008 , before that sourceforge was the place where opensource project were hosted when a project was not hosted on a specific server

  • @Hannibal21623
    @Hannibal21623 11 місяців тому

    Nice job

  • @crystalcee5715
    @crystalcee5715 11 місяців тому

    Could your software take existing documentation and rewrite it - simplify and correct ?

    • @openregulatory
      @openregulatory 11 місяців тому

      Theoretically yes, but it's not a feature we've built yet. Happy to look into it! :)

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

    Does framework integrate with jira, so if you raise a ticket within jira can it link into framework

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

      Good question! We decided not to integrate with Jira because it doesn't increase the efficiency of creating your regulatory documentation. Check out this article on our website to understand why and which mistakes to avoid: openregulatory.com/qms-software-jira-github-gitlab-integration-mistake/

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

    Have you found a perfect way for Agile to work with 62304 yet?

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

      Unfortunately not, but I don't think any other human on this planet has found a solution to this yet, haha..

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

      @@openregulatory thank you for getting back to me. Agile seems to be partly a fashionable and buzz word expected in practice from cutting edge developers.

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

    Will the AI do its own literature search for writing a scientific article in the style of Nature Immunology, or do I need to input a bibliography?

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

      Currently our AI features only draft your software requirements and tests. For your clinical evaluation which most likely includes citing scientific articles, you're on your own.. for now :)

  • @m.taher45
    @m.taher45 Рік тому

    Thank you for this information How can we obtain the forms for the internal audit of the quality management system and all of you for the management review

  • @MS-ff2qo
    @MS-ff2qo Рік тому

    Sure AI can do it

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

    I noticed that you entered the version for jQuery as 3.4.1, however in the package.json it's ^3.4.1, which is 3.4.1 or above. Will this cause issues come audit time?

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

      Good find! And nope, I don't think this will cause any issues. It's highly unlikely that your auditor knows jQuery and/or the versioning scheme in package.json files. SOUP documentation right now is not very useful on a technical level anyway (as e.g. you only need to include first-level dependencies). Also, most auditors don't have much software experience. Well, maybe with mainframes and punch cards..

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

    You guys should add an upload feature, wherein you can upload doc files or xls files and they are automatically converted into documents on your site. Making/Copying the entire document on your site again is unnecessary.

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

      That's a good point! But too complex for now (converting Word to Markdown sounds like hell). It's arguably a feature for enterprise customers who already have a QMS in place and want to migrate to Formwork. For now, we're not interested in enterprise customers.

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

    Thanks for sharing this! A question: any first level dependency depends on a number of second level ones, and those on more dependencies and so on. Any mid-sized rails project can have a few hundred dependencies when you sum all up, and it gets way uglier if you take the node route ... ... are all those considered SOUP? I mean, why would they not be considered as such? Of course, if first level SOUP as you describe is pain, a positive answer to that question would mean insurmountable unbearable agonizing pain. There is probably lower levels in hell to the one when you get to list all the requirements of your node_modules folder ... but not many :) So, what do you think?

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

      Hey David, that's a great question which actually has come up many times in our consulting! I should have answered it in the video, haha.. The TLDR is that you only have to document first-level dependencies, i.e., for rails, what's in your Gemfile (and not what's in your Gemfile.lock). Does this make sense? Probably not. Does SOUP documentation make sense? Probably also not. Do regulators understand SOUP? Let's just say an auditor recently asked me "what SOUP actually was" and I explained it to them, haha..

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

      @@openregulatory thanks a lot for your response, Oliver! Just plain regular pain it is then :) Yeah, I agree that makes zero sense and total sense, both at the same time :) On a sad note, I think that renders this SOUP thing quite useless (I can understand the original intended sense of it).

    • @brainprism88
      @brainprism88 7 місяців тому

      @@openregulatory what happens if it goes high or medium risk?

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

    Very informative.

  • @xy-en1ky
    @xy-en1ky 3 роки тому

    Regarding the anomaly list: I believe it is enough to filter the list for entries for bugs, which is usually possible using labels or other filter operations.

  • @danielwarfield5913
    @danielwarfield5913 3 роки тому

    You are a gentleman and a scholar

  • @lonaur
    @lonaur 3 роки тому

    Sehr sympathischer und interessanter Vortrag. Und eine super Initiative Oliver!

    • @openregulatory
      @openregulatory 3 роки тому

      Vielen Dank fürs Zuschauen und das nette Feedback, Rainer! :)