Difference between revisions of "Minutes - Patient Dossier WG 2023-12-08"
From Health Level 7 Belgium Wiki
KarlienErauw (talk | contribs) |
KarlienErauw (talk | contribs) |
||
| Line 9: | Line 9: | ||
=== Excused/absent === | === Excused/absent === | ||
| − | |||
* Jean-Michel Polfliet, eHealth platform/HL7 Belgium | * Jean-Michel Polfliet, eHealth platform/HL7 Belgium | ||
* Tim Bogaert, Byteflies | * Tim Bogaert, Byteflies | ||
| Line 18: | Line 17: | ||
=== Minutes === | === Minutes === | ||
| − | * MoveUp/Bruno did some review of the logical model & the FHIR IG | + | * MoveUp/Bruno did some review of the [https://hl7-be.github.io/patient-monitoring/StructureDefinition-PatientMonitoring.html logical model] & the [https://hl7-be.github.io/patient-monitoring/StructureDefinition-PatientMonitoringObservation.html FHIR IG] |
::* by checking some examples on bariatrics and orthopedics | ::* by checking some examples on bariatrics and orthopedics | ||
| − | ::::* lots of parameters are being captured, for bariatrics some texts | + | ::::* lots of parameters are being captured, for bariatrics also some some values as texts |
| − | ::::* how do we fit a report in different | + | ::::* how do we fit a report in different timeseries, how do we add these, how do we group these series in the data structure? |
| − | ::::::* initial scop of the IG is one event, so | + | ::::::* initial scop of the IG is one event, so timeseries don't fit in here |
| − | ::::::* is the duration of the follow-up indicated, f.e. for Fibricheck 7 or 15 or 30 days, this could be captured in one single report | + | ::::::* is the duration of the follow-up indicated, f.e. for Fibricheck 7 or 15 or 30 days, as this could be captured in one single report |
| − | ::::::* is also applicable for orthopedics | + | ::::::* is also applicable for orthopedics but more specific, intense after the surgery where more data are captured |
::::* reports can already be made available through the hubs, but not in FHIR | ::::* reports can already be made available through the hubs, but not in FHIR | ||
::::* the FHIR IG can contain an URL pointing to the dashboard and/or pdf | ::::* the FHIR IG can contain an URL pointing to the dashboard and/or pdf | ||
| − | ::* | + | ::::::* are these linked to diagnostic report or to obversation? |
| + | ::::::* we need to agree on where the line is b/w observation and diagnostic report | ||
| + | :::::* we have to investigate where we want to include the PDF and URL (to dashboard) | ||
| + | :::::* F.e. a measurement is done during 60 sec for which there is an outcome and a PDF report is generated | ||
| + | :::::* FHIR R5 has value attachment, but it is not available in R4 yet | ||
| − | ::* | + | ::* goal is to profile observations: capture of a parameter, some qualitative, some quantative |
| − | + | ::::* we need an exhaustive list of quantative observations, we will start working on this [https://docs.google.com/spreadsheets/d/1sk4dY9VfKaVQuIhrmO3l-pFRDIBCiD4g9SbIGNBFUb0/edit#gid=0 here] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
* Work on some examples has already been done, see [https://build.fhir.org/ig/hl7-be/patient-monitoring/artifacts.html#example-example-instances section 3.0.5 here] | * Work on some examples has already been done, see [https://build.fhir.org/ig/hl7-be/patient-monitoring/artifacts.html#example-example-instances section 3.0.5 here] | ||
::* some more examples, from other vendors, are necessary to check off the profile | ::* some more examples, from other vendors, are necessary to check off the profile | ||
| − | |||
| − | |||
| − | |||
=== Action items === | === Action items === | ||
| − | * | + | * Work on listing of observations |
| − | * | + | * investigate where to put pdf and URL |
| + | * provide examples | ||
=== Next meeting === | === Next meeting === | ||
| − | Next WG meeting will take place online on | + | Next WG meeting will take place online on Tuesday 19 December 10AM CET |
Latest revision as of 10:49, 8 December 2023
Attendees
- Bart Decuypere, eHealth platform/HL7 Belgium
- Benny Tops, Remecare
- Bruno Neckebroek, MoveUP
- Christopher Hex, Fibricheck
- José Costa Teixeira, imec/HL7 Belgium
- Karlien Erauw, Agoria/HL7 Belgium
- Peter Van Vooren, Remecare
Excused/absent
- Jean-Michel Polfliet, eHealth platform/HL7 Belgium
- Tim Bogaert, Byteflies
- Ward Servaes, MoveUP
Agenda
- Review of logical model & FHIR IG
Minutes
- MoveUp/Bruno did some review of the logical model & the FHIR IG
- by checking some examples on bariatrics and orthopedics
- lots of parameters are being captured, for bariatrics also some some values as texts
- how do we fit a report in different timeseries, how do we add these, how do we group these series in the data structure?
- initial scop of the IG is one event, so timeseries don't fit in here
- is the duration of the follow-up indicated, f.e. for Fibricheck 7 or 15 or 30 days, as this could be captured in one single report
- is also applicable for orthopedics but more specific, intense after the surgery where more data are captured
- reports can already be made available through the hubs, but not in FHIR
- the FHIR IG can contain an URL pointing to the dashboard and/or pdf
- are these linked to diagnostic report or to obversation?
- we need to agree on where the line is b/w observation and diagnostic report
- we have to investigate where we want to include the PDF and URL (to dashboard)
- F.e. a measurement is done during 60 sec for which there is an outcome and a PDF report is generated
- FHIR R5 has value attachment, but it is not available in R4 yet
- goal is to profile observations: capture of a parameter, some qualitative, some quantative
- we need an exhaustive list of quantative observations, we will start working on this here
- Work on some examples has already been done, see section 3.0.5 here
- some more examples, from other vendors, are necessary to check off the profile
Action items
- Work on listing of observations
- investigate where to put pdf and URL
- provide examples
Next meeting
Next WG meeting will take place online on Tuesday 19 December 10AM CET
