Search
Talk with us

Systems and integrations

Connect your systems around a clear care need.

Start with the information that would help your people and the work it should support. We review your existing systems with your team, agree the connections, and confirm what needs configuration or implementation.

Discuss your connectionsSee the platform

What is available

Know what is ready and what needs work.

A useful connection has a purpose, an agreed source of information, and someone responsible for keeping it working. Availability is confirmed for your program; a standard or device category is not a list of connected vendors.

Current platform foundation

genusConnect uses Amazon Cognito for authentication. The platform includes content-authoring and delivery tools, and device-management views. The options enabled for your program are confirmed during scoping.

Program configuration

Agree the people, roles, content, supported delivery options, and workflows for your organization. Configuration determines how the selected tools work together in your program.

Scoped implementation

Partner single sign-on, HL7 v2 or FHIR connections, and live device connections need their own requirements, compatibility review, and testing. Work and availability are agreed for each project.

Planned capabilities

Roadmap ideas remain separate from an agreed live scope. For example, automatic program tuning from engagement patterns is planned; people currently review feedback and decide how to change a program.

Current authentication; scoped partner SSO

Connect staff access with the right permissions.

genusConnect uses Amazon Cognito for current authentication. Single sign-on through your organization’s identity provider is scoped implementation work.

With your identity team, we evaluate SAML or OpenID Connect (OIDC), the roles staff need, and the organization and site access each role should have. Signing in and permission to see information are separate parts of the setup.

  • Agree identity-provider configuration, role mapping, and multifactor authentication requirements.
  • Plan account creation, staff changes, access removal, and session behavior.
  • Test the staff journey and access boundaries before enabling the connection.
More about staff sign-in

Scoped implementation

Bring clinical information into an agreed workflow.

HL7 v2 and FHIR are approaches to exchanging health information. A connection depends on the interfaces your system makes available, the information needed, and permission to use it.

We scope the work with your IT team and system vendors. The care need comes first: who needs the information, what they will do with it, and how the connection will be checked before live use.

  • Confirm the sending and receiving systems, data fields, direction of exchange, and patient-matching approach.
  • Agree consent and access rules, error handling, and responsibility for supporting the connection.
  • Test each agreed interface and validate the workflow before introducing live health information.
HL7 and FHIR scoping details

Program configuration and supported formats

Put your knowledge where people can use it.

Your team can prepare resources in the Partner Portal and use them through the Care App, Care Wall, or supported activities. Bring your guidance, documents, media, and questions; agree the audience, placement, and review process.

Supported imports, exports, and playback options vary by tool and client. An uploaded document, an interactive resource, and a live connection to another system are different kinds of work. We confirm the formats and information flows your program needs.

  • Identify the source, permitted use, intended audience, and person responsible for keeping the resource current.
  • Agree who reviews and publishes content, and what can be reused in another setting.
  • Scope any external data exchange separately, including access rules and handling when information is missing or out of date.
Where genusAI fits Use assistance within the permissions and review process of the workflow.

In supported authoring workflows, genusAI can help prepare or revise drafts. People check the sources, accuracy, suitability, and rights before deciding what to share.

Connecting a system does not automatically give an AI service permission to use its information. Agree the sources and uses permitted for the workflow, along with the people responsible for review.

Content and pathwaysHow genusAI supports the work

Current views; scoped live connections

Confirm the device, the information, and the response.

The Care App includes device-management views for personal and community contexts. Device records and simulated readings can help explain an experience; a live connection requires a supported, configured device and service.

Review compatibility, available readings, update frequency, reliability, and supported actions for your setup. Agree who can see the information, how interruptions are communicated, and who follows up.

  • Keep simulated examples distinct from live readings.
  • Confirm the source, timestamp, and meaning of information before someone relies on it.
  • Keep personal check-ins and appropriate care-team follow-up in place. These tools do not replace emergency services or a dedicated safety system.
Device views and connection requirements

Responsibilities

Give every connection a clear owner.

genusConnect supports managed AWS deployment, with a separate workload account available as a scoped option. We agree environment ownership, region, permissions, integrations, and support responsibilities for the project.

Your program, IT, security, and system-vendor teams bring different parts of the picture. Together, we agree the operating arrangements and validate the workflow before using live health information.

Access and information use

Agree who administers access, the purpose of each exchange, permitted uses, and the applicable data-processing and Business Associate Agreement terms.

Operation and support

Document who supports each connection, handles errors, and responds to incidents. Agree retention, backup, and recovery expectations for the deployment.

Scope and change

Confirm the selected tools, configuration, implementation work, and validation steps. Review dependencies, licensing, support, and data-return arrangements in the applicable agreements.

Shared learning

A useful resource or lesson may be shared with the necessary permission. Working together does not open access to another organization’s private records or authorize automatic cross-partner AI training.

Read the security overviewPlan your rollout

For technology partners

Bring a useful capability into the care experience.

If you build a device, service, or software product, start with the care need it addresses and the people it would support. We can review your available interfaces, the information flow, and a focused first scope together.

Developer-kit components, access, product boundaries, licensing, hosting, and support are matters to agree for the project. A connection or independent product arrangement needs its own scope; it is not implied by joining a partner conversation.

Discuss your product or connectionQuestions for developers and product builders