Re: [Care2002-developers] [Fwd: The Data Elements of an EHR]
good work, for me interesting tooo! -- 此致 easy 在2009-04-09?16:33:59，"Mark?Alan"??写道： >Interesting... > > >From:? John?Halamka? > >I've?recently?been?asked?to?provide?a?list?of?the?data?elements?of?an >EHR?which?might?be?used?as?part?of?the?ARRA?mandate?to?exchange?data?as >part?of?meaningful?use.?There?are?a?nearly?infinite?number?of?actors, >actions?and?events?for?data?exchange,?but?in?the?interest?of?getting >"data?liquidity"?in?healthcare,?here?are?the?elements?that?are?most >commonly?used?and?represent?a?great?starting?point?for?healthcare >information?exchange.?I?always?strive?for?parsimony?of?standards?-?the >fewest?that?we?need?for?the?purpose.?Below?you'll?see?that?I've?included >the?standards?that?support?the?systems?we?have?in?place?today?as?well?as >the?XML/Web-based?standards?that?support?newer?web-centric?systems?and >healthcare?information?exchanges. > >Demographics >Content:?HL7?2.x?for?messaging,?CCD?for?document?summaries >Vocabulary:?HITSP?Harmonized?codesets?for?gender,?marital?status > >Problem?List >Content:?HL7?2.x?for?messaging,?CCD?for?document?summaries >Vocabulary:?SNOMED-CT > >Medications >Content:?NCPDP?script?for?messaging,?CCD?for?document?summaries >Vocabulary:?RxNorm?and?Structured?SIG > >Allergies >Content:?HL7?2.x?for?messaging,?CCD?for?document?summaries >Vocabulary:?UNII?for?foods?and?substances,?NDC-RT?for?medication?class, >RxNorm?for?Medications > >Progress?Notes?and?Other?Narrative?Documents?(History?and?Physical, >Operative?Notes,?Discharge?Summary) >Content:?HL7?2.x?for?messaging,?CCD?for?document?summaries >Vocabulary:?CDA?Templates > >Departmental?Reports?(Pathology/Cytology,?GI,?Pulmonary,?Cardiology?etc.) >Content:?HL7?2.x?for?messaging,?CCD?for?document?summaries >Vocabulary:?SNOMED-CT > >Laboratory?Results >Content:?HL7?2.x?for?messaging,?CCD?for?document?summaries >Vocabulary:?LOINC?for?lab?name,?UCUM?for?units?of?measure,?SNOMED-CT?for >test?ordering?reason > >Microbiology >Content:?HL7?2.x?for?messaging,?CCD?for?document?summaries >Vocabulary:?LOINC?for?lab?name/observation > >Images >Content:?DICOM > >Administrative?Transactions?(Benefits/Eligibility, >Referral/Authorization,?Claims/Remittance) >Content:?X12 >Vocabulary:?CAQH?CORE > >Quality?Measures >Content:?Derived?from?all?the?data?elements?above >Vocabulary:?Derived?from?all?the?data?elements?above > >Privacy?and?Security >Transport:?HTTPS,?SOAP/REST >Transport?Orchestration:?WS* >Authorization/Access?Control:?XACML > >Given?that?meaningful?use?needs?to?be?achieved?by?2011-2012,?it's?clear >that?we?cannot?rip?and?replace?existing?hospital?information?systems?and >EHRs.?We?need?to?leverage?them,?upgrade?them?over?time,?and?install?new >systems?in?an?incremental?fashion.?This?is?really?true?of?any?change?in >healthcare.?If?we?had?a?greenfield,?we?would?design?healthcare?delivery, >payment,?and?infrastructure?entirely?differently.?Unfortunately,?we?do >not?have?a?greenfield,?we?have?limited?resources,?and?limited?time?to >achieve?healthcare?reform,?so?we?need?to?leverage?what?we?have?and >evolve?it?in?phases. > >HITSP?will?be?reformatting?and?streamlining?its?previous?work?over?the >next?90?days?to?support?ARRA,?the?HIT?Standards?and?Policies?Committees, >and?ONC.?I?hope?you?agree?that?the?list?of?EHR?data?elements?above?is >practical,?achievable?now,?and?reasonable. > >-- >This?SF.net?email?is?sponsored?by: >High?Quality?Requirements?in?a?Collaborative?Environment. >Download?a?free?trial?of?Rational?Requirements?Composer?Now! >http://p.sf.net/sfu/www-ibm-com >___ >Care2002-developers?mailing?list >Care2002-developers@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/care2002-developers -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com___ Care2002-developers mailing list Care2002-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/care2002-developers
Re: [Care2002-developers] [Fwd: The Data Elements of an EHR]
yep really interesting... On Thu, 2009-04-09 at 09:33 +0100, Mark Alan wrote: > Interesting... > > > From: John Halamka > > I've recently been asked to provide a list of the data elements of an > EHR which might be used as part of the ARRA mandate to exchange data as > part of meaningful use. There are a nearly infinite number of actors, > actions and events for data exchange, but in the interest of getting > "data liquidity" in healthcare, here are the elements that are most > commonly used and represent a great starting point for healthcare > information exchange. I always strive for parsimony of standards - the > fewest that we need for the purpose. Below you'll see that I've included > the standards that support the systems we have in place today as well as > the XML/Web-based standards that support newer web-centric systems and > healthcare information exchanges. > > Demographics > Content: HL7 2.x for messaging, CCD for document summaries > Vocabulary: HITSP Harmonized codesets for gender, marital status > > Problem List > Content: HL7 2.x for messaging, CCD for document summaries > Vocabulary: SNOMED-CT > > Medications > Content: NCPDP script for messaging, CCD for document summaries > Vocabulary: RxNorm and Structured SIG > > Allergies > Content: HL7 2.x for messaging, CCD for document summaries > Vocabulary: UNII for foods and substances, NDC-RT for medication class, > RxNorm for Medications > > Progress Notes and Other Narrative Documents (History and Physical, > Operative Notes, Discharge Summary) > Content: HL7 2.x for messaging, CCD for document summaries > Vocabulary: CDA Templates > > Departmental Reports (Pathology/Cytology, GI, Pulmonary, Cardiology etc.) > Content: HL7 2.x for messaging, CCD for document summaries > Vocabulary: SNOMED-CT > > Laboratory Results > Content: HL7 2.x for messaging, CCD for document summaries > Vocabulary: LOINC for lab name, UCUM for units of measure, SNOMED-CT for > test ordering reason > > Microbiology > Content: HL7 2.x for messaging, CCD for document summaries > Vocabulary: LOINC for lab name/observation > > Images > Content: DICOM > > Administrative Transactions (Benefits/Eligibility, > Referral/Authorization, Claims/Remittance) > Content: X12 > Vocabulary: CAQH CORE > > Quality Measures > Content: Derived from all the data elements above > Vocabulary: Derived from all the data elements above > > Privacy and Security > Transport: HTTPS, SOAP/REST > Transport Orchestration: WS* > Authorization/Access Control: XACML > > Given that meaningful use needs to be achieved by 2011-2012, it's clear > that we cannot rip and replace existing hospital information systems and > EHRs. We need to leverage them, upgrade them over time, and install new > systems in an incremental fashion. This is really true of any change in > healthcare. If we had a greenfield, we would design healthcare delivery, > payment, and infrastructure entirely differently. Unfortunately, we do > not have a greenfield, we have limited resources, and limited time to > achieve healthcare reform, so we need to leverage what we have and > evolve it in phases. > > HITSP will be reformatting and streamlining its previous work over the > next 90 days to support ARRA, the HIT Standards and Policies Committees, > and ONC. I hope you agree that the list of EHR data elements above is > practical, achievable now, and reasonable. > > -- > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > ___ > Care2002-developers mailing list > Care2002-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/care2002-developers -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Care2002-developers mailing list Care2002-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/care2002-developers
[Care2002-developers] [Fwd: The Data Elements of an EHR]
Interesting... From: John Halamka I've recently been asked to provide a list of the data elements of an EHR which might be used as part of the ARRA mandate to exchange data as part of meaningful use. There are a nearly infinite number of actors, actions and events for data exchange, but in the interest of getting "data liquidity" in healthcare, here are the elements that are most commonly used and represent a great starting point for healthcare information exchange. I always strive for parsimony of standards - the fewest that we need for the purpose. Below you'll see that I've included the standards that support the systems we have in place today as well as the XML/Web-based standards that support newer web-centric systems and healthcare information exchanges. Demographics Content: HL7 2.x for messaging, CCD for document summaries Vocabulary: HITSP Harmonized codesets for gender, marital status Problem List Content: HL7 2.x for messaging, CCD for document summaries Vocabulary: SNOMED-CT Medications Content: NCPDP script for messaging, CCD for document summaries Vocabulary: RxNorm and Structured SIG Allergies Content: HL7 2.x for messaging, CCD for document summaries Vocabulary: UNII for foods and substances, NDC-RT for medication class, RxNorm for Medications Progress Notes and Other Narrative Documents (History and Physical, Operative Notes, Discharge Summary) Content: HL7 2.x for messaging, CCD for document summaries Vocabulary: CDA Templates Departmental Reports (Pathology/Cytology, GI, Pulmonary, Cardiology etc.) Content: HL7 2.x for messaging, CCD for document summaries Vocabulary: SNOMED-CT Laboratory Results Content: HL7 2.x for messaging, CCD for document summaries Vocabulary: LOINC for lab name, UCUM for units of measure, SNOMED-CT for test ordering reason Microbiology Content: HL7 2.x for messaging, CCD for document summaries Vocabulary: LOINC for lab name/observation Images Content: DICOM Administrative Transactions (Benefits/Eligibility, Referral/Authorization, Claims/Remittance) Content: X12 Vocabulary: CAQH CORE Quality Measures Content: Derived from all the data elements above Vocabulary: Derived from all the data elements above Privacy and Security Transport: HTTPS, SOAP/REST Transport Orchestration: WS* Authorization/Access Control: XACML Given that meaningful use needs to be achieved by 2011-2012, it's clear that we cannot rip and replace existing hospital information systems and EHRs. We need to leverage them, upgrade them over time, and install new systems in an incremental fashion. This is really true of any change in healthcare. If we had a greenfield, we would design healthcare delivery, payment, and infrastructure entirely differently. Unfortunately, we do not have a greenfield, we have limited resources, and limited time to achieve healthcare reform, so we need to leverage what we have and evolve it in phases. HITSP will be reformatting and streamlining its previous work over the next 90 days to support ARRA, the HIT Standards and Policies Committees, and ONC. I hope you agree that the list of EHR data elements above is practical, achievable now, and reasonable. -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Care2002-developers mailing list Care2002-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/care2002-developers
Re: [Care2002-developers] Have problem to install care2x in ubuntu
Dear Mark Alan!
I had use for guide and I can start nginx success test.
But in step 5: I don't know how to change.
And when I start for phpmyadmin it has same problem (403 forbidden).
when I start with care2x/install.php, the firefox browser appear the opening
file (install.php for saving), I don't know how to config this problem in
firefox. I can't install care.
Best regards,
Ly Kim Quyen,
lyk...@gmail.com
+84908282030
On Wed, Apr 8, 2009 at 11:19 PM, Mark Alan wrote:
> Kim Quyen Ly wrote:
> > I am follow the guide in Care Development Blog " Installing care2x 2.6
> > alpha"
> http://care2x.wordpress.com/2008/11/03/installing-care2x-26-alpha/
> > I had success when install phpmyadmin, but when I test it :
> > http://localhost/phpmyadmin, I received the error " 403 Forbidden"
> > (I test success nginx ).
>
> From this I will assume that your nginx setup was successful set up,
> and that it is serving both .html and .php pages.
>
>
> # 1. change 'pma.clinica' for your own values:
> # start by defining some temporary host names
> sudo sed -i -e 's/^127\.0\.0\.1.*/127\.0\.0\.1 localhost clinica.0
> www.clinica.0 pma.clinica.0 care2x.clinica.0/' /etc/hosts
>
> grep '127.0.0.1' /etc/hosts # check if all went well
>
> sudo /etc/init.d/networking restart # restart to apply changes
>
>
> # 2. Use a text editor to create a nginx config for phpmyadmin, changing
> 'pma.clinica.0' for your own values:
> sudo nano /etc/nginx/sites-available/spma
>
> # and copy-and-paste into it the text between the "# --- cut here ---"
> bellow.
>
> # 3. then activate it in nginx:
> sudo ln -svf /etc/nginx/sites-available/spma /etc/nginx/sites-enabled/
> sudo kill -15 $(/bin/pidof nginx) ; sudo /etc/init.d/nginx restart
>
> # 4. test if it works with:
> # https://pma.clinica.0/
> http://pma.clinica.0/
>
>
> # 5. After checking that all went well, you may create another file to
> start care2x (let's call it /etc/nginx/sites-available/care2x). In this
> case, besides changing 'pma.clinica.0' for your own values, also change
> the root directive to something like:
> root /var/www/nginx-default/care2x;
> (or to any other place were you created or linked to your care2x directory)
>
>
> That should do it.
>
> M.
>
>
>
>
> # --- cut here ---
> # nginx - /etc/nginx/sites-available/spma
> #
> server {
>listen pma.clinica.0:80;
>server_name pma.clinica.0;
># redirect to secure https page
> # rewrite ^ https://pma.clinica.0$request_uri? permanent;
> #}
> #server {
> # listen pma.clinica.0:443;
> # server_name pma.clinica.0;
>
>access_log /var/log/nginx/spma.access.log;
>error_log /var/log/nginx/spma.error.log;
>
>root /usr/share/phpmyadmin;
>
> # ssl on;
> # ssl_certificate /etc/nginx/ssl/clinica/server.crt;
> # ssl_certificate_key /etc/nginx/ssl/clinica/server.key;
>
>location / {
>include /etc/nginx/fastcgi_params;
>fastcgi_pass unix:/tmp/php-fastcgi.socket;
>fastcgi_index index.php;
>fastcgi_param SCRIPT_FILENAME
> $document_root$fastcgi_script_name;
> # fastcgi_param HTTPS on;
>}
> }
> # --- cut here ---
>
>
>
> --
> This SF.net email is sponsored by:
> High Quality Requirements in a Collaborative Environment.
> Download a free trial of Rational Requirements Composer Now!
> http://p.sf.net/sfu/www-ibm-com
> ___
> Care2002-developers mailing list
> Care2002-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/care2002-developers
>
--
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com___
Care2002-developers mailing list
Care2002-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/care2002-developers
