TARDOC Bill creation / transmission - Revision history

Stefanseiler: /* See also */

2026-05-06T21:21:44Z

Stefanseiler: /* Billing Fundamentals */

2026-05-06T21:21:32Z

Billing Fundamentals

@@ Line 217: / Line 217: @@
 ** '''Output:''' <code>[Original Text] [Free text, pre-2026]</code>
 ** '''Example:''' <code>Cataract, right eye [Free text, pre-2026]</code>
 == See also ==

Stefanseiler at 20:20, 6 May 2026

2026-05-06T20:20:47Z

← Older revision		Revision as of 20:20, 6 May 2026
Line 254:		Line 254:

	* [[Kordeus Core]]		* [[Kordeus Core]]
			[[Category:Kordeus.CORE Epics]]

Stefanseiler: /* See also */

2025-09-29T12:44:33Z

Mionamilosevic at 09:43, 29 September 2025

2025-09-29T09:43:16Z

← Older revision		Revision as of 09:43, 29 September 2025
Line 22:		Line 22:
	\|		\|
	* <u>Doctors</u> can not edit anything in the form without having started the examination timer		* <u>Doctors</u> can not edit anything in the form without having started the examination timer
	* If the encounter is already signed, the doctor can press the "Start-Timer" again, which re-opens the ~~timer~~		* If the encounter is already signed, the doctor can press the "Start-Timer" again, which re-opens the encounter
	* Other users can edit anything at any time		* Other users can edit anything at any time
	* Doctors can not leave the form without having stopped the examination timer		* Doctors can not leave the form without having stopped the examination timer

Mionamilosevic at 08:17, 24 September 2025

2025-09-24T08:17:43Z

← Older revision		Revision as of 08:17, 24 September 2025
Line 107:		Line 107:
	* Admin can create edit, rules by this schema: (1) LKAAT positions and (2) materials are created out of a detected service		* Admin can create edit, rules by this schema: (1) LKAAT positions and (2) materials are created out of a detected service
	\|Materials TBD, handed out, consumed? They are currently products and will be billed as WAR as they come from different catalogues.		\|Materials TBD, handed out, consumed? They are currently products and will be billed as WAR as they come from different catalogues.
			Keep same UI for medical services
	\|-		\|-
	\|Billing preparation screen		\|Billing preparation screen
Line 115:		Line 116:
	* LKAAT positions can be added / removed manually		* LKAAT positions can be added / removed manually
	Please note, that all encounters till 31.12.2025 must use the old Billing-Flow, Encounters from 01.01.2026 must use the new billing flow		Please note, that all encounters till 31.12.2025 must use the old Billing-Flow, Encounters from 01.01.2026 must use the new billing flow
	\|~~TBD~~		\|Logic stays the same for products and other catalogues than LKAAT/TARDOC
	\|-		\|-
	\|Billing creation flow		\|Billing creation flow
Line 125:		Line 126:
	\|Grouper and mapper jsons do not exists. Ther are functions in TARDOC matcher.		\|Grouper and mapper jsons do not exists. Ther are functions in TARDOC matcher.
	Understanding of the logic is off.		Understanding of the logic is off.

			Update: Discussed with Stefan.
	\|-		\|-
	\|Bill upload		\|Bill upload
Line 133:		Line 136:
	\|First two points have to be reviewed, on sign the date is set.		\|First two points have to be reviewed, on sign the date is set.
	This would obsolete draft bills then.		This would obsolete draft bills then.

			Bill has to be signed
	\|-		\|-
	\|		\|
Line 142:		Line 147:
	* In the Test environment of Medidata (Seiler IPR AG - Webservice 1) we can upload files from Kordeus Integration		* In the Test environment of Medidata (Seiler IPR AG - Webservice 1) we can upload files from Kordeus Integration
	\|Who is responsible for setting up this?		\|Who is responsible for setting up this?
			See with SSeiler
	\|-		\|-
	\|Mid November		\|Mid November

Mionamilosevic at 07:51, 23 September 2025

2025-09-23T07:51:44Z

@@ Line 153: / Line 153: @@
+|
 |}
 == See also ==
 * [[Kordeus Core]]

Mionamilosevic at 13:15, 17 September 2025

2025-09-17T13:15:24Z

← Older revision		Revision as of 13:15, 17 September 2025
Line 31:		Line 31:
	* Timer stops on being more than 30 minutes inactive		* Timer stops on being more than 30 minutes inactive
	\|<u>Doctors</u> can not edit anything in the form without having started the examination timer TBD depending on the encounter		\|<u>Doctors</u> can not edit anything in the form without having started the examination timer TBD depending on the encounter
			How to handle Alex?
	\|-		\|-
	\|Create ICD-10 catalog to incorporate in the system		\|Create ICD-10 catalog to incorporate in the system

