Healthcare Locations (New or Moves)

[Jennifer Red]

I've been asked to find out how other healthcare organizations handle new locations or moving locations... not necessarily specific to ServiceNow itself. We have Epic as a system, and it seems that there is no set way with our IT Epic folks to create these in their side. Then, we're getting requests for locations be created within ServiceNow to match. How do you all communicate this across the board? Would it be something as simple as it being a catalog that would generate multiple tasks for Epic, etc.? I think the biggest challenge with that would be adoption. A lot of people are used to their current flow and altering that may be challenging, but I don't think that can be avoided if we go that route.

[Josh Pirozzi]

Hi @Jennifer Red,

We're experiencing a similar situation with our organization. We use FM Systems as our Location Services platform and went through a manual effort to export this location data points (Building / Floor in building / Room on floor in building) and add them into our Locations Table. Current use cases / setup are, on the Incident Form or Catalog Item, we reference the Location Table and limit the results based on which conditions are needed by having a 'Location Type' on each Location Entry. 

The team who manages FM doesn't keep the data up well, and we're typically notified on Location entry changes 6+ months after they take place which is where we've started conversations with the managing teams to see if they'll be able to either:

1. Provide a connector from FM to ServiceNow that runs weekly to keep the Location Table updated.
2. Grant that team access to the Location Table in ServiceNow and suggest a transition over to using ServiceNow natively. 

[Jennifer Red]

I understand that. We also have flags on our performance health from SN because of the various locations having the same rooms, floors, etc. But that's a different issue that we're trying to navigate.