This wiki has undergone a migration to Confluence found Here
October 17, 2013 Financial Management Work Group Conference Call
Jump to navigation
Jump to search
Return to Financial Management Home Page
Contents
Conference Call Schedule
- Occurs on Thursday October 17, November 21, and December 20, 2013 @ 2:00 pm, Eastern Standard Time (New York, GMT-04:00)
- Phone Number: +1 770-657-9270 Participant Passcode: 686300# (alternative for US if the first number doesn't work: +1 888-321-4501)
Attendees
- Kathleen Connor Co-chair
- Paul Knapp Co-chair
October 17, 2013 Call Agenda
Agenda Topics
- (5 min) Roll Call, call for agenda item, approve FM Call Minutes August 29th and Cambridge September WGM Minutes
- (10 min) Review of Action Items
- (30 min) Discuss work items: FHIR, v.3, v.2 - report on search for an A_Billable_Chiro-Physio CMET
- (15 min) Other Business - WGM Planning
- (5 min) Next call agenda, interim work
Minutes
Presiding Co-chair - Quorum was not achieved, so attendees held informal discussion of agenda topics.
- RE: Approval of agenda and minutes
| Motion | Moved | Second | Affirm | Abstain | Opposed | ||
|
Approval of FM Minutes |
xxxx |
xxxx |
xxx |
xxx |
xx |
- RE: Action Items -
- RE: Work Items - Kathleen reported that Dave Hamill and Andy Stechishin cannot find an A_Billable_Chiro-Physio CMET. Paul will research further among the Canadians who developed the artifact.
- RE: FM FHIR Domain - how to structure it? Would need to create of resources to cover FM requirements, and create a number of "composites" to pull together into a message resource (the equivalent of the v.3 wrappers). To create a message to exchange, one would have to create a atom feed, which contains entries and the first entry would be the message resource, then a data element that points to the first resource in the payload, which acts as the entry point. From within the first non-message resource, reference other resources, which reference other resources in turn. Paul created a pseudo-claim to illustrate how this would be done below:
<feed>
<entry>
<content>
<Message>
-> entry point resource
<Message>
</entry>
base resource
<entry>
</entry>
<entry>
supporting resource
</entry>
</feed>
Paul has been advocating for the ability to hold the resources within the message resource structure rather than create atom feed. If sending a batch claim for example, create an atom feed with multiple message resources each containing a complete, standalone claim resource. If we don't architect it that way, then we won't be able to send batches, which need to be tracked as unique artifacts, not just undifferentiated bundles of individual claim resources. Some FHIR proponents are not favoring this composite approach to nesting multiple standalone resources in a batch, but we can't create composites we can't support FM business requirements related batch processing.
- RE: Resource Identifiers: Paul discussed the FM business requirements for including identifiers in financial resources. He demonstrated the ability to do so at the Sept. FHIR Connectathon, and provided us with the following example of a claim resource that includes an identifier at claim stamp:
<?xml version="1.0" encoding="UTF-8"?> <feed xmlns="http://www.w3.org/2005/Atom">
<title>Claim Message</title> <id>urn:uuid:886b5121-fb78-4439-b1d4-fce073bcdadd</id> <totalResults xmlns="http://a9.com/-/spec/opensearch/1.1">1</totalResults> <updated>2013-10-17T11:26:37Z</updated> <entry> <title>Provider (Billing) "organization/@1535" Claim "1500"</title> <id>urn:uuid:5596d1ca-06e5-49a9-8468-a07991c2a1b1</id> <link href="http://localhost:81/fhir/mailbox/@5596d1ca-06e5-49a9-8468-a07991c2a1b1" rel="self" /> <updated>2013-10-17T11:26:37Z</updated> <published>2013-10-17T11:26:37Z</published> <author> <name>127.0.0.1</name> </author> <content type="text/xml"> <Message xmlns="http://hl7.org/fhir"> <identifier value="urn:uuid:9fb07e49-4df7-4b39-9636-e7a5f82785b1" /> <timestamp value="2013-10-17" /> <source> <name value="KCI FHIR Connectathon 4 Client Software" /> <version value="V1.03" /> <endpoint value="http://www.pknapp.com/claims/sample" /> </source> <destination> <endpoint value="http://localhost:81/fhir/mailbox" /> </destination> <responsible> <type value="Organization" /> <reference value="organization/@1535" /> </responsible> <reason> <coding> <system value="http://hl7.org/fhir/vs/message-reason-encounter" /></coding> </reason> <Claim stamp="urn:uuid:5596d1ca-06e5-49a9-8468-a07991c2a1b1" vstamp="1"> <identifier> <label value="number" /> <system value="http://happyvalley.org/claim" /> <key value="1500" /> </identifier> <servicedate value="2013-10-17" /> <provider> <type value="Provider" /> <reference value="provider/@904563" /> </provider> <billingProvider> <type value="Organization" /> <reference value="organization/@1535" /> </billingProvider> <referrer> <type value="Provider" /> <reference value="provider/@720415" /> </referrer> <reason> <coding> <system value="http://hl7.org/fhir/v3/ReferalReason" /></coding> </reason> <patient> <name> <use value="usual" /> <family value="Smith" /> <given value="John" /> </name> <gender> <coding> <system value="http://hl7.org/fhir/v3/AdministrativeGender" /></coding> </gender> <address> <line value="1234 Any Street" /> <city value="Menlo Park" /> <state value="California" /> <postal value="90123" /> </address> <birthdate value="1973-04-14" /> </patient> <coverage> <issuer> <label value="Insurer" /> <system value="urn:BINN" /> <key value="654123" /> </issuer> <type></type> <identifier> <label value="Certificate" /> <system value="http://happyvalley.org/claim" /> <key value="A7G345" /> </identifier> <plan value="123YHT56" /> <subplan value="35" /> <dependent value="01" /> <subscriber> <name> <use value="usual" /> <family value="Smith" /> <given value="John" /> </name> <address> <line value="1234 Any Street" /> <city value="Menlo Park" /> <state value="California" /> <postal value="90123" /> </address> </subscriber> <relationship> <coding> <system value="http://hl7.org/fhir/v3/RelationshipToSubscriber" /></coding> </relationship> </coverage> <service> <instance value="1" /> <service> <coding> <system value="urn:USCLS" /></coding> </service> <fee value="65.00" /> </service> <service> <instance value="2" /> <service> <coding> <system value="urn:USCLS" /></coding> </service> <fee value="105.00" /> <location> <coding> <system value="urn:ISO-3950" /></coding> </location> <surface> <coding> <system value="urn:FDI:surface" /></coding> </surface> </service> <service> <instance value="3" /> <service> <coding> <system value="urn:USCLS" /></coding> </service> <fee value="900.00" /> <location> <coding> <system value="urn:ISO-3950" /></coding> </location> <lab> <service> <coding> <system value="urn:USCLS" /></coding> </service> <fee value="250.00" /> </lab> </service> </Claim> </Message> </content> <summary type="xhtml">
Claim: 1500
</summary> </entry>
</feed>
- RE: Other Business - Paul reported that he is now the backup FMG liaison for FM, and will work with Lloyd on managing incorporation of FM artifacts into FHIR resources as well as the composition of FM FHIR resources to cover the FM domain.
Action Items
- Paul to contact Jay about using his server for his project.
- Kathleen to contact Duane Decouteau about Paul's FHIR server and opportunities to use FHIR security labels.
Return to Financial Management Home Page