Marcostoeckli at 12:02, 17 September 2025

2025-09-17T12:02:47Z

← Older revision		Revision as of 12:02, 17 September 2025
Line 30:		Line 30:
	* When the doctor accidentally closes the browser, the timer is stopped preclose		* When the doctor accidentally closes the browser, the timer is stopped preclose
	* Timer stops on being more than 30 minutes inactive		* Timer stops on being more than 30 minutes inactive
	* Starting the
	\|<u>Doctors</u> can not edit anything in the form without having started the examination timer TBD depending on the encounter		\|<u>Doctors</u> can not edit anything in the form without having started the examination timer TBD depending on the encounter
	\|-		\|-
Line 37:		Line 36:
	* We have a searchable catalog (fulltext search) in some service, which can be searched realtime		* We have a searchable catalog (fulltext search) in some service, which can be searched realtime
	\|Please send it		\|Please send it
			https://medcode.ch/de/de/static_pages/api_documentation
	Free text diagnoses?		Free text diagnoses?
	Are diagnoses related to services?		Are diagnoses related to services?
	\|-		\|-
	\|ICD-Rule-Editor		\|ICD-Rule-Editor
			(not 1. Priority)
	\|		\|
	* The admin can create rules, which encounter data drives which ICD-10 diagnose with Tiggerconditions (AND OR connected) and a resulting ICD-10 Diagnose		* The admin can create rules, which encounter data drives which ICD-10 diagnose with Tiggerconditions (AND OR connected) and a resulting ICD-10 Diagnose
Line 47:		Line 48:
	\|-		\|-
	\|Service Detection Rule Editor		\|Service Detection Rule Editor
	(~~optional~~)		(not 1. Priority)
	\|		\|
	* The admin can create rules, which encounter data drives which LKAAT position with Tiggerconditions (AND OR connected) and a resulting ICD-10 Diagnose		* The admin can create rules, which encounter data drives which LKAAT position with Tiggerconditions (AND OR connected) and a resulting ICD-10 Diagnose

Mionamilosevic at 10:17, 16 September 2025

2025-09-16T10:17:19Z

← Older revision		Revision as of 10:17, 16 September 2025
Line 5:		Line 5:
	!ToDo		!ToDo
	!Definition of Done / Acceptance Criteria		!Definition of Done / Acceptance Criteria
			!Comment
	\|-		\|-
	\| rowspan="6" \|		\| rowspan="6" \|
Line 14:		Line 15:
	* Automatically end consultation timer on end		* Automatically end consultation timer on end
	* The logic of works on the consultation time tracking		* The logic of works on the consultation time tracking
			\|
	\|-		\|-
	\|Extend current version of Kordeus:		\|Extend current version of Kordeus:
Line 29:		Line 31:
	* Timer stops on being more than 30 minutes inactive		* Timer stops on being more than 30 minutes inactive
	* Starting the		* Starting the
			\|<u>Doctors</u> can not edit anything in the form without having started the examination timer TBD depending on the encounter
	\|-		\|-
	\|Create ICD-10 catalog to incorporate in the system		\|Create ICD-10 catalog to incorporate in the system
	\|		\|
	* We have a searchable catalog (fulltext search) in some service, which can be searched realtime		* We have a searchable catalog (fulltext search) in some service, which can be searched realtime
			\|Please send it
			Free text diagnoses?
			Are diagnoses related to services?
	\|-		\|-
	\|ICD-Rule-Editor		\|ICD-Rule-Editor
	\|		\|
	* The admin can create rules, which encounter data drives which ICD-10 diagnose with Tiggerconditions (AND OR connected) and a resulting ICD-10 Diagnose		* The admin can create rules, which encounter data drives which ICD-10 diagnose with Tiggerconditions (AND OR connected) and a resulting ICD-10 Diagnose
			\|Can you stop a diagnose, can you delete it?
			What happens with previous diagnoses, they are related to the patient not enc.
	\|-		\|-
	\|Service Detection Rule Editor		\|Service Detection Rule Editor
Line 42:		Line 50:
	\|		\|
	* The admin can create rules, which encounter data drives which LKAAT position with Tiggerconditions (AND OR connected) and a resulting ICD-10 Diagnose		* The admin can create rules, which encounter data drives which LKAAT position with Tiggerconditions (AND OR connected) and a resulting ICD-10 Diagnose
			\|
			# This can be done if the all rules are added manually, search service add rule for it and save it
			# What happens with the new version of catalogue?
	\|-		\|-
	\|Encounter ICD-10 qualifikation		\|Encounter ICD-10 qualifikation
