A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Outlook » Contacts
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Additional Phone Number Fields



 
 
Thread Tools Display Modes
  #11  
Old March 21st, 2010, 10:14 PM posted to microsoft.public.outlook.contacts
Leonid S. Knyshov // SBS Expert
external usenet poster
 
Posts: 290
Default Custom Fields in Outlook (was Additional Phone Number Fields)

On 3/21/2010 1:33 PM, Jim Robertson wrote:
On 3/21/10 11:30 AM, in article ,
"Leonid S. Knyshov // SBS Expert"
wrote:

If you have Office Professional or Small Business, you already have BCM.
If not, it's a $149/seat SKU product. It does not require a dedicated
server as it is a light-weight application.


Sorry to keep bothering you.

I couldn't find a stand-alone trial version of BCM. The only download from
MS appears to be as part of MS Office Professional. I already have Office
Standard installed on Win 7 VMs on both my Mac Pro and my MacBook Pro. It's
not obvious to me how I add the BCM without installing all of Office
Professional.

Is there a stand-alone DL of BCM available? If I install BCM trial, when it
expires, will I need to reactivate my Office Standard or the Outlook client
within it?

Is there another way of demonstrating for myself how BCM might be usable for
my purposes?

Thanks again,
Jim Robertson

A standalone SKU means you need to buy the product. $149/license. It was
created specifically to address this concern.

This product is not included with Office 2007 Standard. If you purchased
the Office 2007 product within the last 90 days, something could be done
about that with volume licensing but that's off-topic and unlikely.

There is actually no such thing as BCM trial and it won't stop working
unlike other Office products (in fact, that's how we install it on
volume license deployments where BCM is excluded from the download
package but legal to use), but you can't legally use it with Office 2007
Standard. The only way you could legally try it would be to uninstall
your licensed version of Office 2007 Standard and install trial of
Office 2007 Professional, install BCM on top of that. You might as well
install Office 2010 Professional Plus beta while you are at it and enjoy
the improvements.

There is an upgrade SKU for Office 2007 Small Business, but it will
actually buy you Office 2010 Professional as of today.

For a preview, see
http://www.microsoft.com/events/seri...webcastid=2214

Customization is covered at about 12 minutes into video.

More webcasts are available at
http://www.microsoft.com/events/seri...casts&id=42401
--
Leonid S. Knyshov
Crashproof Solutions
510-282-1008
Twitter: @wiseleo
http://crashproofsolutions.com
Microsoft Small Business Specialist
Try Exchange Online http://bit.ly/free-exchange-trial
Please vote "helpful" if I helped you
  #12  
Old March 22nd, 2010, 03:08 AM posted to microsoft.public.outlook.contacts
Diane Poremsky [MVP]
external usenet poster
 
Posts: 17,338
Default Custom Fields in Outlook (was Additional Phone Number Fields)

Will the EHR system be able to import Outlook or BCM data? If not, migration
may not be easy. I would first find out what format the main EHR systems
can import and plan from there. You don't want to spend hours creating the
records in Outlook only to discover you can't import them into the EHR
system.

BCM data is not accessible from OWA.

See http://msdn.microsoft.com/en-us/library/ee693018.aspx for info on
customizing OWA forms. It's not as simple as customizing an Outlook form and
having it available in OWA. It's actually a lot of effort - definitely more
effort than its worth for 6 months use. You could probably put something
together in Access with a SQL backend (SQL Express if your SBS doesn't
include it) that can be accessed using either Access or Infopath.

If it comes down to hiring someone to develop a system for you, you're
probably better off putting the funds into EHR (dev work can be pricey).
With just basic knowledge of Access and the desire to learn, you could do a
database yourself fairly easily. It won't be fancy, but it will store the
data. If your office version doesn't have Access (or Infopath), I wouldn't
buy it - save the money for the EHR and use sharepoint. It can be accessed
over the web (although you need to be sure its secure and in compliance with
HIPPA).


--
Diane Poremsky [MVP - Outlook]
Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com/

Outlook Tips by email:


EMO - a weekly newsletter about Outlook and Exchange:


