Stop the war!

Остановите войну!

for scientists:

default search action

combined dblp search
author search
venue search
publication search

ask others

Sidna M. Tulledge-Scheitel

Name: dblp XML data dump
Creator: Schloss Dagstuhl - Leibniz Center for Informatics
Published: 1993
License: https://creativecommons.org/publicdomain/zero/1.0/
Keywords: dblp, XML, computer science, scholarly publications, metadata

◀ ▶ joint publications with Nick Beard

> Home > Persons > Sidna M. Tulledge-Scheitel

Publications

2004
[c2]
- view
  - electronic edition via DOI (open access)
  - references & citations
  authority control:
- export record
  dblp key:
  - conf/medinfo/TuMSCHMHMPRABGM04
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/medinfo/TuMSCHMHMPRABGM04
Samson W. Tu, Mark A. Musen, Ravi D. Shankar, James R. Campbell, Karen M. Hrabak, James C. McClay, Stanley M. Huff, Robert C. McClure, Craig G. Parker, Roberto A. Rocha, Robert M. Abarbanel, Nick Beard, Julie Glasgow, Guy Mansfield, Prabhu Ram, Qin Ye, Eric Mays, Tony Weida, Christopher G. Chute, Kevin McDonald, David N. Mohr, Mark A. Nyman, Sidna M. Scheitel, Harold Solbrig, David A. Zill, Mary K. Goldstein:
Modeling Guidelines for Integration into Clinical Workflow. MedInfo 2004: 174-178
2002
[c1]
- view
  - electronic edition @ amia.org
  - no references & citations available
- export record
  dblp key:
  - conf/amia/BeardCHLMMMMMORSST02
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/amia/BeardCHLMMMMMORSST02
Nick Beard, James R. Campbell, Stanley M. Huff, Mauricio Leon, James G. Mansfield, Eric Mays, James C. McClay, David N. Mohr, Mark A. Musen, David O'Brien, Roberto A. Rocha, Anne Saulovich, Sidna M. Scheitel, Samson W. Tu:
Standards-based Sharable Active Guideline Environment (SAGE): A Project to Develop a Universal Framework for Encoding and Disseminating Electronic Clinical Practice Guidelines. AMIA 2002

a service of

manage site settings

To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.