In 2008, ADL 1.4 was adopted as the basis of ISO 13606-2.
A few years ago, the renewal process started for this standard, and as
part of that, openEHR Foundation was asked to allow the ADL2 version of
the Archetype Formalism (specifically, the AOM2 specification
<ht
Don't miss a two-day workshop which will provide hands-on development sessions
on the Better Platform™.
Dear member of openEHR tech community,
I'm kindly inviting you to our two-day workshop which will provide hands-on
development sessions on the Better Platform™. So please, mark your
learn the openEHR template format
specification.
The first thing I did was looking at the specification page
(https://specifications.openehr.org/), to see what template formats
exist. On this page OPT1.4, OPT2 and AOM2 are listed as description
laguages that somehow are related to templates
llo,
I am currently trying to learn the openEHR template format specification.
The first thing I did was looking at the specification page
(https://specifications.openehr.org/), to see what template formats
exist. On this page OPT1.4, OPT2 and AOM2 are listed as description
laguages that s
Hello,
I am currently trying to learn the openEHR template format specification.
The first thing I did was looking at the specification page
(https://specifications.openehr.org/), to see what template formats
exist. On this page OPT1.4, OPT2 and AOM2 are listed as description
laguages
pretty much everything on this page
<https://www.openehr.org/openehr_in_use/deployed_solutions/> was a
(successful) procurement
- thomas
On 22/08/2019 13:34, Erik Sundvall wrote:
Hi!
I have started a wikipage about "Procurement of openEHR-related systems":
https://opene
Dear Erik,
we had a few procurements in Slovenia focusing on OpenEHR systems and also
a few other procurements that included OpenEHR archetypes and templates as
part of requirements or to be delivered as part of the results. However,
all procurements have been specified in the Slovene language so
Hi!
I have started a wikipage about "Procurement of openEHR-related systems":
https://openehr.atlassian.net/wiki/spaces/resources/pages/416514052/Procurement+of+openEHR-related+systems
(As a preparation for an upcoming, not yet started procurement)
Please help me list things there, i
t
advocate for hgaving a separate space.
Best!
Luis
El mié., 7 ago. 2019 a las 9:27, Bakke, Silje Ljosland via
openEHR-technical () escribió:
> I think we may need a more thorough discussion about how to best use the
> wiki. How do we maximise information findability, how do we ena
with “Specifications” and
“Clinical”. There also seems to me there’s an overlap in use between
“Education”, “Community” and “Resources” that needs to be delineated.
I also noticed that we have the Calendar app enabled. Does anyone use it? If
not, could we disable it?
Kind regards, Silje
From: openEHR
FAQs that people may well access.
these are just my views, and others may have better ideas...!
- thomas
On 07/08/2019 08:26, Bakke, Silje Ljosland via openEHR-technical wrote:
I think we may need a more thorough discussion about how to best use
the wiki. How do we maximise information
the existing spaces
become crowded? How do we decide what goes in which space?
For now:
* I’ve reactivated the Education space, since I saw it was used for the
Spanish openEHR Day. (Is this really education though, and not community?)
* The Ontologies space has a single page with a few
On 06/08/2019 13:43, Bakke, Silje Ljosland via openEHR-technical wrote:
Picking this up again half a year later…
I’ve archived the following spaces, since there seemed to be a
consensus that they weren’t used. This is easily reversible:
* Healthcare
* Demonstration Space
* Education
at and/or move the stuff in the following
spaces?
* CIMI
* Terminology
For the rest of you, does anyone care if the following spaces are archived?
* Projects (https://openehr.atlassian.net/wiki/spaces/projects)
* Zz openEHR Community (https://openehr.atlassian.net/wiki/spaces
Hi!
Those of you interested in openEHR modeling for physical activity data etc.
from personal health platforms (like Google Fitness, Apple Health, Samsung
Health, Withings, Garmin, Polar, Strava, MyFitnessPal etc.) may want to take a
look at some of the info, links, mindmaps etc at
https
BTW, the querying we use is not AQL, is what we call path-based queries,
that is explained here
https://docs.google.com/document/d/1pGJXIWHCgjyiofLmNHRTG7UFuB-tVWzm625X5rkiHiw/edit?usp=sharing
On Tue, Mar 26, 2019 at 9:22 AM Pablo Pazos
wrote:
> If the idea is to get openEHR data ba
If the idea is to get openEHR data based on the SNOMED CT structure, we
have been doing that for a while
https://www.youtube.com/watch?v=JIolq3b_Gkw=5=PL-4c1WHznyulrf8wPhaOq7T0E2QWQMCHH
On Mon, Mar 25, 2019 at 1:03 AM Erik Sundvall wrote:
> Hi all openEHR+Snomed CT hackers!
>
&
Hi all openEHR+Snomed CT hackers!
Doing the inference described below using a reasoner and openEHR with AQL+api
calls as a bridge to EHR content would be pedagogical.
Who in the openEHR community will get a demo video out first?
Good luck with this little challenge!
Best regards,
Erik
Please let me know if you find any issues when using it:
https://github.com/ppazos/openEHR-OPT/issues
On Fri, Feb 22, 2019 at 8:28 AM Georg Fette
wrote:
> Hello,
> Thank you all. The .xsds are already very useful. And the Toolkit also
> looks beneficial for what I want to do.
&g
://www.ehrscape.com/api-explorer.html
Both sides together should give you enough tooling about how OpenEhr is
supposed to work in the technical details.
Bert
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http
-85516
Am Hubland Fax.: +49-(0)931-31-86732
97074 Würzburg mail: georg.fe...@uni-wuerzburg.de
-
___
openEHR-technical mailing list
openEHR-technical
to experiment with the API and thus also see the JSON
datasets.
Best regard
Bert
Sent from my Xperia™ by Sony smartphone
Bert Verhees wrote
>The question asked by George Fette is that he wants to see an example of an
>OpenEhr dataset in XML or JSON containing demogr
The question asked by George Fette is that he wants to see an example of an
OpenEhr dataset in XML or JSON containing demographics and commonly used
archetypes.
Best regards
Bert
Sent from my Xperia™ by Sony smartphone
Pablo Pazos wrote
>Adding to Thomas comments,
>
>1.
Adding to Thomas comments,
1. Yes, XML XSDs should be the source of truth here
2. You can use the openEHR Toolkit to generate instances in XML from an OPT
http://server001.cloudehrserver.com/cot/
That helps testing and verifying formats.
On Thu, Feb 21, 2019 at 5:45 AM Thomas Beale
wrote
You may want to look at the XSDs here on Github
<https://github.com/openEHR/specifications-ITS-XML/tree/master/components>
and JSON schemas (emerging) here
<https://github.com/openEHR/specifications-ITS-JSON>.
On 21/02/2019 08:14, Georg Fette wrote:
Hello,
Is there a d
Hello,
Is there a documentation of the syntax how openEHR EHR data is
serialized ? I would be interested in a concrete example of an
EHR-API-GET-call and the returned String in XML or JSON which can be
used as transfer medium between applications or as a storage format. It
would be beneficial
Dear colleagues,
We are pleased to update the openEHR community on the outcome of our
EtherCIS camp held over 3 days in London in December 2018.
A group of 12 individuals, representing 8 nationalities, from academia,
commercial and non-profit sectors came together to explore, discuss and
plan
There are now some useful links to get to any openEHR terminology group
on the specifications home page
<https://specifications.openehr.org>(scroll down) in one click.
- thomas
___
openEHR-technical mailing list
openEHR-technical@lists.opene
and planned actions are
performed, but now we would like to have (some) more feedback from you, the
community. It will help us proceed to final steps towards releasing these new
schemas.
If you did not follow or notice changes lately in the openEHR-ITS, here is a
little explanation
a home page and align
with the rest of the foundation’s organisation.
As other areas are identified as required, then we need to have a clearly
responsible person or team who is the coordinator.
Cheers
Heather
From: openEHR-technical On Behalf
Of Ian McNicoll
Sent: Wednesday, 19 December 2018
here, though...
- thomas
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
FYI See example JSON based //openEHR <--> FHIR mapping template //for
Allergy content attached and more here
https://github.com/RippleOSI/Ripple-FHIR/tree/master/FHIR-Ripple_Mapping/examples/templates
This approach has also been designed with npm in mind for easy distribution
and usage,
Go for it. I trust you. A spruce up is a good start.
Ian
Dr Ian McNicoll
mobile +44 (0)775 209 7859
office +44 (0)1536 414994
skype: ianmcnicoll
email: i...@freshehr.com
twitter: @ianmcnicoll
Co-Chair, openEHR Foundation ian.mcnic...@openehr.org
Director, freshEHR Clinical Informatics Ltd
Hi everyone,
Sorry for the crossposting, but I thought this would concern everyone.
I believe the openEHR wiki is an important documentation tool that has probably
been a bit neglected(?). The default Confluence theme isn't super pretty, and
the site is difficult to navigate, in my opinion
ran...@oceanhealthsystems.com> wrote:
> Although I will add, and I think someone has already suggested this, at
> least we only have to do this mapping once for each FHIR resource. So as a
> openEHR/FHIR community we should aim for a set of templates, as Thomas
> indicated, a set of FHIR extensi
com>) escribió:
> Although I will add, and I think someone has already suggested this, at
> least we only have to do this mapping once for each FHIR resource. So as a
> openEHR/FHIR community we should aim for a set of templates, as Thomas
> indicated, a set of FHIR extensi
Although I will add, and I think someone has already suggested this, at least
we only have to do this mapping once for each FHIR resource. So as a
openEHR/FHIR community we should aim for a set of templates, as Thomas
indicated, a set of FHIR extensions, and a library of mappings and transforms
Thanks Pablo,
I second that.
Regards
Heath
_
From: Pablo Pazos mailto:pablo.pa...@cabolabs.com>>
Sent: Wednesday, December 19, 2018 3:36 am
Subject: Re: openEHR on FHIR and vice versa
To: For openEHR technical discussions
mailto:openehr-technical@lists.opene
On Tue, Dec 18, 2018 at 2:50 PM Thomas Beale
wrote:
>
> On 18/12/2018 17:04, Pablo Pazos wrote:
>
> Yes, in fact the closest we can get to automatic transformations is just
> defining the mappings between openEHR classes and the correspondent FHIR
> resources, and fee
On 18/12/2018 17:04, Pablo Pazos wrote:
Yes, in fact the closest we can get to automatic transformations is
just defining the mappings between openEHR classes and the
correspondent FHIR resources, and feed that to a system that, for a
specific openEHR instance, provides a mapper user
Yes, in fact the closest we can get to automatic transformations is just
defining the mappings between openEHR classes and the correspondent FHIR
resources, and feed that to a system that, for a specific openEHR instance,
provides a mapper user with constrained options of FHIR resources to choose
Hi Thomas,
This is an excellent description and is inline with our implementation.
Regards
Heath
From: 3003270n behalf of
Sent: Monday, November 26, 2018 11:43 pm
To: Openehr-Technical
Subject: Better definition of 'system_id' attribute in openEHR sytems
I agree Pablo and we have to remember that the number of high-quality,
truly interoperable FHIR profiles is going to be very small for a long time.
@Dileep V S - we have started to put FHIR bindings
in CKM archetypes but in practice, the FHIR-openEHR mappings will between
local FHIR profiles
I also concur with Bert that if CKM were to develop into what is intended
to be, the FHIR mapping problem can cease to be a major concern for
majority of the use cases.
Could we not look at extending term mapping in OpenEHR to cover this
requirement also? That way nodes in archetypes can
In fact is this a bit of exciting question. On one side, the OpenEhr
community has the point of view that OpenEhr is static, CKM rules and is
planned to cover the whole information requirement for healthcare. Do not
invent your own archetypes, but use the high quality CKM archetypes is an
advice I
I also did some mapping work FHIR -> openEHR using Mirth, but this is
ad-hoc, no automatic mapping yet, for that you need to define a lot of
constraints to make it work automatically. Maybe some semi-automatic tool
come out in the future, assisting architects on doing such mappings, either
mail: georg.fe...@uni-wuerzburg.de
-
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr
> Dipl.-Inf. Georg Fette Raum: B001
> Universität WürzburgTel.: +49-(0)931-31-85516
> Am Hubland Fax.: +49-(0)931-31-86732
> 97074 Würzburg mail: georg.fe...@uni-wuerzburg.de
> -
>
>
> __
I was thinking in a openEHR -> FHIR bundle, similar to what they already do
with CDA
El vie., 14 dic. 2018 a las 12:40, GF () escribió:
> The requiremetns for OpenEHR are NOT the same as those for FHIR or CIMI.
> Therefor a complete generic mapping is impossible.
> Always it will
Fette Raum: B001
Universität WürzburgTel.: +49-(0)931-31-85516
Am Hubland Fax.: +49-(0)931-31-86732
97074 Würzburg mail: georg.fe...@uni-wuerzburg.de
-----
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
The requiremetns for OpenEHR are NOT the same as those for FHIR or CIMI.
Therefor a complete generic mapping is impossible.
Always it will be an ad-hoc, bespoke, one.
The choices FHIR made for its Resources differ from those of OpenEHR and CIMI
archetypes.
They do NOT share the same Reference
11:49 schreef Diego Boscá :
> Hello Georg,
>
> The main result of that paper was supporting FHIR as a reference model to
> define archetypes (you can do that with no limitations on the currently
> available tool). There is no openEHR archetype <-> FHIR profile service
>
Hello Georg,
The main result of that paper was supporting FHIR as a reference model to
define archetypes (you can do that with no limitations on the currently
available tool). There is no openEHR archetype <-> FHIR profile service
yet, although I believe that providing a openEHR -> FHIR
Hi Georg
In terms of openEHR to/from FHIR transformation, the (open source) QEWDjs
part of our stack does this work.
See this video explainer here (with related JSON transformation examples in
the links below)
https://www.youtube.com/watch?v=iaGGGgJdWvM=9=PLNxHSK29ViKLrrhdPTqbYr6XGTya4uGBv=0s
Let
Hello,
I have just read the paper "Combining Archetypes with Fast Health
Interoperability Resources in Future-proof Health Information Systems",
in which the representation of openEHR archetypes as FHIR profiles is
presented. As I am also trying to use this approach an
Following SPECPR-99 <https://openehr.atlassian.net/browse/SPECPR-99> and
this email string
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/2014-August/008468.html>
from 2014, the imminent RM 1.0.4 release will include SPECRM-80
<https://openehr.atlas
Hi Ricardo,
Yes, I've integrated SNOMED Expressions into our path-based queries, that
is basically another syntax for openEHR queries, alternative to AQL.
What I did was adding the operator in_snomed_exp associated to
DV_CODED_TEXT, so you can say something like "retrieve all the composi
Hi all,
It's been a while since I've seen it but I think Pablo Pazos has some quite
good work for that topic on EHRServer, at least for subsumption [
https://ppazos.github.io/cabolabs-ehrserver/ mentions "Support of SNOMED CT
Expressions on openEHR queries (simplifies complex qu
e,
We’ve recently started an informal and practically oriented regular contact
with the Norwegian SNOMED CT NRC. One of the things they were interested in
discussing was how to use postcoordinated SNOMED CT (expression constraint
language) expressions with openEHR, which I know nothing about. Does anyone
terested in discussing was how to use postcoordinated SNOMED CT
> (expression constraint language) expressions with openEHR, which I know
> nothing about. Does anyone have any knowledge about or experience with this?
>
>
>
> Kind regards,
> *Silje Ljosland Bakke*
>
>
>
&g
-Chair, openEHR Foundation ian.mcnic...@openehr.org
Director, freshEHR Clinical Informatics Ltd.
Director, HANDIHealth CIC
Hon. Senior Research Associate, CHIME, UCL
On Mon, 19 Nov 2018 at 15:38, Thomas Beale wrote:
> I mostly agree with Ian, but with the small caveat that for very speci
ordination is like nuclear fusion - a damned good idea but
tricky to do without blowing everything up.
Ian
Ian
Dr Ian McNicoll
mobile +44 (0)775 209 7859
office +44 (0)1536 414994
skype: ianmcnicoll
email: i...@freshehr.com <mailto:i...@freshehr.com>
twitter: @ianmcnicoll
Co-Chair, openEHR Foun
*Attention all users of the openEHR BMM files*:
these used to be in the Github repo reference-models
<https://github.com/openEHR/reference-models>, but have now moved to
specifications-ITS-BMM Github repo
<https://github.com/openEHR/specifications-ITS-BMM>. They have also had
nu
(0)775 209 7859
office +44 (0)1536 414994
skype: ianmcnicoll
email: i...@freshehr.com
twitter: @ianmcnicoll
Co-Chair, openEHR Foundation ian.mcnic...@openehr.org
Director, freshEHR Clinical Informatics Ltd.
Director, HANDIHealth CIC
Hon. Senior Research Associate, CHIME, UCL
On Mon, 19 Nov 201
Hi everyone,
We've recently started an informal and practically oriented regular contact
with the Norwegian SNOMED CT NRC. One of the things they were interested in
discussing was how to use postcoordinated SNOMED CT (expression constraint
language) expressions with openEHR, which I know
IIRC the LHS toolbox project at the Norwegian Centre for E-health Research is
doing federated AQL queries? I don’t know the details, but I suspect someone
else on this list do.
Regards,
Silje
From: openEHR-technical On Behalf
Of Ian McNicoll
Sent: Friday, October 5, 2018 12:46 AM
's SHRINE in the openEHR world ? SHRINE
is a system that distributed an i2b2 query to a network of i2b2
installations and aggregates the returned results.
Greetings
Georg
--
Thomas Beale
Principal, Ars Semantica <http://www.arssemantica.com>
Consultant, ABD Project, Intermountain Heal
Hello,
Is there an equivalent to i2b2's SHRINE in the openEHR world ? SHRINE is
a system that distributed an i2b2 query to a network of i2b2
installations and aggregates the returned results.
Greetings
Georg
--
-
Dipl.-Inf
I've put up a wiki page with a draft of what a real world guideline
<https://openehr.atlassian.net/wiki/spaces/spec/pages/344621059/openEHR+Expression+Language+EL>
(for choosing breast cancer therapy, based on various input variables)
might look like in the emerging openEHR Expr
n/status/1037276071002038272
> <https://twitter.com/ianmthompson/status/1037276071002038272>
>
> Bert
signature.asc
Description: Message signed with OpenPGP
_______
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
better solution in this case,
with the original patient being given the new EHR id.
I think GDPR has some way to go yet in healthcare...
- thomas
_______
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/m
s perhaps permanent anonymisation is a better solution in
> this case, with the original patient being given the new EHR id.
>
> I think GDPR has some way to go yet in healthcare...
>
> - thomas
>
signature.asc
Description: Message signed with OpenPGP
________
In my view, GDPR is a huge opportunity for openEHR.
Issues like versioning of templates and compositions allow security aligned
with GDPR.
Ricardo Correia
---
Ricardo João Cruz Correia
Professor Auxiliar
ISI: www.researcherid.com/rid/A-2756-2009
research gate: www.researchgate.net/profile
On 04-09-18 16:40, Ricardo Correia wrote:
Dear all,
I published recently an attempt to "systematyse" the relation between
openehr and gdpr.
Thanks very much for sharing, I am sure that the chapter OpenEhr and
GDPR is not yet to be closed, there is quite some work to do.
Altho
Really useful resource Ricardo!
El mar., 4 sept. 2018 a las 16:41, Ricardo Correia (<
ricardo.jc.corr...@gmail.com>) escribió:
> Dear all,
>
> I published recently an attempt to "systematyse" the relation between
> openehr and gdpr.
>
> Hope i
Dear all,
I published recently an attempt to "systematyse" the relation between
openehr and gdpr.
Hope it is useful to you.
Link: http://ebooks.iospress.nl/publication/48760
Regards,
Ricardo Correia
---
Ricardo João Cruz Correia
Professor Auxiliar
ISI: www.researcherid.com/rid/A
remark
Bert
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
provider, I think this is fine according to the law, but still some
> law-changes may be needed.
I think we agree.
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
_______
openEHR-technical mailing list
openEHR-technical@lists.o
tural details, for which
> > solutions can be found.
>
> Not in the real world today.
>
> Karsten
> --
> GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
>
> ___
> openEHR-technical mailing list
&g
transaction is subject to archiving laws. For tax purposes the time period is 5
years in the Netherlands, I think. Only after these periods as defined by law
the transactions can/must be deleted.
In the case of the EHR (13606 / OpenEHR) there is a need to ‘obscure' the
patient in the clinical
mple, to prepare for a
> > visit next day, he can ask the patient to allow access to the PHR the day
> > before the visit, but these are al infrastructural details, for which
> > solutions can be found.
>
> Not in the real world today.
>
> Karsten
> --
> GPG 40BE 5B
n
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
_______
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
is a better
>> solution in this case, with the original patient being given the new EHR id.
>>
>> I think GDPR has some way to go yet in healthcare...
>>
>> - thomas
>>
>> On 01/09/2018 18:57, Diego Boscá wrote:
>>
>> If a patient uses a priv
a patient uses a private health provider then he has the right of
> taking all that information and move to another provider. In that case he
> will want a hard-delete of data. And I hope private health providers are
> also able to use openEHR ;D
> I think we should also review the &quo
4994>
> skype: ianmcnicoll
> email: i...@freshehr.com
> twitter: @ianmcnicoll
>
>
> Co-Chair, openEHR Foundation ian.mcnic...@openehr.org
> Director, freshEHR Clinical Informatics Ltd.
> Director, HANDIHealth CIC
> Hon. Senior Research Associate, CHIME, UCL
>
>
&g
and API. Apple will certainly connect too. What will run below is not
specified. It could well be OpenEhr. Their might also be smaller parties which
will be health data provider.
The idea is that the patient (or better, consumer) becomes the owner of the
data. A connected PHR. He gives
On Sat, Sep 01, 2018 at 08:33:08PM +0200, Diego Boscá wrote:
> Supporting hard delete doesn't mean mandate hard delete :)
Indeed. I agree with that.
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
___
openEHR-technical mail
> > need to support that kind of delete operations to allow openEHR systems
> to
> > be GDPR compliant
>
> Whether we like it or not (I do not like it, personally, as a
> patient, but do like it, professionally, as a GP): in Germany
> there is the right to keep a record &
nother provider. In that case he
> will want a hard-delete of data. And I hope private health providers are
> also able to use openEHR ;D
> I think we should also review the "consent" mechanisms we have, as they
> probably should also be tweaked to comply with GDPR.
>
&
providers, so we have the legal
> need to support that kind of delete operations to allow openEHR systems to
> be GDPR compliant
Whether we like it or not (I do not like it, personally, as a
patient, but do like it, professionally, as a GP): in Germany
there is the right to keep a record &q
s to allow openEHR systems to
be GDPR compliant
El sáb., 1 sept. 2018 a las 20:17, Karsten Hilbert ()
escribió:
> On Sat, Sep 01, 2018 at 07:57:31PM +0200, Diego Boscá wrote:
>
> > If a patient uses a private health provider then he has the right of
> taking
> > all that informati
then he has the right of
taking all that information and move to another provider. In that case
he will want a hard-delete of data. And I hope private health
providers are also able to use openEHR ;D
I think we should also review the "consent" mechanisms we have, as
they probably s
AC80 7D4F C89B
_______
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
If a patient uses a private health provider then he has the right of taking
all that information and move to another provider. In that case he will
want a hard-delete of data. And I hope private health providers are also
able to use openEHR ;D
I think we should also review the "consent"
It
> does allow for copies of the record to be retained for medico-legal
> purposes.
The latter reason for retention would have a hard limit of 30
years in Germany.
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
_______
openEHR-technic
7859
office +44 (0)1536 414994
skype: ianmcnicoll
email: i...@freshehr.com
twitter: @ianmcnicoll
Co-Chair, openEHR Foundation ian.mcnic...@openehr.org
Director, freshEHR Clinical Informatics Ltd.
Director, HANDIHealth CIC
Hon. Senior Research Associate, CHIME, UCL
On Sat, 1 Sep 2018 at 14:52
OpenEhr does not really allow to delete data, only logical deletion (mark as
deleted), but GDPR demands the right of the patient to be forgotten.
Is there some change expected in the specs for compliance to GDPR, or was this
already implemented?
We had this discussion, slightly different
at design time in
> archetypes. It can be used at runtime. For instance we use snomed expressions
> embedded in openEHR queries to filter coded texts. In the archetype or
> template that defines that coded text, there is only a binding with snomed,
> nothing else.
>
> On Thu, Aug
IMO it means post coordinated stuff can't be used at design time in
archetypes. It can be used at runtime. For instance we use snomed
expressions embedded in openEHR queries to filter coded texts. In the
archetype or template that defines that coded text, there is only a binding
with snomed
Hello,
Using terminology bindings it is posssible to bind terminology IDs of
specific terminologies to archetypes as well as to their members. In the
openEHR documentation it is written that there is no concept of
post-coordination outside the terminology environment. What does that
exactly
1 - 100 of 1999 matches
Mail list logo
