Microservice architectures are often a graph of components distributed across a network. This architecture gives rise to a new problem. How can we trace and bind together all services involved in one operation request? When a client calls an operation, it can be spread across different services over the network, each service has its own context.
Most DMS platforms like Documentum and SharePoint have their out-of-the-box full clients which are meant to provide all (or most of all) of the platform functionality. Although these full clients can, normally, get customized or configured, they are, however, complex and slow to adopt new technologies.
If you have a specific use case, why start from a complex system and reduce it to your needs? Why not build a custom client that is streamlined and focus on your use case instead? The business logic can reside on the server. But for the client, we are free to use any state-of-the-art modern web framework.
Monday morning, for some this is the agonizing beginning of the week and the work stress, for me this is the time of anticipation until I’m back at the fme office. Because when I go to the office in the morning; I’m already expected with a sweet smile and a “Hah, good that you’re there!”. For one or the other, these words may already scare the ToDo list. I, on the other hand, wonder what will happen this week…
So while I’m still thinking about all the adventures, I move slowly in the direction of the computer and again need tens of starts to type in the password correctly. After successfully completing the mission, I discuss today’s daily routine with my colleague. Once this is done, it goes to the preserves.
With so many applications/systems to keep an eye on, nowadays, it often takes IT staff too much time to perform repeated manual tasks. This is valuable time we then lack in communicating with stake holders, key users and operational departments or solving other problems.
It’s often easy to say: “I’ll just do this manually because it only takes me half an hour a week”
Markus Schneider, Managing Consultant and Life Sciences Expert at fme AG in Frankfurt, is one of the leading migration specialists in Central Europe. He is leading a team of application- and content-migration experts specialized on the Life Science and especially Pharmaceutical industry.
Changes always seem frightening in the first moment. What will the new bring? Will I be able to deal with it? Is it just as good as the old? New things gives you the chance to bring something even better to light – something that we often don’t take into consideration at the beginning.
In the regulated life sciences environment, the management of controlled documents such as SOPs (Standard Operating Procedures), procedural instructions or work instructions is of great importance. Change management processes ensure that these documents are properly reviewed, approved, trained, distributed and, if necessary, overruled. In addition to well-known use cases within change management, there are special cases that are designed differently from company to company.
One of these applications is so-called Redlining .
In regulated life sciences environments, the management of controlled documents such as SOPs (Standard Operating Procedures), procedural instructions or work instructions is of great importance. Change management processes ensure that these documents are properly revised, approved, trained, distributed and, where necessary, suspended. In addition to well-known use cases within change management, there are special cases that are handled differently from company to company.
One of these applications is the case of the so called document release process.
Do you know these sentences, which simply belong to every job description?
“Are the rolls fresh?” – »But really only cut the tips.« – »Is the space at the window still free?« or also »I would like to migrate 15,000 documents – what does it cost me?«
I have heard the last sentence very often in the past six years and definitely count it among my top three.
It is a challenging time for many traditional pharmaceutical companies. The competiveness of the market place, the looming loss of patents, ever-increasing international regulatory requirements and pressure to lower the overall cost for healthcare – they all increase the burden and force these companies to find new approaches in order to survive in the industry.
Pharmaceutical companies are today driven to adopt strategies for reducing resources and costs, circumstances that have been tangible in other manufacturing sectors for some time. The expectation from IT departments is that they should support the business challenges and deliver cost-effective solutions without compromising quality, compliance, agility or flexibility.
Cloud computing seems to fulfil the promises of solving these business challenges and life sciences firms increasingly look to it for the universal remedy. However, how well does cloud computing coexist with GxP compliance and regulated environments?