Wes,
Well said - and an excellent informative recap of what's happening in health
care apart from HIPAA-land! My personal opinion is that whatever work
product results from this group's efforts must support any type of payload
consistent with the ebXML MS.
Rachel Foerster
-Origin
Bruce,
I agree with you. Given that, are you making any recommendations for changes
to the draft document. I didn't seem to see any?
Thanks,
Rachel
-Original Message-
From: Bruce T LeGrand [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 14, 2002 9:04 AM
To: WEDI/SNIP Listserve
Subje
col Profile
and CPA is a Collaboration Protocol Agreement.
Rachel Foerster
-Original Message-From: Hipaa Guru Jr.
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, August 13, 2002 8:03
PMTo: [EMAIL PROTECTED]Subject: CPP & CPA
defined
I want to apoligize for my ignorance
eb site at www.x12.org. Drill
down to the X12N pages and then follow the links to the download documents.
The first one listed, Introduction to Requirements Management Using the
UN/CEFACT Unified Modeling Methodology, is the one I'm referring to.
Rachel Foerster
-Original Message-
Fr
t for two entities to then reach agreement (CPA) on
how they will conduct business electronically. Trying to develop a CPP
without first going through the use case analysis and rigorously documenting
the results will only result in an incomplete/inaccurate/unusable CPP.
Rachel Foerster
-Ori
partners agree on the codes to be used.
Rachel Foerster
-Original Message-
From: Hipaa Guru Jr. [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 09, 2002 5:38 PM
To: [EMAIL PROTECTED]
Subject: Fw: 276 routing question, esp. interested in Clearinghouse
guru's opinion
I believe I
y.it's whether someone makes the payroll at the end of the week or
not.
A CPP is only one aspect of establishing an electronic messaging interface.
Agreeing to it is the other, and the CPA specification from ebXML is what
addresses this aspect.
Rachel Foerster
Principal
Rachel Foerster &a
up with that perfect all-encompassing CPP isn't realistic nor
achievable, in any timeframe. It's much more important to get something
simple that can be used quickly so the industry can either see the
benefit/value or not and then grow it as needed.
Rachel
Rachel Foerster
Principal
Rachel Foerster
Ken,
If I'm not mistaken, the payer-to-payer model is currently what Medicare
follows where Medicare processes/adjudicates as primary and then forwards
the claim on to the Medigap insurerright? Is the secondary payer
(Medigap in this example) be identified in the primary claim submission or
t
h a continued discussion of companion documents. These
discussions only serve to distract attention from the group's primary goal.
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-8
they have trading partner agreements to
conduct COB. Once such an agreement
is in place, a health plan may not refuse
to accept and process a COB transaction
on the basis that it is a standard
transaction."
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI &am
t the CPP/A as presently spec's expects that specific business process
scenarios, etc. that each of the trading partner's support be identified.
The use of process analysis resulting in business scenarios is a critical
and essential concept to Open-edi, ebXML and CPP/A.
Rachel Foerster
P
oup's list.
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
Fax: 847-872-6860
http://www.rfa-edi.com
-Original Message-
From: William J. Kammerer [mailto:
Please excuse my confusion here, but I don't see how the use of companion
guides is related to the challenges of addressing and routing. Are we
getting off on a non-essential tangent to the primary goal of this group?
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Profess
r vision of the future for health information exchanges.
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
Fax: 847-872-6860
http://www.rfa-edi.com
discussions on this lis
s that would
be within the realm of solution by an automated health care registry.
Rachel Foerster
-Original Message-
From: William J. Kammerer [mailto:[EMAIL PROTECTED]]
Sent: Saturday, June 29, 2002 5:24 PM
To: WEDi/SNIP ID & Routing
Subject: Re: Non-participating/out of network p
outing of transactions to payers from non-par/out-of-network
providers one that should require a lot of analysis/discussion, but rather
be put in a "parking lot" for future work effort?
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Comme
Julie, 2pm PST = 4pm CT and 5pm ETalready at the close of business for
many people.
Julie, I've now seen several messages on this, each with a different time.
Could you just lay out all of the details in a single message? Thanks.
Rachel
-Original Message-
From: Julie A. Thompson [ma
Julie,
When, where, how, duration, cost?
Rachel Foester
-Original Message-
From: Julie A. Thompson [mailto:[EMAIL PROTECTED]]
Sent: Saturday, June 29, 2002 12:20 PM
To: 'WEDi SNIP 4 (E-mail 3) '; '[EMAIL PROTECTED]'
Cc: Julie A. Thompson
Subject: Your are invited to HIPPA Transaction Te
achel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
Fax: 847-872-6860
http://www.rfa-edi.com
discussions on this listserv therefore represent the views of the individual
partici
070 standard to
be replied to any claim with adjudication issues. This will be
re-clarified in a NJ meeting next month.
Please redirect any other questions to X12 Insurance TG2 WG5 or to me
directly, if applicable.
Dominic Saroni
Associate
Rachel Foerster & Associates, Ltd.
Professionals in EDI &
uire a 277 Unsolicited v3070 standard to be
replied to any claim with adjudication issues. This will be re-clarified in
a NJ meeting next month.
Please redirect any other questions to X12 Insurance TG2 WG5 or to me
directly, if applicable.
Dominic Saroni
Associate
Rachel Foerster & A
ng up.
Out of scope!
Rachel
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
Fax: 847-872-6860
http://www.rfa-edi.com
-Original Message-
From: William J. Kammerer [ma
Dave,
The prohibition against posting commercial messages already exists for all
WEDi SNIP lists.
Rachel
-Original Message-
From: Dave Minch [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 25, 2002 5:37 PM
To: [EMAIL PROTECTED]
Cc: '[EMAIL PROTECTED]'
Subject: RE: Vendor communications g
William,
I don't think that Dave was advocating "exotic" business modelsjust
recognizing that one needs to have a starting point for developing a roadmap
to another point. For example, if you were going to put an addition on your
home you most likely would start with a model (the blueprint) o
William,
Since as the lead of this work group you've already personally contacted the
other organizations you mentioned, I think it's only appropriate that you
continue this role with HIMSS or any other group with which it makes sense.
http://www.himss.org
Rachel Foerster
Princi
f the NHII. However, interoperability and connectivity are central
to both a NHII and HIPAA. What I am advocating is an effort to reach out to
HIMSS and its membership for greater participation and input into this
group's efforts rather than ignore or downplay such an influential group.
Rachel
t health-care information-technology priority over the next two
years, up from 64% the previous year. Using technology to promote patient
safety and reduce medical errors was the second most-pressing
information-technology issue identified by respondents, now and for the next
two years."
Ra
And round and round the mulberry bush we go! Making the payer-centric
mailbox model go away or even enabling it to go away is not the objective of
this group.
Rachel
Rachel Foerster
Rachel Foerster & Associates, Ltd.
Phone: 847-872-8070
-Original Message-
From: William J. Kamm
Ahh, Paul.we used to call it a "technology in search of a market!" Good
point.
Rachel Foerster
Rachel Foerster & Associates, Ltd.
Phone: 847-872-8070
-Original Message-
From: Paul Weber [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 13, 2002 11:55 AM
To: [EMAIL PROT
, via their
professional associations and a well organized SMP-data content
committee. The startup capital and initial outreach/education, however,
should probably come from the payor and DSMO communities... so that it
happens quickly.
Meanwhile, his group should continue working on our assignment, a
by the CPP and the Registry will make that at all possible.
Thanks again,
William J. Kammerer
Novannet, LLC.
Columbus, US-OH 43221-3859
+1 (614) 487-0320
- Original Message -
From: "Rachel Foerster" <[EMAIL PROTECTED]>
To: "'WEDi/SNIP ID & Routing'" <[E
icates for access to CPP repository
If authentication is in place then there should be no need to worry
about "digital certificates for access to CPP repository."
Rachel Foerster wrote:
>
> Oh Lordy, Lordy! Are we going down a rabbit hole with Alice or what! I
> understand auth
Fact 1: Almost all (if not all) of
the currently mandated HIPAA EDI transactions contain protected health
information
Fact 2: Today's business model
supports and enables protected health information to be stored redundantly by
many intermediaries between a health care provider and p
Oh Lordy, Lordy! Are we going down a rabbit hole with Alice or what! I
understand authentication is part of the CPA spec, but how is this relevant
to getting the industry up and running with EDI by the HIPAA compliance
dates?
Rachel
-Original Message-
From: joe mcverry [mailto:[EMAIL PRO
on-Protocol Profile (CPP) can
accommodate your request.
Thanks for the suggestion.
William J. Kammerer
Novannet, LLC.
Columbus, US-OH 43221-3859
+1 (614) 487-0320
- Original Message -
From: "Rachel Foerster" <[EMAIL PROTECTED]>
To: "'WEDi/SNIP ID & Routing'&qu
a problem not yet defined that any of the vendors
could evaluate and incorporate into their solutions offerings?
I'm all for being a visionarybut a vision without a starting point is
just a wish.
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI &a
about how this info is managed locally by the
interchange senders? The obvious advantage of aligning our repository
structure with a standard local user's "address book" would be
auto-updating ability.
-Chris
At 10:24 PM 6/4/02 -0500, Rachel Foerster wrote:
>Chris,
>
>
focused on the registry component. I believe Dave
Minch is inquiring about standard structures or templates that might be
evolving in OASIS for all or part of the CPP-repository. Are you aware of
anything like this, Rachel?
Regards,
Chris
At 10:24 PM 6/4/02 -0500, Rachel Foerster wrote:
>Chri
usuable by different industry
segments.
NIST would like to field a test registry for WEDI/SNIP CPPs.
--lisa carnahan
NIST
(301)975-3362
[EMAIL PROTECTED]
Quoting Rachel Foerster <[EMAIL PROTECTED]>:
> Chris,
>
> My immediate first-read impression is that this is a good approach.
hcare could tap into using it.
Rachel
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
Fax: 847-872-6860
http://www.rfa-edi.com
-Original Message-
From: Christopher
it return to sender? I bet
not! That envelope is passed to another activity that performs certain
levels of validation, like opening the envelope, examing the content, and
making some determination as to what to do with the content.
Rachel
Rachel Foerster
Principal
Rachel Foerster & Associate
rmore, keep in mind that Wal*Mart's in-store pharmacies are providers.
Thus, this function of Wal*Mart is now a covered entity under HIPAA and as
such, Wal*Mart will have to determine its compliance strategy.
Rachel
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Profes
tification and routing so that point 4 can be
accomplishedand tick tock, tick tockthe clock is ticking and time is
running out!
Rachel
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone:
William,
Well said!
Rachel
-Original Message-
From: William J. Kammerer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 30, 2002 6:15 PM
To: WEDi/SNIP ID & Routing
Subject: Open Portals and "Blind Trust"
Clearinghouses could have taken care of trust issues between payers and
"unknown"
reserve the right to not load data into our system that is
coming from a submitter (which may be a provider) we don't know.
And 5... We process it (provided we can identify the provider).
_
Martin A. Morrison
-Original Message-
From: Rachel Foerster [mailto:[EMAIL PROTECTED]]
Code 40 in NM108 specifies
receiver
Code 41 in NM108 specifies
submitter
Since these two terms can be somewhat ambiguous and
interpretable I very early on in this work group's efforts recommended that a
glossary be developed which provided specific unambiguous definitions to terms.
For
... We process it (provided we can identify the provider).
_
Martin A. Morrison
-Original Message-
From: Rachel Foerster [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 9:15 AM
To: [EMAIL PROTECTED]
Subject: RE: TA1 responding to non-participating health care providers
g
different. I assume that by your "...but..." you are not in favor of
retaining that original functionality (I apologize if I have misread that
point). I believe that eliminating the "Application" capability from the GS
would be a mistake.
Bob
&
Bob,
You are correct in your description and conclusion about the GS
sender/receiver codes. In their first incarnation in the first X12 standard,
they were envisioned to be identifiers for the two party's application
systemsbut their use has morphed, as one would expect over time.
Rachel
-
ut we didn't. If we assume, now, that it's just
a matter of opening all the spigots, I'm afraid we'll all drown.
_
Martin A. Morrison
-Original Message-
From: Rachel Foerster [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 28, 2002 4:49 PM
To: [EMAIL PROTECTED]
d or
used by the health plan (for example,
coordination of benefits information).
(4) A health plan may not offer an
incentive for a health care provider to
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, I
g the
user or the marketplace wants, needs, or will accept.
And lastly, without such a roadmap, it's impossible to manage/lead a project
that achieves the goal of the project to any successful conclusion within
any acceptable timeframe.
Rachel Foerster
Principal
Rachel Foerster & A
erty
and Casualty or Worker's compensation X12N transactions?
Or were you thinking of the supply chain side of Health Care?
William J. Kammerer
Novannet, LLC.
Columbus, US-OH 43221-3859
+1 (614) 487-0320
----- Original Message -
From: "Rachel Foerster" <[EMAIL PROTECTED]
ess him - has even been futzing with a UML diagram; see
http://www.novannet.com/wedi/Healthcare_CPP_Model.jpg.
Developing the spreadsheet is an integral part of enumerating
requirements: what's the problem?
William J. Kammerer
Novannet, LLC.
+1 (614) 487-0320
- Original Message -
From: "Rachel F
: WEDI/SNIP Listserve
Subject: Re: CPP Data elements draft for comment
- Original Message -
From: Rachel Foerster <[EMAIL PROTECTED]>
> Developing a requirements documenthow novel!
What is really novel here is asking USERS (in this case, user=software
developer) what they need.
02 6:35 PM
To: 'WEDI/SNIP Listserve'
Subject: Re: CPP Data elements draft for comment
- Original Message -
From: Rachel Foerster <[EMAIL PROTECTED]>
Subject: RE: CPP Data elements draft for comment
> If this group starts delving into the data of the various HIPAA
transacti
n gathering", which will then be used to reshuffle
sections and fields.
Sorry about that. I'll be more careful commenting next time.
Ajay
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of Rachel Foerster
Sent: Monday, May 06, 2002 9:33 PM
To: '
/required by a
trading partner.
Furthermore, the scope of this effort should not be limited to the HIPAA
transactions, but serve all of health care.
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Ph
Developing a requirements documenthow novel!
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
Fax: 847-872-6860
http://www.rfa-edi.com
-Original Message-
From
provided the
> service they are billing for.. Guess that is fraud the same way we
> have it right now
>
> -Original Message-
> From: Rachel Foerster [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 03, 2002 4:11 PM
> To: [EMAIL PROTECTED]; 'WEDi/SNIP ID & Routing'
>
ernet. Among the requirements that would be
removed would be the HIPAA requirement for encryption.
(Hopefully, this note will be close or will stimulate someone telling us
what the real situation is.)
-Original Message-
From: Rachel Foerster [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 0
hat's new at the Beech!
www.beechstreet.com <http://www.beechstreet.com/>
-Original Message-
From: Rachel Foerster [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 03, 2002 1:11 PM
To: [EMAIL PROTECTED]; 'WEDi/SNIP ID & Routing'
Subject: RE: FW: Article
David,
Int
David,
Interesting letter from the AHA to HHS. A thorough reading of the letter
makes clear that what the AHA is asking HHS to do is declare a
HIPAA-compliant claim as a "clean" claim and thereby kicking in many states'
prompt payment acts for clean claims. To date none of the state prompt pay
ac
William, I think it's a bit misleading to state that CMS refusal to use the
internet. Below is the HCFA Internet Policy statement of 1998. Unless some
official pronouncement from CMS states otherwise,
I've also inserted below the current FAQ from CMS' web site re their
Internet policy.
Rachel
=
Wes, et al,
I would agree that the need to be able to specify a variety of transport
methods and protocols goes beyond just what CMS requiresbut it's
incorrect to presume that CMS prohibits the use of the Internet. See my
other post with CMS' current Internet policies.
Rachel
-Original
ivate network for the
Blues.
Rachel
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
Fax: 847-872-6860
http://www.rfa-edi.com
-Original Message-
From: William J. Kammerer [
e., the meat of the CPP record)? ... that they are
essentially focused on the business transactions that would take place
AFTER the trading partners had established solid, 2-way connection?
Thanks,
Chris
At 12:06 PM 4/21/02 -0500, Rachel Foerster wrote:
>Chris,
>
>The "left field&qu
d take place
AFTER the trading partners had established solid, 2-way connection?
Thanks,
Chris
At 12:06 PM 4/21/02 -0500, Rachel Foerster wrote:
>Chris,
>
>The "left field" I was referring to was the UBL reference, etc. since UBL's
>focus is "to define a common XML librar
y mark up the draft copy.
I see a need to move this effort to a more organized level, starting with
drafts of:
1. Mission and requirements list
2. Definitions of terms used in "addressing and routing"
3. Proposed data elements for the CPP record
Thanks,
-Chris
At 04:42 PM 4/20/02 -050
[X12] to more automated means of setting up
Business relationships 418
and doing Business under them. 419
-Chris
At 04:42 PM 4/20/02 -0500, Rachel Foerster wrote:
>The X12 transaction is the 838 Trading Partner Profile.
>
>I don't know that it informed any of the work that resulte
Chris,
A few thoughts/comments inserted inline to yours below.
Rachel
-Original Message-
From: Christopher J. Feahr, OD [mailto:[EMAIL PROTECTED]]
Sent: Saturday, April 20, 2002 9:40 PM
To: William J. Kammerer; WEDi/SNIP ID & Routing
Cc: Rishel,Wes
Subject: Basic thoughts on ebXML's rel
As a side note, Peter, I, Kepa and others also put together a full day
pre-conference session at the HIPAA Summit West II in San Francisco in
March.
All of that Summit's presenter material, plus previous summits, and the
up-coming summit, is made available for download at no cost at
http://www.hi
ore of the CPP done first.
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
Fax: 847-872-6860
http://www.rfa-edi.com
-Original Message-
From: Christopher J. Feahr, O
d is just plain invalid.
Rachel
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
Fax: 847-872-6860
http://www.rfa-edi.com
-Original Message-
From: David Frenkel [mailto:
More on the continuing saga of ebXML, CPP/A specs and IBM's patent.
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
Fax: 847-872-6860
http://ww
l 19, 2002 9:45 AM
To: [EMAIL PROTECTED]; WEDi SNIP 4 (E-mail 3)
Subject: Re: FW: IBM patents issue response (from ebXML JCC)
Rachel,
Can we safely conclude that this fire has been put out by IBM's statement?
-Chris
18/02 -0500, Rachel Foerster wrote:
>More on ebXML.
>
>Rache
FYI
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
Fax: 847-872-6860
http://www.rfa-edi.com
-Original Message-
From: Martin W Sachs [mailto:[EMAIL PROTECTE
More on ebXML.
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
Fax: 847-872-6860
http://www.rfa-edi.com
-Original Message-
From: James Bryce Clark [mailt
f X12.
Rachel
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
Fax: 847-872-6860
http://www.rfa-edi.com
-Original Message-
From: Scott Nieman [mailto:[EMAIL PROTECTED]]
S
Kepa, Peter, et al,
This could be.it will be interesting to see how IBM follows through on
this. The howls are extremely loud on the ebXML and UN/CEFACT lists.
Rachel
-Original Message-
From: Kepa Zubeldia [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 17, 2002 6:51 PM
To: [EMAIL
FYI,
Rachel Foerster
Hong Kong university starts test ebXML registry
http://www.technewslit.com/news/S20020412_02.html
12 April 2002 -- The Center for E-Commerce Infrastructure Development
(CECID), at the University of Hong Kong (HKU) announced this week the
availability of an OASIS ebXML v2
Michael,
Right on!
Rachel
-Original Message-
From: Michael Mattias/Tal Systems [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 09, 2002 9:30 AM
To: WEDI/SNIP Listserve
Subject: RE: Who am I? Sender, Receiver, Intermediary, or just plain
Chump?
I have followed this thread with some int
So, what's new here. The only valid and allowed ISA sender/receiver
identifiers are those specified in the HIPAA guides. Get over it, and get on
with it.
It seems to me the issue that should be addressed is not which coding system
the identifier is from, but rather the function that identifier sh
ailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 10, 2002 11:16 AM
To: Rachel Foerster
Subject: Re: A proposed work plan for this group
Don't we really get to start fresh considering that most providers
haven't done EDI at all? Even Dave Minch's hospital group is new to EDI,
so can
Ron, while I don't disagree with your comments in general, keep in mind that
nowhere in the HIPAA guides is the ISA sender or receiver identified as any
other party than the provider or the payer. Nothing in the guides, which is
what the industry must use, indicates that the ISA sender or receiver
mpleted by May
3rd. During May the recommendations/specifications/guidance document can be
developed...I would certainly expect that the final draft of this document
could be completed by the end of May.
Comments?
Rachel Foerster
Rachel Foerster & Associates, Ltd.
Phone: 847-872-8070
-Original
nterchange envelopes follow as well.
Rachel
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
Fax: 847-872-6860
http:/www.rfa-edi.com
-Original Message-
From: Chri
Peter's paper can be downloaded from
http://www.hipaasummit.com/pastwest2/agenda/index.html
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
Fax: 847-872-6860
http:/ww
industry to become operationalwhich is not October, 2003, by the
way -- but April of 2003 as required by ASCA.
What do you think?
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-
I'm not sure I understand why the primary focus is only on identifying
providers.? I saw nothing in the original business case document that
limited the effort to providers only.
Rachel Foerster
Rachel Foerster & Associates, Ltd.
Phone: 847-872-8070
-Original Message-
From
k it's quite irrelevant to the goal of this work group to get too
wrapped around the axle about various identification systems. Rather,
shouldn't the focus be on the "functional use" of the identifier in the ISA
as the key to discovering the detailed EDI addressing information?
R
for EDI Addressing of EDI
interchanges"
Folks, where are we on the objective for this work
group? If the objective is neither 1 or 2, then what is
it?
Rachel Foerster Principal
Rachel Foerster &
Associates, Ltd. Professionals in EDI &
Electronic Commerce 39432 North Avenue
Bea
David,
I too saw this article today, and it does have some interesting information.
However, I'm not at all clear on how you feel this article ties into the
focus for this list. Can you draw the link for me?
Thanks,
Rachel Foerster
Rachel Foerster & Associates, Ltd.
Phone: 847
n and animal health
care for a variety of needs to uniquely identify a given entity or a logical
department within a given entity.
Get off of it, get over it, and move on! And can the continual caustic
comments. They're not contributing to the identification of any solutions.
Rachel Foerster
Princi
facturing, SCAC codes for transport, or even
Dun & Bradstreet D-U-N-S numbers.
William J. Kammerer
Novannet, LLC.
+1 (614) 487-0320
- Original Message -
From: "Rachel Foerster" <[EMAIL PROTECTED]>
To: "'WEDi/SNIP ID & Routing'" <[EMAIL PROTECTE
se the HIN without
paying the appropriate fees could be in violation of various copyright and
trademark rights.
This is the reason that I provided you with fictictious examples, etc. of
the HIN in response to your earlier request to me.
Rachel
Rachel Foerster
Rachel Foerster & Associates, Ltd.
Phone
their provider
contracting.
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone: 847-872-8070
Fax: 847-872-6860
-Original Message-
From: Noel, Keith [mailto:[EMAIL PROTECTED]]
Sent
mated means of finding a partner's profile - and make
what had been done manually now automatic, all without upsetting already
in-place systems.
William J. Kammerer
Novannet, LLC.
+1 (614) 487-0320
- Original Message -
From: "Rachel Foerster" <[EMAIL PROTECTED]>
To: "WE
FYI...
Also keep in mind that the ebXML MS specification fully supports all
required security capabilities, such as encryption, etc.
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Phone:
1 - 100 of 155 matches
Mail list logo
