Logo
English (US) Français
Submit a Ticket Sign in
  1. OceanMD
  2. Integrations
  3. Integrations FAQ

Why was my Cloud Connect server deauthorized?

Avatar
OceanMD Support
Edited January 11, 2019 15:59
Follow

  

You may have received an email notifying you that your Cloud Connect configuration has been de-authorized. A common cause is due to EMR vendors conducting maintenance to ensure our clients with a secure and stable Ocean API connection. Cloud Connect may also be de-authorized manually by an admin user from the Cloud Connect portal.

To re-authorize your Cloud Connect configuration, please refer to this support guide: Re-Authenticating Ocean Cloud Connect.

Previous Article Next Article
Have more questions? Submit a request

Integrations FAQ

At A Glance: Integrations FAQ Read All FAQs View All Terms Return To Guide Return To Getting Started Guide Read All Articles
  • Can active referrals be resent to an eReferral API endpoint?
  • Is there an authorization process for systems to connect/integrate with Ocean for clinical, administrative, or analytic purposes?
  • What EMR field does Ocean use for Alternate ID?
  • Which EMR demographics are not automatically updated by Ocean?
  • Does Ocean work with Avaros EMR?
  • How can I display Ocean Patient Reference Numbers in my appointment scheduler?
  • Why was my Cloud Connect server deauthorized?
  • How do I sync a new provider schedule into Ocean?
  • My notes aren't appearing in my patient's chart. What do I do?
  • What situations cause note downloads to fail?
See More

© 2024 OceanMD