MD Support, sounds reasonable but we need to adapt this to the chaotic world of open source development, where things happen because someone is scratching an itch and not because of a mandate from above. For example if there is an underlying well-documented code base that facilitates standardization, developers are likely to use it.
Feel free to comment more specifically on how this work can be improved towards that end. My feelings will definitely not be hurt and it may be useful if/when someone is willing to do or sponsor such improvements. Thanks.
This is not a suggestion to rework any code - rather a brief conceptual discussion.
Using unified approach for handling demographics would mean accepting either CCR or HL7 as external input standard.
If CCR is adequate, then CMS Portal would translate user input into CCR format and deliver to OpenEMR using Direct message mechanism (without need for Direct messaging). No further development in standard code will be needed.
If HL7 is set as demographics interface standard, CMS Portal project would translate user input into HL7 and deliver to OpenEMR using Direct message mechanism. That project will also add code to process HL7 ADT records within OpenEMR.
By reusing the existing standards based infrastructure OpenEMR can encourage others to explore use of additional interfaces at lower cost without affecting the core package. From staff perspective, they have a single inbox to process with consistent UI - less training for ever changing front office staff.
This could replace or be added to the Demo pages that some time in future will be taken offline.
With Rod’s permission I will try to add some hurdles taken when I tried to implement the CMS- portal, possibly others will do the same. Arnab? Alfonso?