add roadmap

mherman22 · Sep 23, 2022 · bd24165 · bd24165
1 parent d4be221
commit bd24165
Show file tree

Hide file tree

Showing 3 changed files with 14 additions and 2 deletions.
diff --git a/docs/dev/roadmap.md b/docs/dev/roadmap.md
@@ -0,0 +1,11 @@
+# Roadmap
+
+The maintainers seek feedback from the broader health IT community involved in patient identity management to inform future directions for OpenCR. Please reach out on the OpenCR channel on the iHRIS Slack!
+
+Priority areas for feedback are the following:
+
+* **Simplify configuration for patient matching decision rules:** A longstanding request is to simplify configuration for patient matching decision rules. In 2022 this was addressed by removing the need to write a configuration for ElasticSearch for decision rules. Instead, fields required for indexing because they are in the decision rules are automatically included for indexing.
+
+* **Support for HAPI FHIR Server MDM (Master Data Management) as an optional backend:** This feature would make it possible to use the OpenCR UI with the HAPI MDM backend. OpenCR utilizes ElasticSearch for the task of matching which is scalable and fast. After the initial release of OpenCR, SmileCDR released a patient identity matching mechanism and then overhauled it to allow matching any FHIR resources. There are proprietary features in the SmileCDR product that allow managing 'golden records', meaning to promote fields as authoritative. OpenCR has an open source UI which does not exist in the HAPI or SmileCDR products. 
+
+* **Support Keycloak and similar:** This feature would allow for using authentication and authorization realms managed by Keycloak, a popular open source engine.
diff --git a/mkdocs.yml b/mkdocs.yml
@@ -49,6 +49,7 @@ nav:
     - 'dev/docs.md'
     - 'dev/license.md'
     - 'dev/contributing.md'
+    - 'dev/roadmap.md'
 
   - Sysadmin:
     - 'Introduction': 

diff --git a/packaging/ansible/keys.yaml b/packaging/ansible/keys.yaml
@@ -8,11 +8,11 @@
   vars_prompt:
 
     - name: "user"
-      prompt: "Existing user whom new keys will be added to"
+      prompt: "Existing user on target host whom new keys will be added to"
       private: no
 
     - name: "add"
-      prompt: "Sender who wants their keys added to the existing user's account"
+      prompt: "GitHub username whose keys will be added to the existing user's account"
       private: no