Article Submission Guidelines
health Management technology is written for senior executives in hospitals, healthcare
organizations, integrated delivery networks, managed care organizations and health plans, and
physician practices and IPas.
our readers are ceos, cIos, cFos, cMos, ctos, It directors and managers, and other decision
makers working in information technology in healthcare settings.
Please send queries and abstracts to:
[email protected], or to the following address:
health Management technology
attn: editor
2477 Stickney Point road Suite 221b
Sarasota, Fl 34231
WHAT WE ARE LOOKING FOR
exclusive, informative, non-promotional, original content.
4FEATURES: Feature articles explore advances in healthcare information technology. We
examine issues and questions facing executives as they make technology decisions for their
organizations—facts they need to know, obstacles, technology trends, available options, or
innovations to consider. We cover a wide range of topics described in our editorial calendar
and we welcome suggestions for new topics not listed. We accept submissions of solutionsbased, real-world application stories in a case-study format written by providers and suppliers.
We also publish tutorials that discuss technology developments important to healthcare
organizations (i.e., hospitals, healthcare organizations, integrated delivery networks, managed
care organizations and health plans, and physician practices and independent practice
associations). articles should be focused on end-user solutions, or solutions provided by
service providers to end-users.
4THOUGHT LEADERS: this feature offers an opportunity to editorialize on a healthcare or
technology topic of your choice. the thought leaders column is typically about 800 words in
length. a high-resoltion photo of the author is required for use on the cover.
4THINK TANK: our cover feature article is staff-written and includes exclusive interviews
with key healthcare professionals from providers, suppliers, and associations involved in the
industry. check our editorial calendar for topics in which you may wish to participate, including
nominations for c-Suite It innovators for our editors to follow.
contact [email protected] for specifics.
GETTING STARTED
1. Send us a short abstract. Indicate the issue month and the focus of the article in the subject
line of your e-mail. Monthly topics can be found in our editorial calendar at www.healthmgtech.
com/advertise. After defining the topic, write a detailed decription of what you wish to convey in
your article. Please identify the supplier or provider used in the article.
2. IMPORTANT: Include the supplier or provider’s name, address, phone, fax, email and fax who
would be the contact person for reader inquiries. We will also need the contact name, phone
number and e-mail address of anyone mentioned or quoted for the article. Editors routinely call
these contacts to verify information or to ask additional questions. Failure to provide these contacts
can result in your article being rejected. DO NOT submit an abstract unless the companies involved
(supplier or provider) have agreed to have the article published.
3. Email the abstract to the managing editor at least 12 weeks prior to publication date (e.g.,
Dec. 1 for the March issue). We will review all proposals at the same time and inform potential
contributors whether their abstract has been accepted. Please do not call to “check the status” of
your abstract.
CASE STUDIES should be solution-based, providing practical and useful information to healthcare
organization end-users (i.e., hospitals, healthcare organizations, integrated delivery networks,
managed care organizations and health plans, and physician practices and independent practice
associations). A simple and effective formula is: “Here is a problem we had; here is the way we
solved it; these are the products and techniques we used; this is how we are working now.”
A case study should not be more than two years old. It should include all the elements of the
solution, not just the provider’s products. We prefer third-person accounts, so try to include quotes
from the end-user. Case studies should not carry the provider’s byline, since the provider and
products are mentioned in the story. Also, quotes from the provider are generally inappropriate for
case histories and are usually deleted from manuscripts. A case study should focus on just ONE
end-user situation, not on multiple end-user examples.
PLEASE DON’T MANUFACTURE QUOTES IN CASE HISTORIES. Interview the subject and use real
quotes. An unacceptable example: “XYZ company did a fantastic job with the implementation, and
their products are saving us lots of time and money.” These types of quotes are generally deleted
from the article.
Here is some information we prefer in the article:
4Describe the problem solved and the improvements made.
Be descriptive of an actual situation that illustrates the point, rather than simply making the point, as in “the solution provides security.” Put a statement in context with an actual example of how security was provided for the customer.
4Provide a straightforward presentation on how a solution was implemented
Describe what the challenges were and what the results are, so IT decision-makers will have most of their questions answered. Remember the technical side of the implementation is the most important element of a case study, providing useful information to CIOs, and IT and department managers who want to know how the network is configured, what changes were made, how the changes affected the network, etc.
4Was there a particular moment or occurrence that crystallized the need for the solution?
4How did the problem increase expenses, hinder operations, or cause staff to be unproductive?
TUTORIALS examine a new, basic, or advanced technology in a new or updated context.
A tutorial article should be readable and, where possible, cite specific examples and cases. It will
carry a byline from a provider representative, but the provider’s products will not be mentioned in
the article.
Please do not submit an opinion piece as a tutorial. We prefer a discussion of solutions, not
problems. Your article should explain how the technology is used and the benefits the end-user.
Avoid too much historical background. Do not criticize competing technologies; instead focus on the
features, implementation, benefits, etc., of the technology you are writing about.
Tutorials should be solution-based, providing practical and useful information to end-users.
4Provide a straightforward presentation of the technology/solution discussed, so that IT
decision-makers will have at least most of their questions answered.
4What are the cost and staffing implications of the technology/solution being discussed?
4Is the solution interoperable with other components of the network? If not, what changes must be made to provide interoperability?
4Describe the most important components of the technology/solution.
4What are the benefits, in terms of savings, in productivity, customer care, service, etc.?
PLEASE NOTE
4Articles that are self-serving or recite the technical specifications of a particular product are unacceptable. The article should not serve as a thinly disguised promotion for a product or company.
4Any submission of articles must be exclusive to Health Management Technology. We generally do not accept articles that have been published in another trade journal, newspaper, periodical, on the Web, company literature, or conference proceedings.
4To be fair to all potential contributors, we limit the frequency of articles accepted for publication from any one company to no more than one article every four months.
4Our feature stories generally run from 800 words to 2,000 words.
4f your article is accepted for publication, please undertand that your manuscript will be edited for style, space requirements, and ease of reading.
4We do not include trade or copyright marks in editorial.
4Please submit your article via email as a Word document. Do not embed graphics, artwork or photos in the article’s Word document.
4Graphics attached should be in tif or jpg format with resolution of at least 300 dpi. Low resolution images or images embedded in Word, PowerPoint, PDF, or other files are not acceptable. Please include separate captions for all graphics. Line drawings such as tables, charts, or schematics are acceptable. Submit all line drawings as high-resolution art. You may include some form of art for consideration as an introduction to the article. This color material would be placed on the opening page of the article, be of high quality, and unique.
4If your article is accepted, you will be required to send us a signed COPY RELEASE FORM on the next page, or found at www.healthmgttech.com (under ABOUT US tab). No submission will be published without it.
2477 Stickney Point Road Suite 221-B
F: 941/388-7490 ATTN: HMT Editor
Sarasota, FL 34231 P: 941/388-7050
[email protected]
Copy Release
I hereby release copyrights to all materials and articles submitted to nP communications llc for
publication in health Management technology.
this release gives nP communications and its assignees worldwide rights for all forms of publishing,
including digital and online rights. I retain all other rights and ownership of the materials and articles.
Topic/Title of Article __________________________________________________________________
Proposed Date of Publication _________________________________________________________
Name of Author _____________________________________________________________________
(please print)
Direct Contact for Author (Required)
Phone ______________________________________________________________________________
Email _______________________________________________________________________________
Company Name _____________________________________________________________________
Company Address ___________________________________________________________________
Company City/State/Zip ______________________________________________________________
Company Phone Number ___________________________________________________________
Author’s Signature _________________________________________________________________
Date ________________________