The next stage in the systems engineering process is the definition of interfaces. Recognize, when we talked about system design earlier, interfaces are actually designed in this process. However, we talk about them separately because they are such an important item. Interfaces are one of those items that get lost in the system design because nobody takes responsibility for it. Each person is working on their own piece of the puzzle, and then people trying to figure out how do these different pieces fit together? Well, that's the interfaces, and if you don't have a good systems engineer, healthcare systems engineer to be able to recognize what those interfaces are, the design can get flawed. There can be problems, there can be risks, so it's important to recognize the interfaces. From the definition, just think about it this way there are going to be two entities. Those two entities need to communicate in some fashion. Software, hardware solutions, other types, data solutions. There is an interface between two elements, two entities within the system, so you have to recognize that. It can be all the way at the very high level via context diagram. Here's the problem, what are the inputs? What are the outputs, what governs it, what type of infrastructure? All those elements describe interfaces that interconnection. Or if you go all the way down to let's just say an ICU, what does that mean in terms of what type of interfaces, the inputs. Here's some patients, the outputs a positive outcome for the patient. Also, you have laws and policies that dictate who goes on to the intensive care unit. As well as where is that Intensive Care Unit actually residing? Is it in a hospital, is it in somebody's home? Where is that ICU? Make sure you're clear, but those interfaces are so important. Where do you fit into the puzzle, and what are the interconnections in that puzzle? Those are interfaces. Elaborating a bit more on interfaces, stage 9 of the systems engineering process. Let's talk about first, why do we need interfaces? Remember, you have two different elements. When you have two different elements within a system, they need to communicate. How do you transfer information back and forth? Also, there's probably some control mechanism. How do you control one element with the other and then also the idea of feedback. So, information passes from one unit to the other, how do you know you got it right? How do you know that it's doing the right thing, that we have these interfaces and that's why they're so important. Think about human machine interfaces. A video game, for example, or just something you're working on your PC. There's some human machine interface, you're looking at the machine, you're touching the machine, that is an interface. Also, there can be electro-mechanical interfaces within a system. Wiring, electronics passing back and forth, that's an electronic mechanical interface, those need to be defined. Two different elements, something's passing between them. Maybe there's some type of virtual interface, something with the virtual reality. How do you display that virtual reality, that is an interface. Also, potentially human to human, how do people interface, specifically within healthcare? How can you communicate better? How can you make sure the clinicians are talking to the patients who are talking to the administrators? How do you do that better? There are so many different interfaces in healthcare, why is this important? Look at the impact, you want things done in a timely fashion. You absolutely need it done accurately, and it needs to be complete. If any of these are impacted from a healthcare perspective, bad things can happen. So be very clear, the interfaces are so important. And it's often the case when designing a system, complex system to system or enterprise system, interfaces where things fall apart. So be very clear, very purposeful as you build your system. The next stage in the systems engineering process is integration. So integration is in essence, the beginning of putting it all back together. What we've done so far is look at a very broad problem statement, look at those needs. Look at what operational requirements and take it all the way down to a system design. Now what we're doing with that system design is assembling it and putting it together. So integration is you're looking at the different pieces and then putting them together to realize the final system. It is a methodical process, which you don't want to do in systems integration, is when you start assembling the parts, not having strategy to try to figure out how you're going to put it all back together. You have all these different elements that you have meticulously designed to put together. Now you gotta figure out how to put them back together and realize them so that is just not assembled in a very haphazard way. When you start integrating, you want to make sure that, it's clear how it's going to be put together. You want to make sure who's involved in the process. So, those that are actually in the design process can help you, as well as those who are going to take it later and test it can help you. Recognize when you integrate, there are different types of elements within your system. There's software, there's hardware, and in many cases, there's people and the process. So making sure you're aware of who are your stakeholders in the assembly process. Also, there are logistics. Often forgotten, you are going to assemble this. How are you going to get the parts all together at the same time to be able to assemble, as well as there is a series of documentation. People have taken a lot of time to design the system. There should be a series of documentation, you have needed to build a different type of integration documentation to complement the design. So make sure that that is available and clear, external and internal. That means internally, as you build with your team as well as externally, as you integrate the system with external stakeholders. As we continue with the discussion of systems integration, stage 10 in the systems engineering approach, we cannot get sloppy in terms of performing this function. Oftentimes we think of the design process as the fun part, but one of the most challenging elements of the system engineering process is the integration. Remember what we've done, is we've articulated the problem and we brought it down to an engineering solution. Now what we're doing is bringing up the backup, assembling it, and integrating and make sure to address as the original problem statement operationally. We must go through this cycle or else we will not achieve our objectives. So it's very clear you need to maintain requirements traceability. So recognize what the requirements are, what the design was, and then when you start to integrate, doesn't actually achieve those requirements. Make sure that you avoid basically integrating the find problems. Work very hard early on to make sure that your design is clean, so when you're integrating, it's a very efficient process. Also make sure that you maintain good configuration control, what does that mean? You will have so many elements associated with your complex system, system to system or enterprise system. It is easy to lose control about what version is which each element and what version is the entire system. If you do not keep track of that, you will lose configuration management and you will be assembling probably the wrong elements. Make sure that you understand the risks, and these risks can be technical. They can be logistic, they can be scheduled, they can be cost, they can be all kinds of risks. So when you bring those together, be very systematic, have reviews often and be very clear and meticulous how you're bringing these things together.
