search

jorritspee / openEHRxNuts

A specification for a distributed openEHR data federation using Nuts v6
0 stars 1 forks source link

Create skeleton for spec #4

Open jorritspee opened 5 months ago

jorritspee commented 5 months ago

Align with Nuts tech team

jorritspee commented 5 months ago

Flow from data user perspective:

  1. Authentication
  2. Localization 2a services 2b SCP/ CareTeam
  3. Authorization
  4. Actual data exchange
rolandgroen commented 5 months ago
  1. Authentication
  2. Localization
    1. Services
    2. Santeon style zorgnetwerk
  3. Authorization
  4. Actual data exchange
joostholslag commented 4 months ago

As discussed I think localisation is use case specific. So I think it should be out of scope for this project. For the POC/hackathon we can just reuse the simplest localisation from another use case on nuts.

jorritspee commented 4 months ago

Unfortunately I don't think there is a simple open source localization function available for any use case at the moment.

joostholslag commented 4 months ago

Unfortunately I don't think there is a simple open source localization function available for any use case at the moment.

how about hardcoding a list of known data sources?