Small Transport; Low Wing; 2 Turbojet Eng
Air Traffic Control Fully Certified
Situational Awareness; Confusion
ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Human Factors; Procedure
Aircraft X was on a vector southbound @5000 feet in my airspace.  I had another aircraft in very close proximity to him that I was trying to sequence him with (he was passing the other aircraft).  As I went to call traffic I saw a limited data block descending out of about 5800 feet descending SW bound on a converging course.  I immediately turned Aircraft X southwest-bound and descended him to 3000 feet and called traffic.  The aircraft probably got within 500 feet and 2 miles.  I did not get to watch a replay so that is just a recollection.1.  Since [the introduction of] Optimization of Airspace and Procedures in the Metroplex (OAPM) airspace changes very few people (including myself) know exactly where their airspace is without looking; thus many people violate your airspace accidentally or without knowing where their actual airspace is.2.  This aircraft was a medical emergency.  It was tagged with a yellow 'ME' but now since non-RNAV aircraft are also in yellow you no longer associate a 'yellow' color with a medical emergency (as it used to be one of the only things yellow and since you didn't see them that often you automatically noticed them easier)3.  Many of us are still used to descending to 5000 feet on feeder east and sometimes it still 'slips out' although I do not know if that happened in this case or not.4.  Way too much 'look and go' through other people's airspace without proper point-outs.  (again; I do not know if this was the case here.  5. With THREE supervisors in the tracon; someone could have walked over to ZZZ North and showed me the aircraft and pointed out that the aircraft was going direct to the airport to try to accommodate the descent for him.  This is how it SHOULD happen!  When I am CIC I always walk over to other positions and make sure they are aware of the emergency! 1.  Stop all of the 'look and go' in the Tracon and ensure that controllers are making proper point outs.  2.  Make procedures for the supervisors that they ensure ll controllers effected or who may be effected are aware of the situation.  3. It is too late about the lack of training on the OAPM stuff that I know was ATSAPed numerous times.
Aircraft Y was a medical emergency inbound to ZZZ from the northeast. He was given RWYXXR and sent direct to the fix ZZZZZ on the final.  During the time the aircraft was on frequency; I was asked by management to ask the pilot if 'The sick passenger had FLU-LIKE symptoms i.e. EBOLA'.  This was a very uncomfortable and distracting situation to deal with. There was a lot of talking going on behind me and I also had to continue to work the rest of the airplanes I had. I descended Aircraft Y to 5000; which was the lowest shelf of airspace I owned. I thought the aircraft had been coordinated with the other affected positions by supervision. As the aircraft descended out of 6000; Aircraft X inbound to ZZZ1 was descending out of 5000 southbound. The management was notified and said the situation was a non-event according to the computer plot.
TRACON Controller described a loss of separation event claiming the introduction of OAPM airspace as well as some current procedures contributed to the incident.