Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DocumentReference and KMEHR #76

Open
fdetaver opened this issue Mar 7, 2024 · 2 comments
Open

DocumentReference and KMEHR #76

fdetaver opened this issue Mar 7, 2024 · 2 comments

Comments

@fdetaver
Copy link

fdetaver commented Mar 7, 2024

I have several issues with the current BeDocumentReference profile as we believe this resource will be used for KMEHR documents at some point :

  1. How should we map the different KMEHR codesystems into BeDocumentReference ? Shouldn't we provide a mapping or guidance ? Should we allow KMEHR code systems in the relevant fields ?
  2. The 2 mandatory codes (CD-TRANSACTION & CD-HCPARTY(dept)) in KMEHR are used to determine access (access matrix). What about the cardinality of those concept in the resource ? What to do for access if we don't know the document type in relation to the access matrix
  3. Isn't there a need to deal with the encryption layer related to KMEHR documents exchange ? The attachment in binary could be encrypted (use of provenance ?)
@fdetaver
Copy link
Author

Hello,

I apologize for not being present yesterday (17/04). In my defense, I had a double booking with another eHealth meeting ...
Marcelo has warned me that an input was needed or the issue will be closed without answer.

This issue is still important to me and other systems. As such, I would rather not close it completly.
However, we agreed that this issue can be put "on pause" or transfer to another queue or whatever and the profile discuss here would be restricted to the use of a specific project.

We believe that, if this profile is put out there for a more general usage, these questions are still relevant for the compatibility with the current KMEHR system.

Best regards,
Félix

@fdetaver
Copy link
Author

fdetaver commented May 15, 2024

This is an example of a KMEHR transaction (dieticianreport) in a getTransactionList :

<transaction> <cd S="CD-TRANSACTION" SV="1.0">contactreport</cd> <cd S="LOCAL" SV="1.0" SL="PatientAccess" DN="" L="fr">yes</cd> <cd S="LOCAL" SV="1.0" SL="PatientAccessDate" DN="" L="fr">11/04/2024 16:06:22</cd> <date>2024-04-11</date> <time>16:06:22.0000000+02:00</time> <author> <hcparty> <id S="ID-HCPARTY" SV="1.0" SL="">HUB ID</id> <cd S="CD-HCPARTY" SV="1.1" SL="" DN="" L="fr">hub</cd> <name>RSB</name> </hcparty> <hcparty> <cd S="CD-HCPARTY" SV="1.0" SL="">deptdietetics</cd> <name/> </hcparty> <hcparty> <id S="ID-HCPARTY" SV="1.0">HCP INAMI</id> <cd S="CD-HCPARTY" SV="1.0" SL="" DN="" L="">persdietician</cd> </hcparty> </author> <iscomplete>true</iscomplete> <isvalidated>true</isvalidated> <recorddatetime>2024-04-11T16:06:22.537</recorddatetime> </transaction>

I removed some of the fields that are irrelevant or for identification

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant