Differences

This shows you the differences between two versions of the page.

--- ivci:maintenance [2024/04/02 15:52] – removed - external edit (Unknown date) 127.0.0.1
+++ ivci:maintenance [2024/04/02 15:52] (current) – ↷ Page name changed from ivci:maintained to ivci:maintenance fkaag
@@ Line 1: / Line 1: @@
+====== Metrics - Maintained ======
+===== Definition =====
+Maintains a formal process to introduce new concepts consistently and in a timely fashion
+===== Rationale =====
+The evolving nature of healthcare requires systems that can adapt and integrate new concepts.
+===== Possible measure =====
+<data metrics>
+Occasional: 0
+Regular, unstructured: 20
+Structured: 50
+Formalized: 100
+</data>
+> NB: I would love to see operational standards here that address different qualities of how the system is maintained. Answering questions such as: How long does it take for new changes to be adopted? Does the organization that adopts new codes have a sustainable process to introduce new concepts? Are the criteria/rules for when new codes are or are not created documented? (I.e. do they have a consistent and dependable philosophy on code creation.) How open is the process to community involvement? How well does it balance the need of involvement of outside stakeholders and for centralized decision making? What processes do they have to disseminating code changes? What mechanisms do they have for community engagement?
+>> FK - I have translated and uploaded the {{nuva_management_policy.pdf |NUVA management policy}}, it can be improved (eg. with quality indicators) but can serve as a starting point.