Forum Replies Created
-
Posts
-
This message just to say sorry for not replying before.
Short version: It’s quite busy currently. And actually we are busy because we’re working on a product version of the “OT3” microservices and modules.
Long version: I will get back to you with more info in a week or two when we’re beyond current deadline.
Best,
MichaelI have forwardet your question to a couple of developers that may know. In the meantime it would be great if you would file the issue at https://issuetracker4s.atlassian.net/projects/OT/issues. And please let us know if you yourself have any further findings on this issue.
Regards,
MichaelDevelopment of the XDS Connector was initiated back in 2014 and the developer who initiated the project back then had expertise in working with Spring. Not sure what the status of the JAX WS RI was in 2014? Anyway, you can say that it’s partly for historical reasons , partly it’s due to personal preferences/expertise. Several different developers have since then been involved in minor or major increments of the development of this component and, even if some may have favored a JAX WS RI approach, building on top of the existing has been favored over starting all over.
/Michael
I have not been part of the design discussions for this component, but AFAIK the GreenCDA approach was originally chosen by Henrik Bærbak, who was the main developer of the original PHMR Builder. However, Henrik has not been part of the latest CDA Builder development (and is currently travelling the world), so I have forwarded your question to Bjarne and Lars who are behind the development of the latest CDA Builder.
/Michael
Hi,
Video functionality is currently not a part of the open source version of OpenTele. The video stuff that you do see in the open source version are only stubs and the like for interacting with a closed source video solution that has been used in some of the OpenTele installations used in the Capital Region in Denmark. The closed source video solution was built on top of Vidyo. But this was developed by a third party and 4S are not in possession of further documentation on this.
/Michael
Hi Simon,
What you and your team is working on sounds very interesting.
You are very welcome to contact me directly at software@4s-online.dk if you want to have a Skype or similar to chat about plans.
Kind regards,
Michael Christensen
Coordinator for the software group in 4SKim,
Just had a look at “Guide til Videreudvikling”. This instructions might be a bit outdated. Have you tried building using the instructions found here: http://4s-online.dk/wiki/doku.php?id=opentele2:developer:buildinstructions ?
/Michael
Sorry, but it is not something I have encountered myself. I will check with others here if they have seen anything similar.
Perhaps comparing your setup with the setup of our sandbox http://4s-online.dk/wiki/doku.php?id=opentele2:sandbox could help track down the problem?
/Michael
The documentation on “Snitflader” found at http://4s-online.dk/wiki/lib/exe/fetch.php?media=opentele:opentele_systemsnitflader_2.0.2.pdf states that “rest/patient/login” is an interface for OpenTele 1.x. Really it also works for OpenTele 2.x versions prior to version 2.0.3, but since the latest OpenTele servers are at version 2.12 the “rest/patient/login” interface will not work with that version.
Also see my answer here: https://4s-online.dk/wordpress/forum/topic/opentele-android-client-server-communication-issues/
As it states on http://4s-online.dk/wiki/doku.php?id=opentele2:source this Android app is not compatible with Citizen Servers later than version 2.0.3. If you downloaded the latest version of the citizen server this is now at version 2.12. (This by the way also explains why you would have to change the path for the server)
For clients that are compatible with this latest version of the citizen server please look at the HTML5/JavaScipt client. Please see http://4s-online.dk/wiki/doku.php?id=opentele2:source again for where to find the source code for this. And also see build and setup instructions here: http://4s-online.dk/wiki/doku.php?id=opentele2:developer:introduction.
/Michael
The OpenTele citizen server was last changed 2016-03-14, as you can see here: https://bitbucket.org/4s/opentele2-citizen-server. Perhaps your local configuration somehow changed?
/Michael
I personally have good experience using IntelliJ IDEA. I am using the commercial “Ultimate” edition since this version has support for Grails, so I can’t say how well the free “Community” edition works with OpenTele2 development.
/Michael
Step by step guide to how we created the OpenTele 2 sandbox, can be found at: http://4s-online.dk/wiki/doku.php?id=opentele2:creating_sandbox
Hi Geir,
The information is as you are saying stored in clear text (unencrypted) in the database underlying OpenTele. I have asked around a bit and it has not been an issue as such here in Denmark. As I understand it it is seen as sufficient that data is protected through perimeter security. That is, that all servers are behind firewalls and other mechanisms securing the network from outside intrusions.
I am not aware of DK legislation that specifically what call for encryption or similar. I believe the wording of the legislation is more generic and calls for protection preventing access to the data if you do not have express consent from the patient or you are actively engaged in treating the patient (“behandlerrelation”).
But mind you, I am no expert on the above matters,
Regards,
Michael
