FAQ

Note: this FAQ applies to Linux servers. Other systems might behave differently.

Q: How do I begin?

A:

• Download the server binaries and unzip them in an appropriate directory.
• create a directory $HOME/elexis-server, copy the connection settings and the shiro access definitions to that directory and edit them according to your needs.
• cd <server-directory>, then ./linux-start
• telnet localhost 7234 (not localhost:7234 as the linux-start output says)
• es_p2 features install info.elexis.server.fhir.rest.core.feature.feature.group
• Launch a browser and navigate to http://localhost:8380/fhir/Patient?name=&lt;some patient name part>

Q: The server won't start

A:

• consult $HOME/elexis-server/logs
• make sure, your elexis database has a locale-config (select wert from config where param='locale'; ). If this query returns an empty set, find out your machine's locale by typing locale in the terminal. Then insert that in the 'config' table, as in: insert into config (param,wert) values ("locale","de_CH");
• make sure, your table names are lowercase and the mysql server is set to ignore case. Instructions here
• Reinstall the fhir core bundle: es_p2 features uninstall info.elexis.server.fhir.rest.core.feature.feature.group, then es_p2 features install info.elexis.server.fhir.rest.core.feature.feature.groupin the elexis-server telnet console.

Q: What Types of FHIR Resources are supported?

A:

• Patient: (only /Patient?name=xxx is supported, name and firstname are matched; returns a list of matching Patients)

• Encounter: (/Encounter?patient=id is supported; returns a list of encounters for the given patient.)

• Condition

• Organization

• ProcedureRequest

• Coverage

• CodeSystem

• Practitioner

• StructureDefinition

• Observation

• MedicationOrder

• OperationDefinition

• Claim

Q: Why do I get an "No Access-Control-Allow-Origin Header" error?

A: This is a security feature of all modern browsers: A JavaScript App can not load resources from other sites than its own origin (Same Origin Policy). Unfortunately, even a different port on the same server counts as different origin, so our app residing at localhost:9000 can't load data from the elexis-server residing at localhost:8380.

There are three possibilities to get around this:

1. use JSONP instead of XMLHttpRequest in your app. Thats a bit cumbersome, though.

2. Use the Chrome Browser with the "Allow-Control-Allow-Origin" plugin. (Of course, this is only a development-time-solution, since you can't rely on your customers, using all Chrome and loading all this extension.)

3. Enable CORS (Cross origin resource sharing) at the server side. This is a technique to allow cross origin requests while maintaining security. That's the best solution, but in involves some deep-diving into the server code.

Q: How do I make sure that the server listens only to my VPN address?

A: ?

Q: How do I configure https:// - connections?

Q: Is there any authentication/authorisation?