#243: GPC Procedure Ontology: CPT, HCPCS
--------------------------+----------------------------
Reporter: dconnolly | Owner: gkowalski
Type: design-issue | Status: new
Priority: major | Milestone: data-domains2
Component: data-stds | Resolution:
Keywords: | Blocked By:
Blocking: |
--------------------------+----------------------------
Comment (by mish):
To understand the current process at WISC, you have to take a step back
and look at the entire process. In general, there are a series of
transformations that take place on the data as it moves from Clarity
through our Electronic Data Warehouse (EDW) into the i2b2 production
database:
Clarity -> Staging -> EDW -> i2b2 Staging -> i2b2 candidate build -> i2b2
QA Build -> i2b2 Production
All of these transformations (and the SQL that performs them) are under
the control of a tool called Informatica. Informatica
controls/schedules/maintains/executes/tracks the various transformations
within our data warehouse.
Our Clarity database resides on a fairly vanilla Oracle database. Staging
through i2b2 candidate build all reside within a Netezza MPP database
server.The i2b2 QA Build and i2b2 Produciton databases each have their own
dedicated instance of MS SQL.
One of the things services that Informatica provides for us is a lineage
tool (within something called Metadata Manager.) This allows me to simply
hop into metadata manager, and run the lineage tool to tell me that we
simply pull procedure_cd ultimately from clarity_eap.proc_code
in the clarity instance.
--
Ticket URL:
<http://informatics.gpcnetwork.org/trac/Project/ticket/243#comment:2>
gpc-informatics <http://informatics.gpcnetwork.org/>
Greater Plains Network - Informatics
_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev
