05 Sep MDLink Integration Manual/Instructions
TheMD Link Integration Strategy
MD Link is a unique and innovative platform for integrating multiple heterogeneous systems. System integrators can use MD Link to create custom, process-oriented interfaces that can be run on virtually any computing platform.
MD Link’s integration strategy can be summed up as:
- Support the widest-possible range of data, application and network standards with
- Easy-to-use data mapping tools leverage transformational power of XML
- Process-oriented Interfaces support complex detailed business logic
- Plug-in architecture supports custom development of visual Interfaces for legacy
- Design Studio requires no Server for testing and debugging
- Interface-based licensing reduces cost for small to medium implementations
- Processes can be distributed across the network, so that processing is performed
closest to the user or data
Java technology for portability, compatibility and security
MD Link Studio and Server are based on the Java 2 Standard Edition and support almost any operating system, without the need for complex and expensive Enterprise Servers.
Interface Adapters are Java plug-ins that support Visual Mapping of Event, Task and Resource input. Custom Plugins can implement any proprietary or open-source Java library.
At run-time, these plug-ins generate XSLT templates for powerful transformation of content and structure of almost any data type.
Leverage XML for Industry Standard Data Transformation
Leverage XML for Industry Standard Data Transformation XML is the industry standard language for data interchange. MD Link Adapters exchange data automatically as XML and use XSLT templates for content and structural transformation of any type of documents. The visual Design Studio hides the complexity of XML, while supporting advanced XSLT template customization. A wide range of XPath functions support text, math, date and other specialized data conversion requirements.
Easy to Design Process-Oriented Interfaces
System-to-interfaces are usually more than simple point to-point queues of data feeds. MD Link supports complex processes that extend the definition of the term“Interface” to mean “create your own process-oriented interface”.
To create fully functional business interfaces, you need tocreate multi-tasking processes that have many steps.
MDLink’s Event-driven any-to-any Task Mapping model letsyou create complex solutions to Interface problems.
MD Link Development Cycle
MD Link supports a role-based, cyclical development model. Designers create Interfaces and Processes. Managers deploy Processes and run Services. Users monitor Services and Transactions.Auditors verify transaction output against Interface definitions. If changes are required, the Designer can implement them.
Interfaces are the customized mapping of data, application and network resources. MD Link’s growing list of Interface adapters provide visual customization and data mapping. (See Interface Adapters)
Processes link Event, Task and Resource Interfaces to create active solution Services. (See Design Studio)
Services are processes that can be hosted on any server. Services monitor Interface status and Transactions activity.(See Server Console)
Transactions are Service requests that can generate documents, messages and database updates. (See Server Console)
MD Link Design Studio
The MD Link Designer Studio lets Designers (Programmers and/or Analysts) create visual interface mapping solutions. The result is a Process that can run as a Monitored Service and generate Transaction Logs.
Events, Tasks and Resources
All types of Interface Adapters can be customized to point to data sources, schema definitions and metadata. Events monitor data resources and act as application “listeners” that invoke a Process. Tasks are specialized functions for accessing data, mapping and conversion, linked together to form complex transaction interfaces. Resources access static reference information and default values for inclusion into a Task. Error information and working data can be passed to an error-handling process, which can send email or text alerts. Processes always start with an Event, such as a new file in a folder or message in a queue. The incoming Event data record is passed to a series of linked Tasks, all of which can access diverse sources of information.
All types of Tasks have a visual mapping screen for drag-and-drop mapping of source
data to target data. Any Task can be linked to any other Task type, resulting in a
common mapping view and unlimited combinations of Interfaces can be achieved. The
Advanced Target Mapping window on the bottom-right, supports custom coded XSLT
templates, as well as text, date and math functions.
MD Link Server Console
MD Link Processes are saved by the Design Studio as XML solution files containing all the
Interface definitions. The MD Link Server can load these XML solution files and run the
Process as an active solution Service. While it is running, it will accept data via Event, and
then transform the data via XML templates.
While the Process is running the Monitor displays the color-coded status or each Interface
in a Process. Each Interface shows latest activity and will turn yellow for warnings, and red
for errors, such as network trouble. Each interface can be paused and resumed by a
As each Event and Task executes in sequence, Log records are generated that show
informational, warning, error and debug information. The level of details can be set,
depending on debugging and performance objectives.
Interface Adapters provide drag-and-drop access to a variety of data, application and communication protocols,
The plug-in Java programs provide a graphical representation of each interface’s unique properties and data
structure. The input or output from any data source can be linked together, offering unlimited possibilities for creating
customized integration solutions. Simply drop these plug-ins into the MD Link Studio and begin creating customized
integration processes. Developers can create custom Interface Adapters using Java or JPython scripting languages.
Health Level 7 Protocol (HL7)
- Parse & Generate HL7 2.X messages
- Parse, Generate HL7 3.0 XML
- Send and Receive HL7 over TCP/IP or
- Web Services
Remote File Transfer
- Send Data Files using File Transfer Protocol
- Exchange Files between Remote Systems
Database Management Systems
- Interface any Relational Databases
- Structured Query Language (SQL)
- Exchange Data with Message-Oriented
Middleware (MOM) Applications
- Java Message Service (JMS)
- Parse, Generate and Serialize XML
- XML Schema Definition (XSD)
- Document Type Declarations (DTD)
Formatted Text Files
- Design, Parse and Generate Text Files
- Fixed or Delimited Fields
- Hierarchical Record Matching
- Send data to any web application through standard web methods or SOAP.
Generic TCP Sender Task
- Define your own TCP-based protocol to communicate with unique legacy systems
- Simple Mail Transfer Protocol (SMTP)
- Post Office Protocol (POP)
- Dynamic Message Content
- Invoke other applications on your machine
- Utilize third-party documentation conversion software
- Monitor Folders for New or Changed
- Load Documents into Solution for Processing
- Define Customized Tasks using Python Scripting Language
- Utilize third party Java Libraries for Extended Functionality
Scenario 1: Health Level 7 (HL7) Patient Admission Interface to Nursing
This scenario shows how to receive, parse, generate and send HL7 messages. An Admissions message queue is monitored using the HL7 Socket Event. The message is parsed, then a Nursing HL7 record is generated. Finally, an HL7 Socket message sends the converted Admission record to a Nursing System.
The HL7 Generator Task’s Customizer shows:
- HL7 Message Version
- HL7 Message Type
- Not using a Customized
- Writing to a local folder
The process also shows a proprietary format EDI text file written and sent to another system via File Transfer Protocol (FTP).
The HL7 Generator Task’s Data Mapping window shows:
- Source is A01 (Admission)
- Target is also A01 (Nursing)
- The Advanced Target Mapping is converting last name to upper-case characters. This is an example of using XPath function.
Scenario 2: Website Monitor and Alerts
This scenario shows how MD Link can interface with other systems via web pages, using the HTTP Post Task. In
the scenario shown, a Timer Event triggers a form post and attachment upload to a website. After waiting for an
email, the solution can send a text message if an error occurs on any Task.
The “Upload Attachment” HTTP Post Task is highlighted.
This process illustrates:
- How to create a “Monitoring” process using Interfaces
- Interface Data can be passed from oneTask to another
- How Text Messages can be sent on a Task failure (example: website is not responding)
- The Data Mapping panel show the session ID passed from the previous task
- Both Task and Resource (literal values) are on the Source (left) and the Target(right).
MD Link is unique and innovative software for integrating heterogeneous systems by creating Java-based software “services” that enable an enterprise’s data, application and network resources.