Transcript
Subhi Sedate (0:00)
Hello, Combi Nation. My name is Subhi Sedate. I've spent over a decade in medical device pharma and combination product development. Our industry feels complicated sometimes. Drugs, devices, clinical trials, submissions, sterilization, validation, design control, risk management, market access, reimbursement, the list goes on. My goal is mastery, so this podcast is to ask questions I have to people who may have the answers. Each week on the Combinate podcast, I talk to someone about their area to further understand and simplify. Whether you're a pharma person trying to understand the next wave of products, or a device person trying to navigate a pharma system you're unfamiliar with, or a newbie in both areas, I invite you to listen and together we can simplify.
Subhi Sedate (0:49)
By combinating foreign hi everybody and welcome to this special episode of the comedy podcast. I'm your host, Subi Sedeh, and on this episode we are graced and honored by Nathan Roman. Nathan Roman is a validation and temp control expert and he branched off on his own in the 20ish years ago Roman range. I'm not exactly sure how many years it's been. Got a start as a draftsman and is now focused on validation and temperature mapping. More more specifically. Welcome Nathan.
Nathan Roman (1:28)
Hey, thank you so much. Appreciate it.
Subhi Sedate (1:31)
You're focused on validation in many ways now. What got you into this field? Because you transitioned from being an autocad draftsman into validation. And I guess in my head just based on the functions that I've worked with in medtech, biotech and so on, design is one area, operations is another area. But so you got your start as an autocad draftsman and moved from that arena straight into validation. It feels very trial by fiery, if you will. And in my head I'm just thinking it's seldom that somebody goes so hard in, in in a design function to so hard in operation. It's like most people will be like, all right, I'm an autocad, I'm an autocad person. I'm going to move into design for manufacturability. That kind of makes sense, right? But to go from I'm doing pre market drawings to I'm validating lines on one shot feels into the deep end.
Nathan Roman (2:36)
True, I can understand that, I appreciate that. But I certainly didn't go from doing CAD work to jumping into hardcore validation process or process validation type stuff. Right. Doing CAD work. I was, I originally was doing 3D modeling, designing steel structures for aggregate plants in the quarries here in pa, Pennsylvania where I live. Quarry plants are huge, obviously with the being the Keystone State. So I was designing quarry rock, rock crushers and conveyor belts and things like that. Anyway, so that's what I was doing. But I had an uncle who was in the engineering validation role at a company called Raytheon back in the day. And he ended up moving on to a couple different roles. Needed some help on a validation job on a project in Lancaster, and he needed someone to help him out, read P and IDs. So like I say in my story, I knew what he needed because I basically, I worked on P and IDs or drawings every day, all day. I was able to help him out. So I went all. I went over and helped him. And it was very rudimentary, walking around with the drawing. And then I like to say back in those days with the highlighter and I had to follow my path and things like that with piping and the ductwork. So it was very easy stepping into this role. And then after that is when he was interested in. And seeing if I. If I could progress more, do more. Hey, Nate, are you interested in a job? Are you interested in a role? And not to mention, it was quite a pay bump from doing CAD work as a CAD guide to being a validation specialist. So that, of course, was nice. But I started off low level, right. So doing P&ID walk downs, equipment walkthroughs, verifying the tags on equipment. What. What's the name plate say? Okay, read it back to me, that kind of stuff out in the field. And then moved on to put you on a project an hour and 45 minutes away from home. You got to drive there every day. So it was a lot of commuting back then. But. But I was able to get on site with somebody with a good project manager that kind of walked me through. What's a protocol? How do you execute the protocol? What are good documentation practices like? I didn't know any of this stuff, but slowly learn different things through time is how it got started.