Do you sync your mailbox with a smartphone or pda?
http://forums.slipstick.com/showthread.php?t=39473



"Jim Robertson" wrote in message
...
On 3/21/10 9:52 AM, in article
, "Diane Poremsky [MVP]"
wrote:

I would not recommend BCM for this - I don't think I would even suggest
Outlook for it. I'd use Access or Infopath against SQL. Sharepoint is an
option too.


I'm looking at this as a VERY temporary solution (months to less than two
years) for a small LAN consisting of a an SBS 2008 server, 4 docs who work
with laptops on and off the domain, and 5 office staff with workstations
permanently on the domain. We're on a limited budget, and my idea was to
use
the tools we now have (MS Office Outlook for some staffers, Outlook Web
Access for others) to get patient and referring physician information into
a
contact form that would be usable now but capable of being migrated to a
commercial electronic health record once we purchased one.

Adding a second server box and upgrading our SBS license to premium and
buying BCM licenses for our office staff just to make our lives a little
bit
easier now and migration easier later (especially since after the
migration
we'd have no use for BCM) probably doesn't make sense.

I know nothing about InfoPath. I've peeked at its product page, which
suggest it can be used to design forms that can be opened in Outlook. I
also
haven't begun exploring SharePoint yet (I'm a Mac guy doing this in my
spare
time).

Is InfoPath a tool that I could use to modify the basic Outlook contacts
template so that users on our SBS domain using the full Outlook client or
OWA could open a contact form for patients that would contain the
additional
data elements (referring physician, Social Security Number, and yes/no
status fields for which a checkbox would be the interface element (active
patient, deceased, dialysis, and transplant would be examples)? Or would
we
need the SQL server?

Sorry to ask such basic questions. I'm taking baby steps here :-)

Jim Robertson

  #13  
Old March 22nd, 2010, 03:21 AM posted to microsoft.public.outlook.contacts
Diane Poremsky [MVP]
external usenet poster
 
Posts: 17,338
Default Custom Fields in Outlook (was Additional Phone Number Fields)

I guess you haven't been on the same playground as the geniuses at CMS who
are implementing the "stimulus" portions of the "HiTech Act." They're
stumbling all over themselves trying to write so many regulations and
penalties that it's going to be a nightmare.


A friend is a dev for one of the top companies. It's no fun for them either.
They need their software ready to go when the regs are finished.

In any event, I'll look at BCM. Just so I understand, however: if I
struggled with InfoPath (or if someone who knew what he was doing used it
as
a development tool), the result would require a SQL server, not just
SharePoint. Is that correct?


SQL Express will do.



  #14  
Old March 22nd, 2010, 02:21 PM posted to microsoft.public.outlook.contacts
Jim Robertson[_3_]
external usenet poster
 
Posts: 16
Default Custom Fields in Outlook (was Additional Phone Number Fields)

On 3/21/10 7:08 PM, in article
, "Diane Poremsky [MVP]"
wrote:

Will the EHR system be able to import Outlook or BCM data? If not, migration
may not be easy. I would first find out what format the main EHR systems
can import and plan from there. You don't want to spend hours creating the
records in Outlook only to discover you can't import them into the EHR
system.

BCM data is not accessible from OWA.


As to point 1, with the requirement for interoperability among EHRs to be
"certified" by CMS or whomever they delegate, I can't imagine that
demographic data in CVS tables couldn't be massaged into whatever we use
eventually, but you're absolutely correct; I should ask that question of any
vendors with whom we're considering working.

As to point 2, that's very relevant to our current needs. Poking around, I
discovered there are user-definable fields in standard Outlook (apparently 4
of them). Their value types can be specified, but the range of formatting
options; e.g., for numeric values, is limited, such that it doesn't seem
possible to have a string of 9 inputted integers display in the format
###-##-#### (as would be desirable for SSN's). Moreover, it's not obvious to
me how to make those extra fields appear on the standard contacts forms.
I'll explore that a bit more.

Things like "pick lists" for referring MD and insurance company could
probably be handled by links instead.

Jim Robertson

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 11:38 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.