Can AI agents automate CosDoc?

The best evidenced path into CosDoc is the vendor-described CosDoc API, used by CosDoc+ and by welfare-technology partners. DIPS Front's public security document states that CosDocAPI exists in several versions, with an original SOAP/WCF surface and newer .NET Standard REST services, authenticated through a DIPS Front Identity Server token or an authorised application user, plus a mandatory device id. The same vendor pages say the API can connect sensors, medicine cabinets, alarms, deviation systems and route optimisation, and that national services include VKP, Kjernejournal, DigiHelse and SvarUT. Norsk helsenett independently lists CosDoc among the municipal care EPJs integrated with VKP for automated journal read and write. Public technical reference is still contact-gated: the customer documentation index tells readers to request technical docs, and no self-serve endpoint catalogue or first-party auth guide was opened. A sister-company cloud product, Aidn, is described as a future municipal journal and is not this identity. Hospital DIPS is a different product. No official MCP, CLI, SDK or computer-use probe was established.

Best path today: api · Overall automatability: 4/10