# V6 Documentation wish list **URL:** \ **Category:** Management and Administration\ **Created:** [May 11, 2021, 6:12pm UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616 "2021-05-11T18:12:10Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![gutiersa](https://community.open-emr.org/user_avatar/community.open-emr.org/gutiersa/32/11958_2.png) [@gutiersa](https://community.open-emr.org/u/gutiersa)\ **Post date:** [May 11, 2021, 6:12pm UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/1 "2021-05-11T18:12:10Z")
I would like to keep track of missing documentation. Kindly add to this thread version 6 documentation that needs to be done. If you are a developer, and have added or modified code, and you know there is no entry on the wiki for your changes/code, add a link or entry here as well. I will be happy to create the document in the wiki. Thanks ---
**Author:** ![htuck](https://community.open-emr.org/user_avatar/community.open-emr.org/htuck/32/15185_2.png) [@htuck](https://community.open-emr.org/u/htuck)\ **Post date:** [May 13, 2021, 5:15pm UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/2 "2021-05-13T17:15:02Z")
Hi Sandra- As a starting point here’s this rather sketchy (i.e., not detailed) list of the improvements in the 6.0 release: [https://www.open-emr.org/wiki/index.php/Release\_Features#Version\_6.0.0](https://www.open-emr.org/wiki/index.php/Release_Features#Version_6.0.0) Though I guess one would need to have a v5 install to compare with to find the actual changes… ---
**Author:** ![gutiersa](https://community.open-emr.org/user_avatar/community.open-emr.org/gutiersa/32/11958_2.png) [@gutiersa](https://community.open-emr.org/u/gutiersa)\ **Post date:** [May 18, 2021, 2:16pm UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/3 "2021-05-18T14:16:46Z")
@htuck @sjpadgett@stephenwaite @robert.down @brady.miller I am interested in updating the Layout Based Forms page of the wiki: [https://www.open-emr.org/wiki/index.php/LBV\_Forms](https://www.open-emr.org/wiki/index.php/LBV_Forms) I would like to update it specifically as to how these forms function in version 6 I plan on starting a new page for v6 These are my questions: 1. Has this already been done, perhaps I have not researched this topic well enough! 2. The first paragraph refers to “these tables” is it just these two tables? list\_options and layout\_options tables 3. For v6, is it still only those two tables? 4. I would like to add to this page practical examples. One which includes nation notes within a form. I am thinking of writing up SOAP notes sample. I believe that is pretty widely used. Finally, if you know someone who knows a little or a lot about this particular topic, kindly tag them in this thread. Thanks for your consideration of this topic. ---
**Author:** ![gutiersa](https://community.open-emr.org/user_avatar/community.open-emr.org/gutiersa/32/11958_2.png) [@gutiersa](https://community.open-emr.org/u/gutiersa)\ **Post date:** [May 18, 2021, 3:09pm UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/4 "2021-05-18T15:09:53Z")
Thanks so much for this link: I would like to start to get organized. I am listing the improvements here. My goal is that if anyone knows of a thread, or a wiki page, which elaborates on the following improvements, he/she will list it in this thread such that I can update the wiki. Anyone may refer to the improvement by the number only and add the links. 1. Numerous User Interface Improvements 2. Speed and Performance Optimizations 3. New Support for FHIR (Fast Healthcare Interoperability Resources) 4. New Support for SMART on FHIR 5. New Support for OAuth2 6. New Support for OIDC (OpenID Connect) 7. New Support For EasiPro (Patient Reported Outcomes) 8. New Support for Kubernetes 9. New Docker Support for Raspberry Pi 10. New Support for Argon Password Hashing 11. New Database Support for utf8mb4 Encoding 12. Patient Portal Improvements 13. REST API Improvements 14. Installer Improvements 15. Patient Dashboard Improvements 16. LDAP Improvements Including SSL Support 17. Billing Improvements 18. Payment and Batch Payment Improvements 19. Fee Sheet Improvements 20. Patient Flow Board Improvements 21. Calendar Improvements 22. Encounter Improvements 23. Messaging improvements 24. Patient History Improvements 25. Immunization Module Improvements 26. Dicom Viewer Improvements 27. Procedure Order Form Improvements 28. Referral Form Improvements 29. Prior Auth Form Improvements 30. Newcrop Rx Improvements 31. CDR (Clinical Decision Rules) Engine Improvements 32. CCDA Improvements 33. MedEx Improvements 34. Multisite Module Improvement 35. CouchDB Improvements Including SSL Support 36. Access Control Improvements 37. Cookie and Session Improvements 38. Logging Improvements 39. Docker Improvements 40. ICD10 Code Set Updated 41. Supported in 34 Languages 42. Numerous Bug Fixes 43. Numerous Security Fixes and Security Improvements 44. Numerous Fixes to Ensure Compatible with Most Recent Versions of PHP, MariaDB and MySQL 45. Modernization of Codebase 46. Automated Testing 47. Docker Development Environment Improvements For example: 26. [Webservices, DICOM and DICOMSR support](https://community.open-emr.org/t/webservices-dicom-and-dicomsr-support/7411/20) 26. [https://www.open-emr.org/wiki/index.php/DICOM\_Uploader,\_Storage\_Engine\_and\_Viewer](https://www.open-emr.org/wiki/index.php/DICOM_Uploader,_Storage_Engine_and_Viewer) ---
**Author:** ![htuck](https://community.open-emr.org/user_avatar/community.open-emr.org/htuck/32/15185_2.png) [@htuck](https://community.open-emr.org/u/htuck)\ **Post date:** [May 18, 2021, 4:47pm UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/5 "2021-05-18T16:47:15Z")
Hi @gutiersa et al- I’m thinking the most difficult part of building the list of changes to document would be to find out precisely what the v6 improvements are. I mean, ‘Access Control Improvements’ allows for a lot of possibly documentable functionality. And ‘Patient Portal Improvements’- the Patient Portal is a deep topic. Trying to find where the changes are detailed, the best I can come up with is the closed pull requests in github: > **[openemr/openemr](https://github.com/openemr/openemr/pulls?q=is:pr%2Bis:closed)** > > OpenEMR is the most popular open source electronic health records and medical practice management solution. OpenEMR's goal is a superior alternative to its proprietary counterparts. - openemr/o... It’s a (‘the’?) list of specifically what changes have been completed, so it’s possible to find it in the EMR. But then it needs to be determined if it’s a user- relevant change, and also if it’s in the current release. So doing things this way is a lotta lotta work. Maybe I’m over- thinking this. Does anybody have ideas on a better approach? Best- Harley ---
**Author:** ![gutiersa](https://community.open-emr.org/user_avatar/community.open-emr.org/gutiersa/32/11958_2.png) [@gutiersa](https://community.open-emr.org/u/gutiersa)\ **Post date:** [May 18, 2021, 7:36pm UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/6 "2021-05-18T19:36:55Z")
> [@htuck](#): > > It’s a (‘the’?) list of specifically what changes have been completed, so it’s possible to find it in the EMR. But then it needs to be determined if it’s a user- relevant change, and also if it’s in the current release. So doing things this way is a lotta lotta work. > > Maybe I’m over-thinking this. Does anybody have ideas on a better approach? You are not overthinking it. It is a lot, but it needs to get done. OpenEMR has a lot of documentation, however, it is in many different places, and some of it is outdated. I believe some people come, try to get information, but give up and move on to other projects. I am willing to update the wiki (and other areas) as I am setting up my system, and as I learn to use the features I am working on. It works out for everyone, me because I will eventually forget the details and there will be a place for me to look it up, and for newcomers. Regarding user relevant changes, I agree. But documentation for developers also needs to be done. We could consider labeling the pages this way for example: DICOM Uploader, Storage Engine and Viewer v6 DICOM Uploader, Storage Engine and Viewer v6-dev Meaning one page is geared to users, and the second page would be geared to developers. In other words, the wiki would have two pages for DICOM Uploader, Storage Engine and Viewer ---
**Author:** ![htuck](https://community.open-emr.org/user_avatar/community.open-emr.org/htuck/32/15185_2.png) [@htuck](https://community.open-emr.org/u/htuck)\ **Post date:** [May 19, 2021, 7:42pm UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/7 "2021-05-19T19:42:50Z")
That seems a reasonable method to categorize the documents but must be careful to not add yet another layer of organization that has to be navigated by the clueless info- seeker… ---
**Author:** ![gutiersa](https://community.open-emr.org/user_avatar/community.open-emr.org/gutiersa/32/11958_2.png) [@gutiersa](https://community.open-emr.org/u/gutiersa)\ **Post date:** [May 19, 2021, 7:53pm UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/8 "2021-05-19T19:53:45Z")
No, it shouldn’t if these conventions are clearly documented. Also, that is what the Table of documents and index are for. Don’t worry, I will not do anything on my own. These are just ideas! ---
**Author:** ![PeteBoyd](https://community.open-emr.org/user_avatar/community.open-emr.org/peteboyd/32/14391_2.png) [@PeteBoyd](https://community.open-emr.org/u/PeteBoyd)\ **Post date:** [May 25, 2021, 9:12am UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/9 "2021-05-25T09:12:51Z")
> [@gutiersa](#): > > - The first paragraph refers to “these tables” is it just these two tables? list\_options and layout\_options tables > - For v6, is it still only those two tables? Scant though the changelog for new OpenEMR versions is, I can’t see such a radical change having been made in version 6 without alerting people to it. Version 6 isn’t a huge upgrade. In OpenEMR 5, these are the only tables involved, other than the lbf\_\* tables in which form data is saved. - layout\_options - this is your layout - list\_options - the contents of any lists - lbf\_data - data entered into the form about patients ---
**Author:** ![adunsulag](https://community.open-emr.org/user_avatar/community.open-emr.org/adunsulag/32/12606_2.png) [@adunsulag](https://community.open-emr.org/u/adunsulag)\ **Post date:** [May 25, 2021, 11:20am UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/10 "2021-05-25T11:20:20Z")
@gutiersa The SMART on FHIR, and FHIR api use documentation is being spearheaded by @brady.miller. Perhaps the two of you can collaborate here. We have to have a developer friendly documentation for our APIs and the ability to add 3rd party applications which is the SMART on FHIR specification. This has to be done in order for us to pass certification for the latest meaningful use certification (ONC 2015 / 2020 Cares Act certification). I’m the one implementing the FHIR and SMART on FHIR implementation so I’m happy to answer any questions on this. ---
**Author:** ![gutiersa](https://community.open-emr.org/user_avatar/community.open-emr.org/gutiersa/32/11958_2.png) [@gutiersa](https://community.open-emr.org/u/gutiersa)\ **Post date:** [May 25, 2021, 7:30pm UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/11 "2021-05-25T19:30:56Z")
@PeteBoyd Yes, I do agree that there is likely not a lot of change in going from V5 to V6. However, say, someone wanted to change from v4 to V6, then it might be easier for them. Rather than having to chase the forum threads. @adunsulag@brady.miller Great, in that case, I would love to be added to however much documentation is available. The way my brain works, I figure out how to apply the information before I can understand it. If I can implement it in my system, then I can help with documentation. Thanks ---
**Author:** ![adunsulag](https://community.open-emr.org/user_avatar/community.open-emr.org/adunsulag/32/12606_2.png) [@adunsulag](https://community.open-emr.org/u/adunsulag)\ **Post date:** [May 27, 2021, 6:09pm UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/12 "2021-05-27T18:09:53Z")
The current API documentat is found in the codebase for the [API here](https://github.com/openemr/openemr/blob/master/API_README.md) and for [FHIR here](https://github.com/openemr/openemr/blob/master/FHIR_README.md). SMART on FHIR app installation is linked to in the documentation but it really should be integrated directly into the FHIR docs. It can be found [here](https://github.com/openemr/openemr/issues/4148). ---
**Author:** ![gutiersa](https://community.open-emr.org/user_avatar/community.open-emr.org/gutiersa/32/11958_2.png) [@gutiersa](https://community.open-emr.org/u/gutiersa)\ **Post date:** [May 28, 2021, 5:04pm UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/13 "2021-05-28T17:04:09Z")
Thank you I would really love to help more. What would I have to do to help integrate it? How do I test this test script? I mean, what do I enter into the address bar? [Https://domain.com/tests/api/InternalApiTest.php/](Https://domain.com/tests/api/InternalApiTest.php/) that did not work for me! ☹ ---
**Author:** ![benmarte](https://community.open-emr.org/user_avatar/community.open-emr.org/benmarte/32/15117_2.png) [@benmarte](https://community.open-emr.org/u/benmarte)\ **Post date:** [May 29, 2021, 3:27pm UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/14 "2021-05-29T15:27:13Z")
Are there any plans to use something like swagger for API docs? That would be awesome if possible. ---
**Author:** ![htuck](https://community.open-emr.org/user_avatar/community.open-emr.org/htuck/32/15185_2.png) [@htuck](https://community.open-emr.org/u/htuck)\ **Post date:** [June 18, 2021, 5:17pm UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/15 "2021-06-18T17:17:49Z")
Hi All- New doc posted in the v6 user guide ([https://www.open-emr.org/wiki/index.php/OpenEMR\_6.0.0\_Users\_Guide](https://www.open-emr.org/wiki/index.php/OpenEMR_6.0.0_Users_Guide)) Check it out: [https://www.open-emr.org/wiki/index.php/HOWTO\_Activate\_a\_Patient’s\_portal\_access\_-\_v6.0](https://www.open-emr.org/wiki/index.php/HOWTO_Activate_a_Patient%27s_portal_access_-_v6.0) It’s not explicitly mentioned on the wish list; mebbe add it so it can be crossed offf? 🙂 -Harley ---
**Author:** ![htuck](https://community.open-emr.org/user_avatar/community.open-emr.org/htuck/32/15185_2.png) [@htuck](https://community.open-emr.org/u/htuck)\ **Post date:** [June 18, 2021, 5:26pm UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/16 "2021-06-18T17:26:10Z")
Hi @gutiersa - Seems to me like the best way to help is to simply choose a topic and write a tutorial on it. If it has been documented for earlier versions refer to those pages for background, but basically, run through it on your v6 install till you know what all the screen objects do, then write it up. I am happy to consult on how I compose my wiki docs, the style guides I’ve used etc etc, if anybody would like to see them. But again, as some famous outfit’s motto says, “JUST DO IT”. Best- Harley ---
**Author:** ![sjpadgett](https://community.open-emr.org/user_avatar/community.open-emr.org/sjpadgett/32/21623_2.png) [@sjpadgett](https://community.open-emr.org/u/sjpadgett)\ **Post date:** [June 18, 2021, 6:37pm UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/17 "2021-06-18T18:37:32Z")
Thanks Harley for doing this. However, portal has changed since v6(0) and now supports categories. For example: Category setup in Lists(Repository is a place to put templates not used or being worked): ![image](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/2/2db531adf5828fbf5a7812dc338be89f8e2b7bd5.png) In Dashboard(upload, move or edit templates to categories): ![image](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/3/3085968c3a285f00f3136d89af5d81baae30d97a.png) And the Portal:(Templates are duplicated for this example) ![image](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/d/db46f5f2dbcf936b66c5a7d39ed356b2e3733890.png) Also note that now Portal is a SPA(Single Page App) and now includes a HELP template to individualize for each practice. Please also note that the portal now requires that any user that needs to be included in portal must have portal flag set in Users: ![image](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/7/7e343dcdacf8a37bacc4fd45df2b925af9c5780e.png) All these changes also apply to the same demographics patient document feature. ![image](https://discourse-uploads-openemr.s3.dualstack.us-east-1.amazonaws.com/original/2X/7/726e5504e5f4b27964c6751e37f989bd3b98a3a5.png) ---
**Author:** ![VWfeature](https://community.open-emr.org/user_avatar/community.open-emr.org/vwfeature/32/15838_2.png) [@VWfeature](https://community.open-emr.org/u/VWfeature)\ **Post date:** [June 19, 2021, 6:32am UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/18 "2021-06-19T06:32:54Z")
> [@sjpadgett](#): > > Please also note that the portal now requires that any user that needs to be included in portal must have portal flag set in Users: DOes this mean patients can no longer self register using the portal? **Patient self-registration is an incredibly useful tool.** I know there needs to be some mechanism preventing abusive or malicious signups, but there are tech solutions for that too. IIRC, limiting signups to valid emails, and throttling them for the same IP address. Real techs will have better ideas. Can defaulting this to ‘allowed’ be done? ---
**Author:** ![sjpadgett](https://community.open-emr.org/user_avatar/community.open-emr.org/sjpadgett/32/21623_2.png) [@sjpadgett](https://community.open-emr.org/u/sjpadgett)\ **Post date:** [June 19, 2021, 2:46pm UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/19 "2021-06-19T14:46:53Z")
> [@VWfeature](#): > > DOes this mean patients can no longer self register using the portal? I’m talking about what OpenEMR users/providers/doctors/administrators are able to be seen in portal for such things as receiving secure messages. Registration is still available for all. > [@VWfeature](#): > > Real techs will have better ideas. And here I though I was a real tech!🙂 ---
**Author:** ![VWfeature](https://community.open-emr.org/user_avatar/community.open-emr.org/vwfeature/32/15838_2.png) [@VWfeature](https://community.open-emr.org/u/VWfeature)\ **Post date:** [June 20, 2021, 5:01am UTC](https://community.open-emr.org/t/v6-documentation-wish-list/16616/20 "2021-06-20T05:01:29Z")
YOU are a real tech! I was was just flapping gums with ideas for securing the portal!! [Next page](https://community.open-emr.org/t/v6-documentation-wish-list/16616.md?page=2)