CMDB class for HL7 interfaces and FHIR APIs

[changeman]

We are working on fleshing out our SN CMDB instance with logical CIs and have struggled with finding a default CI class suitable for healthcare interfaces, both classic HL7 v2 over TCP/IP as well as FHIR APIs.   At its simplest, an interface sends data from one system to another, whether triggered to push or pull, synchronous or not (most HL7 being synchronous).  In terms of  CI relationships, an HL7 interface connects a sending endpoint to a receiving endpoint, whether there is middleware in the middle (Cloverleaf, Rhapsody, Mirth, Corepoint, etc.) or not.  Ideally, an interface CI would connect endpoints at two levels: server (with IP/listening port or URL listed) and application, or at least through a server CI link to an application/business application CI. 

We couldn't find anything in the list of default CIs (going off of documentation for Tokyo) that would clearly accommodate this concept, but I'm sure we're not the first ones facing such a challenge.  One recommendation was to use cmdb_ci_service, which is defined as "IT Service that directly supports a Business Process (ITIL)." However, its suggested relationship seems to imply closer alignment with one of the endpoints whereas in our thinking the endpoints are equal relationship partners.  Service as a CI and an actual SN service might confuse matters more.

How have other organizations configured their HL7 and FHIR interfaces in SN CMDB?

[Josh Baumann]

Replying to this older thread to highlight the Digital Integrations APM functionality that was release with Utah.  

https://docs.servicenow.com/bundle/utah-application-portfolio-management/page/product/application-po... 

We haven't leveraged yet but plan to start taking advantage of this new functionality.