My software project · Beta
Klinik Wissen 360
Find and maintain clinic knowledge from approved sources
I am developing Klinik Wissen 360 as a knowledge system for an organisation’s internal standards, processes and training knowledge. The intended foundation is content that the clinic can lawfully provide and has professionally approved. Specialist literature and publisher connections remain optional additions.
The development status and target concept are described separately. A visible interface is not operational approval for an organisation.
Klinik Wissen 360 · Knowledge flow
Knowledge with a clear foundation.
Hospital documents
Approved SOPs, processes and training knowledge.
Version & approval
Assign validity and professional responsibility.
Search & original source
Find knowledge and open the underlying version.
AI when needed
Optional processing within the permitted uses of each source.
Schematic target concept · no live interface or patient data.
PDF · 6 pages · 37 KB · English · Updated 14 November 2026
Beta version
I am currently developing Klinik Wissen 360 in internal development and demonstration environments. The Beta is not a finished, approved product version. Market readiness is planned for 2027; this is neither a binding availability date nor approval for operation at a particular organisation.
- Publisher-independent core as the target concept
- Internal development and demonstration
- External evaluation requires authorisation
A software project by Moritz Wagener
Product concept
Klinik Wissen 360 is knowledge infrastructure — not a search box and not a chatbot.
A complex buying process and the search for valid clinic knowledge raise the same basic question: what information is missing for the next decision? In my sales consulting, I clarify participants and decision criteria. With Klinik Wissen 360, I am developing the corresponding knowledge architecture as a product of my own.
Clinic knowledge as the foundation
The focus is on sources that an organisation may lawfully provide and approve for the intended use.
Provenance and responsibility
For the next development stages, I plan to record provenance, rights holder, version, validity, review date and professional responsibility for each source. Missing information should be clarified before processing.
Approvals remain distinguishable
Original sources, locally approved content and AI results should remain distinguishable. An external update must not automatically replace a local SOP.
Usable without generative AI
Search and original-source viewing should work independently of generative AI. The knowledge collection, rights and approvals should remain intact when providers change.
AI-supported assessments are working aids. Source references and identifiable gaps support review but do not guarantee completeness or accuracy. Results must be checked against the original sources; professional judgement remains with the responsible people.
Verified development status
Source references and personal notes in a knowledge space
Internal development status: the Beta supports knowledge spaces with source references and personal notes. The interface explicitly states that no content has yet been analysed automatically. Example of a possible B2B sales application: a knowledge space could group approved product information and evidence for a proposal; later AI analysis would be a separate step requiring review. This does not describe a client deployment.
Binding development requirements
Source rights and quality first
The following requirements describe further development. They do not claim that complete rights management or professional operational acceptance has already been implemented.
Clarify source rights separately
Storage, indexing, quotation, AI summaries and model training must be assessed separately for each source. Public accessibility or a clinic subscription does not automatically permit commercial AI processing. No automatic full-text import is envisaged when rights are unclear. Without separate permission, clinic knowledge must not be used across clinics or for model training.
Maintain local rules in a controlled process
Original sources, locally approved knowledge and AI drafts must remain distinguishable. Changes, contradictions, outdated and withdrawn sources require professional review. External recommendations must not automatically overwrite local SOPs. Search and original-source viewing should remain usable without generative AI.
ChatGPT connection and billing
The requested ChatGPT connection and use of a customer’s own plan have not been released as a production connection for Klinik Wissen 360. I do not equate sign-in with permission for usage, data processing or costs. Unavailable AI functions must remain blocked; another model or a billable replacement account must not take over silently.
The following sections describe the licence and procurement model and the conditions to be agreed. The routes actually available in a personally authorised test are checked separately for its agreed scope. Retaining this text is not a new operational acceptance; the stated rights and publisher conditions remain applicable.
LICENCE MODEL
Bring Your Own License — your publisher licences remain yours
Klinik Wissen 360 clearly separates SaaS access from content licences. You use the platform while your existing publisher agreements remain unchanged.
Own licence (BYOL)
Stored licence information can indicate an access route. Whether your existing licence covers the specific title and intended use, and whether the full text is actually accessible, must be checked with the provider. MWC is not a contracting party of the publisher and does not charge a handling fee for this route.
Procurement via MWC (Single Creditor)
If a licence is missing, Moritz Wagener Consulting can procure access, act as the sole invoice issuer and list a transparent handling fee as a separate line item.
Both routes in parallel
Per tenant you can freely choose which titles run via own licences and which are procured through MWC. The licence route is visible on every result.
The terms of use of the respective publisher apply regardless of the licence route.
The following privacy notes remain unchanged. Before external evaluation, the actual data and access routes used within its approved scope must be checked against them. Beta status does not waive privacy or rights requirements.
DATA PROCESSING & FULL-TEXT ACCESS
Data used in searches and full-text access
Klinik Wissen 360 supports searches, knowledge organisation and the assessment of full-text access routes. These notes explain which data is processed during searches and full-text access.
Data used for operation and traceability
- Account and tenant data: name, e-mail address, role and organisation membership.
- Licence and access configuration of your organisation: publisher licences, network ranges, remote access.
- Technical logs of full-text accesses as billing and publisher evidence — without full-text content.
Searches and external access
- External searches transmit search terms and, where supported by the source, selected filters to external databases or providers. The providers contacted depend on the selected source.
- Do not enter personal information or patient data in search fields. Such information is not automatically removed from search requests.
- A direct publisher link opens the respective provider’s service. Full-text availability depends on that service and your organisation’s access rights.
- No sale or disclosure of usage data to third parties for advertising purposes.
Direct links: When you open an external full-text link, your browser connects to the provider. The provider receives technical connection data, including the IP address used. This may vary depending on the network, VPN or proxy. Please consult the respective provider’s privacy information.
The complete data protection information for Klinik Wissen 360 is provided to your organisation before the contract starts.
Beta structure
11 work areas in the Beta development version
The eleven visible areas describe the current structure of the Beta. Visibility does not mean a fully approved function or acceptance for an organisation. I am working towards a simpler end-to-end flow of sources, a knowledge space, search and review; the eleven areas are not a promise of eleven finished products.
OverviewVisible in the Beta
Beta area for orientation in the knowledge collection and access to open tasks; the data available for a particular organisation must be checked before evaluation.
Knowledge collectionVisible in the Beta
Beta area for organising internal content; complete source rights, versioning and professional approvals still require separate acceptance.
ResearchVisible in the Beta
Beta area for finding and comparing available source references. Metadata or abstracts are not an analysis of full text that cannot be accessed.
SourcesVisible in the Beta
Beta area for provenance and stated access routes; stored licence information proves neither full-text access nor permission for AI processing.
Sources by categoryVisible in the Beta
Existing category view in the Beta system; the target is to support search rather than create a second competing knowledge collection.
Knowledge spaces and notesVisible in the Beta
The existing development version supports storing source references and personal notes. This does not imply automatic analysis of their contents.
DocumentsVisible in the Beta
Beta document-management area. Technical file checks do not replace malware checks, usage rights or professional approval; the complete import process still requires acceptance.
AI analysis – development targetPlanned
The central conversation area currently has no enabled automatic content analysis. Source-grounded answers and their approval are a separate development step.
Optional specialist contentVisible in the Beta
Optional Beta area for access and procurement questions. A price on request is not a confirmed price; neither an enquiry nor an AI result may automatically trigger an order.
Knowledge tasksVisible in the Beta
Beta area for assigned tasks and responsibilities; not an additional CRM or a replacement for the organisation’s professional responsibility.
Access and settingsVisible in the Beta
Beta area for organisation and access settings. A visible settings area does not establish complete operational or privacy approval.
Demo, access and professional responsibility
Client knowledge and the public demo are strictly separated. The demo shows prepared examples; public sources can be queried in the research area.
Separate modes
Demo mode shows prepared examples and can query public sources, with no access to production client data and no administrative functions.
Authorised access
I currently use protected access for internal development and demonstration. External evaluation is possible only after personal agreement and separate authorisation. There is no open registration.
Make missing foundations visible
For further development, I plan visible source versions, professional responsibility and review notes. If an authorised, professionally suitable foundation is missing, the system must show the gap or abstain from answering. A source identifier alone does not establish that a statement is correct.
What I intend to secure in further development
The knowledge collection should remain independent of individual search, embedding and language-model providers. I plan exports with metadata and approval status within the relevant rights, plus practical tests for provider changes, recovery and permission separation between organisations. These checks are development tasks, not operational evidence already delivered.
Development, demonstration and possible evaluation
The three steps represent different approval stages.
My development project
I am developing Klinik Wissen 360 myself as my own software project.
Public Beta demo
The demo shows prepared examples and selected public research routes; it is not evidence of operation at a real clinic.
Personally agreed evaluation
An external test requires a separate agreement on scope, rights, responsibilities and approvals. Installing the product does not by itself provide such access.
Planned organisational pilot
A bounded process within one department
For the first pilot, I plan a bounded organisational use case in one department. The starting proposal is 20–30 approved documents and around 50 professionally reviewed questions. Patient data and individual diagnostic or therapeutic recommendations are excluded. A pilot partner and professional reviewers still need to be found. Intended purpose, privacy, usage rights and regulatory requirements must be reviewed separately before starting. The proposed sample is not evidence of clinical safety.
Evaluation must fit the task
If you want to find and maintain organisational clinic knowledge more effectively, describe a specific process. I will discuss the development status with you and the prerequisites that must be clarified before a possible evaluation.