Hi Ignacio, I don't understand the question. openEHR doesn't "implement" any functionality, just defines the architecture and knowledge management needed to support any clinical system. What you mention is a functionality/feature that can be implemented by end systems. Rephrasing this, you can "implement" the information structure of the vCard using an archetype. It might take 10 minutes to create such archetype.
-- Kind regards, Eng. Pablo Pazos Gutiérrez http://cabolabs.com Date: Fri, 13 Nov 2015 09:12:54 -0600 Subject: Industry wide support for vCard BDI import and export? From: [email protected] To: [email protected] Hi, We are trying to get basic demographics import/export (BDI) using vCard/Carddav working industry wide. This is an important first step for doing anything with a patient in most systems. Is it possible for openEHR to implement import/export by January 1, 2016? My company Astronaut, LLC which supports a VistA variant has implemented it in approximately 5 hours of programmer and test time. Our implementation is open source. A sample output is below. Please let me know as this would be very useful for most people using these systems. BEGIN:VCARDVERSION:3.0N:ZZTEST;BILLY;;;FN: BILLY ZZTESTGENDER:MBDAY:19910101ADR;TYPE=HOME:;;112 anystreet;Maintown;TEXAS;77025LABEL;TYPE=HOME:112 anystreet\nMaintown\,TEXAS 77025TEL;TYPE=HOME,VOICE:555-111-2222TEL;TYPE=CELL:555-444-9999EMAIL;PREF;INTERNET:[email protected]:ZZTEST1234END:VCARD _______________________________________________ openEHR-clinical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
_______________________________________________ openEHR-clinical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
