al at
> lists.openehr.orghttp://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
>
>
> --
>
> *Dr. Sebastian Garde*
> *Dr. sc. hum., Dipl.-Inform. Med, FACHI*
> Ocean Informatics
>
> Skype: gardeseb
>
>
> --
> [image: Avast logo] <http://www.avast.com/>
>
> Diese E-Mail wurde von Avast Antivirus-Software auf Viren gepr?ft.
> www.avast.com
>
>
> ___
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
>
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
http://www.linkedin.com/in/davidmoner
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
Valencia - 46022 (Espa?a)
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20150320/66730368/attachment-0001.html>
part of the metadata
> management. I know that are some details to be fixed, but what do you
> think about the general idea?
>
> David
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20150320/e9b20ccb/attachment.html>
tion. How do we deal with representing
>> what's a current picture of affairs? It might not matter - it's ok if
>> we assume that the translation work is recorded in some registry for
>> example. Finding the balance is the challenge.
>>
>> - thomas
>
>
>
> ___
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
--
*Dr. Sebastian Garde*
/Dr. sc. hum., Dipl.-Inform. Med, FACHI/
Ocean Informatics
Skype: gardeseb
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren gepr?ft.
http://www.avast.com
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20150320/cc0057d4/attachment.html>
y to strike a reasonable balance
between practical needs (who to contact) and attribution requirements.
It might be worth exploring putting in a 'full version history' URI into
an archetype...
- thomas
-- next part --
An HTML attachment was scrubbed...
URL:
>
> >
>
>
> However.. it's not clear who did the most recently translation, and who
> only did some old translation. How do we deal with representing what's a
> current picture of affairs? It might not matter - it's ok if we assume that
> the translation work is recorded in some registry for example. Finding the
> balance is the challenge.
>
> - thomas
>
>
>
> ___
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20150320/6a274e3e/attachment.html>
hunchback.net>**>**?>*
>version_last_translated = <"2.0.1">
>
> >
> >
>
>
>
> However.. it's not clear who did the most recently translation, and
> who only did some old translation. How do we deal with representing
> what's a current picture of affairs? It might not matter - it's ok if
> we assume that the translation work is recorded in some registry for
> example. Finding the balance is the challenge.
>
> - thomas
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20150320/10c86510/attachment.html>
6 matches
Mail list logo