Line 72:		Line 83:
	* Diagnoses can be added manually by text search and speicificatin of state and location		* Diagnoses can be added manually by text search and speicificatin of state and location
	* Diagnoses are adopted from last encounter (with button-states which are adopted as well)		* Diagnoses are adopted from last encounter (with button-states which are adopted as well)
			\|What happens with old diagnoses?
			Encounter does not have a diagnoses patient does
	\|-		\|-
	\|Mid October		\|Mid October
	\| colspan="3" \|Golive in IROC of ICD-10 qualification and time-tracking		\| colspan="3" \|Golive in IROC of ICD-10 qualification and time-tracking
			\|
	\|-		\|-
	\|30.09.		\|30.09.
Line 81:		Line 95:
	* Download and provide to Goran		* Download and provide to Goran
	* 30.09. is the official publish date of TARDOC LKAAT catalog json, we need to form a catalog		* 30.09. is the official publish date of TARDOC LKAAT catalog json, we need to form a catalog
			\|
	\|-		\|-
	\| rowspan="5" \|		\| rowspan="5" \|
Line 89:		Line 104:
	* Admin sees all service, which can be detected		* Admin sees all service, which can be detected
	* Admin can create edit, rules by this schema: (1) LKAAT positions and (2) materials are created out of a detected service		* Admin can create edit, rules by this schema: (1) LKAAT positions and (2) materials are created out of a detected service
			\|Materials TBD, handed out, consumed? They are currently products and will be billed as WAR as they come from different catalogues.
	\|-		\|-
	\|Billing preparation screen		\|Billing preparation screen
Line 97:		Line 113:
	* LKAAT positions can be added / removed manually		* LKAAT positions can be added / removed manually
	Please note, that all encounters till 31.12.2025 must use the old Billing-Flow, Encounters from 01.01.2026 must use the new billing flow		Please note, that all encounters till 31.12.2025 must use the old Billing-Flow, Encounters from 01.01.2026 must use the new billing flow
			\|TBD
	\|-		\|-
	\|Billing creation flow		\|Billing creation flow
Line 104:		Line 121:
	* Use CaseMaster, Grouper and Mapper to get bill.xml		* Use CaseMaster, Grouper and Mapper to get bill.xml
	* Display the bill in the UI		* Display the bill in the UI
			\|Grouper and mapper jsons do not exists. Ther are functions in TARDOC matcher.
			Understanding of the logic is off.
	\|-		\|-
	\|Bill upload		\|Bill upload
Line 110:		Line 129:
	*Bill can be clears the bill for upload		*Bill can be clears the bill for upload
	*Bill is uploaded and visible in Medidata Transport syystem		*Bill is uploaded and visible in Medidata Transport syystem
			\|First two points have to be reviewed, on sign the date is set.
			This would obsolete draft bills then.
	\|-		\|-
	\|		\|
Line 118:		Line 139:
	* We have a fresh fully running Kordeus integration environment which is not identical with the current envirnment, which we need to other tasks testing. This needs to be independent and only for TARDOC testing		* We have a fresh fully running Kordeus integration environment which is not identical with the current envirnment, which we need to other tasks testing. This needs to be independent and only for TARDOC testing
	* In the Test environment of Medidata (Seiler IPR AG - Webservice 1) we can upload files from Kordeus Integration		* In the Test environment of Medidata (Seiler IPR AG - Webservice 1) we can upload files from Kordeus Integration
			\|Who is responsible for setting up this?
	\|-		\|-
	\|Mid November		\|Mid November
	\| colspan="2" \|Deployment on integration enviroment		\| colspan="2" \|Deployment on integration enviroment
	\|Testing and refinement by Marco		\|Testing and refinement by Marco
			\|
	\|-		\|-
	\|12.12.		\|12.12.
	\| colspan="2" \|Doctors training on integration environment		\| colspan="2" \|Doctors training on integration environment
			\|
	\|		\|
	\|}		\|}

@@ Line 203: / Line 203: @@
 # They choose the status (e.g., "G_CONFIRMED") and confirm the date.
 # The entry is added to the patient's diagnosis list.
 === 3. Reporting and Chronology ===
 The reporting module must prepare data to correctly populate the Word document placeholders, ensuring all information and chronology are preserved.
@@ Line 221: / Line 218: @@
 ** '''Example:''' <code>Cataract, right eye [Free text, pre-2026]</code>
 == See also ==
 * [[Kordeus Core]]

← Older revision		Revision as of 21:21, 6 May 2026
Line 220:		Line 220:
	== See also ==		== See also ==

	* [[Kordeus ~~Core~~]]		* [[Kordeus.CORE]]
	[[Category:Kordeus.CORE Epics]]		[[Category:Kordeus.CORE Epics]]