teamcompass.jp

What It Is

Team Compass（チームコンパス） is a nursing documentation and care plan support system provided by Japan’s Innoxia Inc. for hospital nursing departments. It is not positioned as a general-purpose electronic medical record system, but rather as a departmental system for hospitals, helping nursing teams reduce narrative-style documentation, improve record standardization, and use the time saved for patient care.

Core Capabilities

The product consists of three core components: PCAPS (Patient Condition Adaptive Path System), which provides appropriate nursing plans based on the patient’s condition; “看護ナビ,” which supports real-time bedside documentation using standardized observation items; and MEDIS マスター, which standardizes nursing terminology, improves documentation consistency, and makes integration with other systems easier. The system supports nursing care plan creation and daily observation records, while helping improve medical safety by reducing missed documentation items. Public case studies show that some hospitals reduced nursing documentation time by about 30% after implementation, and high-frequency medical safety-related incidents decreased by an average of 24% in before-and-after comparisons.

Pricing and Deployment

Its business model is subscription-based. In principle, added features do not incur additional charges beyond the monthly fee, and contracts are generally renewed annually. Specific pricing is not publicly disclosed and must be requested via a form or sales inquiry. It should be noted that connection fees charged by electronic medical record vendors for integration with Team Compass are billed separately. For deployment, both cloud and on-premises options are supported. If on-premises deployment is selected, the server can be prepared by the vendor, or hospitals can consult with sales about virtualizing the system on existing servers.

Integrations and Support

Electronic medical record integration is a key selling point of this product. The system can connect with information such as physician orders and basic patient data. By default, integration is mainly one-way, though some hospitals use two-way integration for data needed for vital signs or regional collaboration. It is not limited to specific electronic medical record vendors, and the materials mention integration track records with vendors such as Fujitsu, NEC, SSI, and CSI. Support is fairly comprehensive, including operation manuals, YouTube video guides, pre-launch briefing sessions, OKWorks, email, phone support, monthly regular meetings, hospital-dedicated support phone lines, and dedicated account representatives.

Pros, Cons, and Best Fit

Its strengths are its vertical focus on nursing scenarios, a rich set of implementation case studies, quantified evidence of impact, and flexible deployment and electronic medical record compatibility. Its drawbacks are opaque pricing, a recommended implementation period of 6 to 9 months, and relatively high requirements for project coordination between the hospital’s nursing department and information systems department. In addition, publicly available materials do not disclose detailed security compliance information, permission models, or open APIs. It is best suited for Japanese hospitals that want to standardize nursing documentation, reduce overtime, and increase bedside care time, especially institutions that already have an electronic medical record system but face a heavy nursing documentation burden.

Access in China

There is no reliable textual basis for determining website or service accessibility from mainland China, so its status is unknown.