Skip to main content

Consider a healthcare facility with independent software systems for each department. A system engineer is tasked with developing a message exchange system between the departments based on the HL7 Version 2 standards. She begins by describing the interfaces and content exchanged between departments based on SysML interface blocks. The flow properties of these interface blocks are typed by HL7 message types as well as a direction. Next, a SysML internal block diagrams (IBD) of the system is developed. Proxy ports on the parts and the item flows between the ports are used to represent the HL7-based communication between the software systems of the departments, as illustrated in the top figure.

healthcare facility clinical data ibd IBD (partial) of electronic information system connecting healthcare facility departments, selected connectors with their item flows highlighted

While developing and testing the message exchange system, the system engineer will need to keep track of issues and problems that arise. JIRA is an online tool widely used for this purpose.  The system engineer can view and track issues by message type, using Syndeia™ to create reference connections between the SysML model (left side of lower figure) and issues in the JIRA project (right side).

Creating a reference link between SysML and JIRA using Syndeia Creating a reference link between SysML and JIRA using Syndeia

The whitepaper and the sample SysML model, covering all 5 parts of this blog series, is now available for download as below.  Learn more about how Model-Based Engineering can impact the biomedical and healthcare domains. Email us for any questions.

Download

  • Download Technote and SysML model here

Related blog posts:

Related Posts

Pipelines Part 3 – Matching Requirements to Parts using Syndeia Digital Pipelines

We’re continuing our blog series on using Syndeia digital pipelines to execute real world use cases in systems engineering. In Part 2, we demonstrated a digital pipeline that ...
Dirk Zwemer and Gregory Seeds

Pipelines Part 2 – Gap Analysis between Requirements and Tests

Demonstrating measurable ROI from digital engineering is just as important in driving enterprise adoption as customer mandates, e.g. DoDI 5000.97. In particular, the concept of ...
Dirk Zwemer and Gregory Seeds

Pipelines Part 1: Quick Introduction and Demo

Syndeia Pipelines automate digital engineering workflows by orchestrating complex, multi-step tasks, such as ETL operations, cross-repository queries, model transformations/syncs, ...
Manas Bajaj

Christmas at the North Pole, Powered by Pipelines🎄

While the rest of the world is busy hanging lights, doing last minute gift shopping, and sipping cocoa, the North Pole is deep in digital engineering mode. Snow is falling, elves ...
Manas Bajaj

What’s New in Syndeia 3.7? - Part 1

We are excited to release Syndeia 3.7, the next generation of our digital thread platform for integrated digital engineering. Check out the latest features in less than 5 minutes ...
Dirk Zwemer

Model-Based Systems Engineering for Autonomous Vehicles, Part 16 – Custom Dashboards

In Parts 1-10 of this blog series, we built a digital thread for an autonomous vehicle system to demonstrate how a federation of models in different software tools can become a ...
Dirk Zwemer

Model-Based Systems Engineering for Autonomous Vehicles, Part 15 – Digital Pipelines

In Part 14 of this series, we developed a custom script to calculate project metrics for our Autonomous Vehicle digital thread project. The value of this information is greatest ...
Dirk Zwemer

Model-Based Systems Engineering for Autonomous Vehicles, Part 14 – Open REST API

Syndeia has been developed as an API-first enterprise application, i.e. the full capabilities of the software are exposed through an open REST API with the understanding that the ...
Dirk Zwemer

Model-Based Systems Engineering for Autonomous Vehicles, Part 13 – Digital Reports

A key function of Digital Threads is to be able to answer questions about project status in real-time without the overhead of data collection, status reports and meetings. In this ...
Dirk Zwemer